Error no. 10054

[former_member182034]

users are getting disconnection issue during execution and when I check  the log in SM21 there are following errors are showing.

{  Operating system call recv failed (error no. 10054)  Connection to user 2206 (HCM-01 ), terminal 95 ( )

lost  Operating system call recv failed (error no. 10054)  Connection to user 2463 (SKR-02 ), terminal 183 ()

Operating system call recv failed (error no. 10054)  Connection to user 2436 (BWP-02 ), terminal 118 (WIN) lo

Operating system call recv failed (error no. 10054)  Connection to user 2435 (GWR-02 ), terminal 178 los

Operating system call recv failed (error no. 10054)  Connection to user 2100 (SGD-01 ), terminal 131 () lost

Operating system call recv failed (error no. 10054)  }

please guide me how can I rectify this issue and please check the result of attached niping result.

Regards,

172.20.3.150.txt.zip

[Former Member]

first check the pattern in the SM21 log. Find which users appeared to be frequently disconnected, get their IPs(hope it is static and not connected through VPN), list few of them.

try orkun's script on them but modify it so that it has timestamp ( this is easy to do in linux.: ping <ip address> | while read result; do echo "$(date): $result"; done; ).

I dont know how to do it with windows scripting. Maybe someone here can help.

compared log result with SM21 log --> when users getting disconnected, are they also being unable to be reached from network.around that time?

If yes, try offer the network guys four finding and tell them client disconnected from SAP because they lost network connection.

[former_member182034]

Dear all,

thanks for your concern,

I have searched this error 10054 on google/scn and read number of replies inwhich some people said that check the Network, firewall and Switches with the help of ping, NIPING. today, I did logon on Server via wireless than wired and bypass the firewall and result is below.

