Skip to Content

SAPGUI connection WSAECONNABORTED with niping


we are experiencing a lot of SAPGUI connection aborts with Error WSAECONNABORTED.

I had run the command niping with the following parameters:

niping -c -H -S 3218 -O -P -L 1000

It breaks after 66 loops. The last one has always a very high reponse time in comparison

with all other pings before. You can see it the screenshots.

So my question is if this behaviour is quite "normal" or does it indicate a serious network issue ?

Must the niping command run without any errors ?

And if so, how can we interpreting the results and aborts ?

Thanks for your hints!



niping.jpg (140.3 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Sep 12, 2016 at 11:42 AM


    in SAPGUI trace sapni.trc we can some entries like this.

    TM_LAYER TmRead (0) >>

    NiIRead: hdl 1 received incomplete data (rcd=3468,pnd=5620,pac=2)

    NiIRead: hdl 1 recv would block (errno=EAGAIN)

    NiIPeek: peek successful for hdl 1 (r)

    NiIRead: hdl 1 received data (rcd=9088,pac=3,MESG_IO)

    Adresse   Offset  Data from Application Server

    The wireshark log shows some TCP retransmissions in this time window.

    Any ideas what cause can be responsible for that ?


    Add comment
    10|10000 characters needed characters exceeded

    • Hello Sebastian,

      Can you share the niping output from the failure that occurred when you executed niping at the server itself?

      After you are able to logon, can you access the transaction SM50?

      Do you see all work processes taken, or are there free dialog processes?

      (share a screenshot, if possible).