SAPGUI Disconnecting after 20 minutes

[simon_redondie]

Hello,

For a few days, some of our users are experiencing SAPGUI disconnections after 20 minutes of idle time.

In dispatcher log, we have found this error :

Mon Dec 15 19:14:24 2008

ERROR => DpCheckTerminals: NiCheck2(rc=-23) failed for tid: 74 (60secs)-> disconnecting [dpxxdisp.c 10584]

RM-T74, U4631, 610 <user name G00248443>, <computer name>, 18:53:19, M0, W6, PA30, 2/2

We used Wireshark to find out if there is a connection problem but we didn't see any : During normal work, many TCP paquet are captured to AS server service (3200) and during the idle time, no paquet is captured.

Do you know if "Low speed connection" option can help ?

Do you know if it's possible to force the SAPGUI to send a "keepalive" paquet each minute to avoid the disconnection ?

Regards ,

LTN Redondie Simon

Edited by: Simon REDONDIE on Dec 15, 2008 6:33 PM

[Former Member · Accepted solution]

> Do you know if it's possible to force the SAPGUI to send a "keepalive" paquet each minute to avoid the disconnection ?

You can set server to send keepalive by setting rdisp/keepalive parameter.

[simon_redondie]

Hello,

First of all, thank you for you answers, we are trying the different solutions.

Our users log into SAPGUI through the "SAPGUI Iview" in Enterprise Portal 6.40. We didn't find the parameter to force "Low speed connection" in the iview nor in the content system. Do you know if it's possible to set this ?

Regards,

LTN Redondie Simon

[martin_juen2]

hi.

i think that is not the "classic" gui you are talking about - it's only an portal application. for me it sounds that your user will be logged out on portal after being 20 minutes idle. not from the windows application sap gui.

it might be critical if you customize the portal, that no one will be logged out (ever). the connections to the portal and the backend are not cleaned up. that can cause performance or other problems - mainly depends on your installation.

why not using windows gui?

regards,

martin

[simon_redondie]

Hello,

We have found the problem : our WAN did not tranport "NI_PING" packet (to small) from saprotocol to SAPGUI client.

The "rdisp/keepalive" parameters helped us very much because we raised the time-out to 60 minutes until we found how to fix the issue on our network.

Regards,

LTN Redondie Simon

[Former Member]

simon,

It will really help us - if you could share with us - as to how you changed the WAN parameters to interpret NIPING in lowercase .

arvind

[simon_redondie]

Hello,

We did not have any problem NI_PING packet.

We eventually found a time-out on a firewall rule that shutdown the connection only in a side !!

Regards,

LTN Redondie Simon

[Former Member]

Hai,

Low speed connection options will really help. Try pacthing your GUI tlatest level.

Check your system logs in SM21, check the logs in the Front end machine to get some inputs about the error.

Check whether any scheduled tasks are running in the machine,.

Sometimes this happens if any CPU process consuming a lot of cpu load on the server, try to find any unwanted exe's running, try to kill them and check.

Regards,

Yoganand.V