Without Firewall	Via Firewall	Wireless
niping -c -H 172.20.0.9 -B 100000 Thu Jun 07 11:35:12 2012 connect to server o.k. send and receive 10 messages (len 100000) ------- times ----- avg    18.687 ms max    20.497 ms min    18.011 ms tr  10451.952 kB/s excluding max and min: av2    18.545 ms tr2 10531.885 kB/s	niping -c -H 172.20.0.9 -B 100000 Thu Jun 07 11:24:57 2012 connect to server o.k. send and receive 10 messages (len 100000) ------- times ----- avg  1708.306 ms max 16918.592 ms min    17.979 ms tr    114.331 kB/s excluding max and min: av2    18.311 ms tr2 10666.548 kB/s	niping -c -H 172.20.0.9 -B 100000 Thu Jun 07 12:10:44 2012 connect to server o.k. send and receive 10 messages (len 100000) ------- times ----- avg  1772.103 ms max 16947.342 ms min    52.670 ms tr    110.215 kB/s excluding max and min: av2    90.127 ms tr2  2167.069 kB/s
niping -c -H 172.20.0.9 -B 1000000 -L 100 Thu Jun 07 11:36:01 2012 connect to server o.k. Thu Jun 07 11:36:23 2012 send and receive 100 messages (len 1000000) ------- times ----- avg   220.843 ms max  4705.512 ms min   171.932 ms tr   8843.939 kB/s excluding max and min: Thu Jun 07 11:36:24 2012 av2   175.581 ms tr2 11123.814 kB/s	niping -c -H 172.20.0.9 -B 1000000 -L 100 Thu Jun 07 11:27:08 2012 connect to server o.k. Thu Jun 07 11:27:26 2012 send and receive 100 messages (len 1000000) ------- times ----- avg   179.279 ms max   220.964 ms min   172.571 ms tr  10894.343 kB/s excluding max and min: av2   178.922 ms tr2 10916.075 kB/s	niping -c -H 172.20.0.9 -B 1000000 -L 100 Thu Jun 07 12:11:01 2012 connect to server o.k. Thu Jun 07 12:11:53 2012 send and receive 100 messages (len 1000000) ------- times ----- avg   524.703 ms max   778.526 ms min   440.597 ms tr   3722.341 kB/s excluding max and min: av2   522.972 ms tr2  3734.668 kB/s
niping -c -H 172.20.0.9 -B 500 Thu Jun 07 11:36:33 2012 connect to server o.k. send and receive 10 messages (len 500) ------- times ----- avg     0.696 ms max     1.124 ms min     0.572 ms tr   1403.510 kB/s excluding max and min: av2     0.658 ms tr2  1484.702 kB/s niping -c -H 172.20.0.9 -B 1000 Thu Jun 07 11:36:37 2012 connect to server o.k. send and receive 10 messages (len 1000) ------- times ----- avg     0.770 ms max     1.195 ms min     0.681 ms tr   2536.197 kB/s excluding max and min: av2     0.728 ms tr2  2682.403 kB/s niping -c -H 172.20.0.9 -B 1400 Thu Jun 07 11:36:41 2012 connect to server o.k. send and receive 10 messages (len 1400) ------- times ----- avg     1.013 ms max     2.174 ms min     0.664 ms tr   2699.284 kB/s excluding max and min: av2     0.912 ms tr2  2999.863 kB/s niping -c -H 172.20.0.9 -B 1500 Thu Jun 07 11:36:44 2012 connect to server o.k. send and receive 10 messages (len 1500) ------- times ----- avg     1.701 ms max     6.676 ms min     0.839 ms tr   1721.928 kB/s excluding max and min: av2     1.187 ms tr2  2467.365 kB/s niping -c -H 172.20.0.9 -B 4000 Thu Jun 07 11:36:49 2012 connect to server o.k. send and receive 10 messages (len 4000) ------- times ----- avg     2.125 ms max     4.283 ms min     1.406 ms tr   3675.779 kB/s excluding max and min: av2     1.946 ms tr2  4015.419 kB/s niping -c -H 172.20.0.9 -B 10000 Thu Jun 07 11:36:53 2012 connect to server o.k. send and receive 10 messages (len 10000) ------- times ----- avg     2.947 ms max     5.209 ms min     2.476 ms tr   6628.177 kB/s excluding max and min: av2     2.723 ms tr2  7173.354 kB/s niping -c -H 172.20.0.9 -B 40000 Thu Jun 07 11:36:56 2012 connect to server o.k. Thu Jun 07 11:36:57 2012 send and receive 10 messages (len 40000) ------- times ----- avg     8.361 ms max    10.703 ms min     7.661 ms tr   9343.531 kB/s excluding max and min: av2     8.156 ms tr2  9578.544 kB/s	niping -c -H 172.20.0.9 -B 500 Thu Jun 07 11:29:51 2012 connect to server o.k. send and receive 10 messages (len 500) ------- times ----- avg     1.004 ms max     3.557 ms min     0.490 ms tr    973.156 kB/s excluding max and min: av2     0.749 ms tr2  1304.693 kB/s niping -c -H 172.20.0.9 -B 100 Thu Jun 07 11:29:55 2012 connect to server o.k. send and receive 10 messages (len 100) ------- times ----- avg     0.854 ms max     1.946 ms min     0.567 ms tr    228.810 kB/s excluding max and min: av2     0.753 ms tr2   259.422 kB/s niping -c -H 172.20.0.9 -B 1400 Thu Jun 07 11:30:00 2012 connect to server o.k. send and receive 10 messages (len 1400) ------- times ----- avg     1.227 ms max     4.627 ms min     0.667 ms tr   2227.778 kB/s excluding max and min: av2     0.872 ms tr2  3133.954 kB/s niping -c -H 172.20.0.9 -B 1500 Thu Jun 07 11:30:03 2012 connect to server o.k. send and receive 10 messages (len 1500) ------- times ----- avg     1.070 ms max     2.281 ms min     0.727 ms tr   2738.538 kB/s excluding max and min: av2     0.961 ms tr2  3047.789 kB/s niping -c -H 172.20.0.9 -B 4000 Thu Jun 07 11:30:09 2012 connect to server o.k. send and receive 10 messages (len 4000) ------- times ----- avg     1.809 ms max     3.067 ms min     1.258 ms tr   4318.446 kB/s excluding max and min: av2     1.721 ms tr2  4540.171 kB/s niping -c -H 172.20.0.9 -B 10000 Thu Jun 07 11:30:16 2012 connect to server o.k. send and receive 10 messages (len 10000) ------- times ----- avg     3.025 ms max     4.871 ms min     2.566 ms tr   6456.398 kB/s excluding max and min: av2     2.852 ms tr2  6848.865 kB/s niping -c -H 172.20.0.9 -B 40000 Thu Jun 07 11:30:21 2012 connect to server o.k. Thu Jun 07 11:30:22 2012 send and receive 10 messages (len 40000) ------- times ----- avg     8.908 ms max    11.140 ms min     7.753 ms tr   8770.207 kB/s excluding max and min: av2     8.773 ms tr2  8904.783 kB/s	niping -c -H 172.20.0.9 -B 500 Thu Jun 07 12:11:34 2012 connect to server o.k. send and receive 10 messages (len 500) ------- times ----- avg    15.662 ms max    26.952 ms min     3.893 ms tr     62.353 kB/s excluding max and min: av2    15.722 ms tr2    62.116 kB/s niping -c -H 172.20.0.9 -B 100 Thu Jun 07 12:11:45 2012 connect to server o.k. send and receive 10 messages (len 100) ------- times ----- avg     9.724 ms max    18.294 ms min     5.310 ms tr     20.086 kB/s excluding max and min: av2     9.204 ms tr2    21.220 kB/s niping -c -H 172.20.0.9 -B 1400 Thu Jun 07 12:11:51 2012 connect to server o.k. send and receive 10 messages (len 1400) ------- times ----- avg    11.024 ms max    28.704 ms min     2.056 ms tr    248.032 kB/s excluding max and min: av2     9.935 ms tr2   275.216 kB/s niping -c -H 172.20.0.9 -B 1500 Thu Jun 07 12:11:53 2012 connect to server o.k. send and receive 10 messages (len 1500) ------- times ----- avg    14.250 ms max    28.295 ms min     6.019 ms tr    205.589 kB/s excluding max and min: av2    13.524 ms tr2   216.637 kB/s niping -c -H 172.20.0.9 -B 4000 Thu Jun 07 12:11:56 2012 connect to server o.k. send and receive 10 messages (len 4000) ------- times ----- avg     4.142 ms max     6.885 ms min     2.966 ms tr   1886.030 kB/s excluding max and min: av2     3.946 ms tr2  1979.602 kB/s niping -c -H 172.20.0.9 -B 10000 Thu Jun 07 12:11:57 2012 connect to server o.k. send and receive 10 messages (len 10000) ------- times ----- avg     6.763 ms max     9.329 ms min     5.184 ms tr   2887.999 kB/s excluding max and min: av2     6.640 ms tr2  2941.675 kB/s niping -c -H 172.20.0.9 -B 40000 Thu Jun 07 12:11:58 2012 connect to server o.k. Thu Jun 07 12:11:59 2012 send and receive 10 messages (len 40000) ------- times ----- avg    22.639 ms max    42.499 ms min    16.584 ms tr   3450.919 kB/s excluding max and min: av2    20.913 ms tr2  3735.670 kB/s

