Showing results for 
Search instead for 
Did you mean: 

disconected SAP GUI

Former Member
0 Kudos

We are frequently getting error "Connection reset by peer" in the SAPGUI. Even Application server and database is running fine still we are facing this after some time and whenever we are working from customer premises.

Could not understand what is the issue? Is there any one face this issue?

log dev_disp.

Fri Dec 05 09:35:14 2014

***LOG Q0I=> NiIRead: P=10.154.XXX.XXX:63683; L=10.224.XXX.XXX:3201: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5087]

*** ERROR => NiIRead: SiRecv failed for hdl 55/sock 1696

    (SI_ECONN_BROKEN/10054; I4; ST; P=10.154.XXX.XXX:63683; L=10.224.XXX.XXX:3201) [nixxi.cpp    5087]

DpRTmPrepareReq: network error of client T51, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3

DpRTmPrepareReq: client address of T51 is 10.154.XXX.XXX(10.154.XXX.XXX)

***LOG Q04=> DpRTmPrep, NiBufReceive (13070XNAME51 XCOMNAME65) [dpxxdisp.c   12344]

RM-T51, U13070, 100 XNAME, XCOMPNAME, 09:29:26, M0, W3, ZFIA, 3/2

Best Regards


Accepted Solutions (1)

Accepted Solutions (1)

Active Contributor
0 Kudos

Hi Tomasz,

Are your end-users actually getting disconnected while working? Or are you just noticing this in the logs on the server, but no one is actually complaining about it? This could simply be clients timing out after being idle too long, which might indicate a tendency on the part of users to not properly logout when finished with the system. If that's the case, it's not really problem, it indicates that things are working correctly.

If, however, users are being disconnected while actively working in the system, then that is a problem that needs investigation. The cause can be widely varied. Are there particular workstations, or workstations in a particular area, that regularly have the problem, while others do not? Then suspect network connections for those workstations, or a switch or router for that workgroup. Is it all workstations? Then maybe it's a switch/router closer to the server. You could use NIPING to get a little more detailed connection testing done than simple PING and TRACERT tests will provide, but ultimately you may need your network operations group to do some tracing/sniffing to see what's going on.



Answers (3)

Answers (3)

0 Kudos

Hello Tomasz

It's sounds counter-intuitive at first,but here's a quick tip.

If the Gui can display a popup with the WSAECONNRESET error, then the issue is not Sapgui.

The reason behind this is that the Sapgui is still able to communicate to the backend about the error.

If, on the other hand,the Sapgui just disappears, and the error is found in the system logs in the backend, then the issue is the Sapgui.

The reasoning here, is that the communication is lost at the frontend, either due to memory or corrupted Sapgui, and the issue needs to be investigated.

Hope this can help somewhat.


0 Kudos

Hi, Tomasz.

Have you tried to use a low-speed connection parameter in your SAP GUI connection settings?

Seems, that once I had the same situation and we created a small program which just continuously called function 'SAPGUI_PROGRESS_INDICATOR', so connection never broke because of a time-out.

Of course, you always have to run this program and one of your sessions is already used... but it worked out for some time.

Active Contributor
0 Kudos

Hi Tomasz,

It seems like network issue.

Try to ping your server in your desktop and see time interval.

Check firewall settings.

Ask Basis team to check timeout in SAP server and Also check if the parameter rdisp/gui_auto_logout in RZ10 ist higher than 360 (which would be auto logoff after 6 minutes idle time).

Check the system log (SM21) and check the return code of the connection lost. If your RC=456 this seems to be a network issue.

155147 - WinNT: Connection reset by peer


V Srinivasan