the result of ping with wireless, firewall and without firewall is:

Reply from 172.20.0.9: bytes=32 time=11ms TTL=128

without Firewall:

time=11ms is vary from 11 to 12

with Firewall:

time=11ms is vary from 11 to 30

Wireless:

time=11ms is vary from 11 to 100+

the above analysis is showing that there is issue in Network.

what do you say?

Regards

[Former Member]

Hi Jamil,

It is obvious that you have a network problem. Check your network components.

Additionally, the system admin may be kill the process on SM50

Best regards,

Orkun Gedik

[former_member182034]

Dear respected Orkun,

thanks for reply,

Dear, 2 week ago, we were got this error 10054 when we replaced a new Cisco switch and we put back the old switch but still getting disconnection issue.

I have already checked the ping, switches and Firewall which are working fine. now would you tell me which components, I have to check.

Thanks and Regards,

[Former Member]

You should check log traces for each component from the client to the server, such as ethernet drivers, cards, switches and so on. I suggest you to execute ping command at the client side for 1 day, as below;

ping <sapserver> -t > out.txt

Then, check for the "Request timed out" periods. So you will be able to be sure that this problem is caused by a network component. After that you can check the components, one by one.

Best regards,

Orkun Gedik

[former_member182034]

Dear Orkun,

the ping command is working fine and not dropping any packet on those client which are connected to LAN via cable/wired. simple ping is also working fine on those Client which are connected via Wireless while when i ping to server via following command then i got timeout request after 6 to 8 minutes.

timout:

ping 172.20.0.8 -t -l 60000

get only 1 time out after 6 to 8 minutes

working fine

ping 172.20.0.8 -t

Reply from 172.20.0.8: bytes=32 time=1ms TTL=128

here the time is not crossing the 100ms while TTL is consist 128.

network guy is saying that network/switches/Firewall are working fine.

Regards,

[Former Member]

Hi Jamil,

I still believe this problem is caused by the network infrastructure. Additionally, check the Note 413330 - Network timeouts. It may be a workaround about the case.

Best regards,

Orkun Gedik

[former_member182034]

hi Orkun,

thanks for sharing SAP Note.

Dear, I have already read these SAP Notes.

Note 155147 - WinNT: Connection reset by peer

currently, the above MTU entry does not exist in regedit while the result of MTU is:

C:\Users\prdadm>netsh interface ipv4 show subinterfaces

   MTU  MediaSenseState   Bytes In  Bytes Out  Interface

------  ---------------  ---------  ---------  -------------

4294967295                1          0      34398  Loopback Pseudo-Interface 1

  1500                1   32085056    4240696  Local Area Connection

  1500                1  196447728860  47588375757  Local

  1500                1  392079117  1676098043  VPN

here mostly VPN users are getting Error 10054. so now confirm me the parameter value, is it ok.

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCPIP\Parameters

EnablePMTUBHDetect=1

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCPIP\Parameters

MTU=1500

Note 413330 - Network timeouts.

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCPIP\Parameters

TcpMaxConnectRetransmissions=3

TcpMaxDataRetransmissions=5

there is mentioned in above notes that some registry entries are required to add. as you know that registry task is very critical on Server end, so would you  guide me to set the correct Registry entries which i have to add on Server level.

Regards,

[Former Member]

If mostly VPN users get the logout error you should definitely check the VPN backend. There might be a certain disconnect parameter set for VPN clients (e.g. inactivity on client side). If you can adjust that parameter and increase the time before the VPN backend believes a disconnect has to be forced your logout error might be solved.

Kind regards,