Skip to Content
avatar image
Former Member

WSAECONNRESET: Connection reset by peer

Can anyone help me!

-


Connection to partner broken

WSAECONNRESET: Connection reset by peer

Do you want to see the detailed error description?

=======================================

Connection to partner broken /partner not reached(host 192.100.10.1, service sapdp00)

Time

Component NI(network interface) / NI(network interface)

Release 640 / 640

Version 37 / 37

Module ninti.c / nixxi_r.cpp

Line 777 / 8588

Method NipRead(192.100.10.1/sapdp00, hdl 1) / NiPConnect2

Return Code -6 / -10

System Call recv / SiPeekPendConn

Error No 10054 / 10061

Error Text WSAECONNRESET: Connection reset by peer / WSAECONNREFUSED: Connection refused

Counter 1 / 1

-


Thanks,

Praveen.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

7 Answers

  • avatar image
    Former Member
    Jan 05, 2010 at 11:52 AM

    Hi Tutika,

    Check whether you have correct entry on your SAP Logon PAD.

    Check whether you have Port 3200,3300,3600 opened for your Server IP or not, i.e..

    telnet (Server ip) Port number.........

    Check whether you have any network break b/w desktop and server.

    Cheers

    Deepanshu

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Dear Deepanshu,

      1.) I don't know how to check that I have any network break b/w desktop and server.

      Please explain step to step.

      also explain step to step about : how to check

      2.) whether i have Port 3200,3300,3600 opened for your Server IP or not, i.e..

      telnet (Server ip) Port number.........

  • avatar image
    Former Member
    Jan 12, 2010 at 09:42 AM

    Connection to partner broken

    WSAECONNRESET: Connection reset by peer

    Above error occurs if any network disturbance exists.

    Are you able to login again?

    Thanks & Regards,

    Nagendra.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi, l want to update the subject. l faced with this problem for a few days. l read about the solution with firewall and l checked my system. l use win7 and l stopped the windows firewall. My problem is over.

      Burak,

  • avatar image
    Former Member
    Jan 02, 2011 at 07:10 PM

    thx

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 23, 2012 at 12:20 PM

    Solution


    1.

    If the dispatcher crashes, it means that the entire instance terminates. In this case, put the message under the component BC-CST-DP for further analysis.

    2.

    Network problems must (and can only) be analyzed and solved by the customer's network department.

    • You can use the SAP tool niping to examine general network problems.

      Start the following tests between the affected client and server:

      Note 500235, Test 3b (firewall idle timeout)
      Note 155147, 3. (Black Hole Router)
    • The trace of the affected dispatcher (dev_disp) and the error trace of the SAP GUI (errorlog.gui) can be used as sources of information.

      For more details, reproduce the error and perform the following steps:

      Increase the trace level of the dispatcher to 2 before the user logs on.

      When the error occurs, confirm that you want to see a detailed error message.

      Reduce the trace level of the dispatcher to <nn> minutes, where: <nn> = 2 * rdisp/keepalive
    • In the last instance, you create a network trace on the client and the server (for example, using Wireshark, tcpdump) to find the cause of the error.


    See also the notes listed under 'Related notes'.

    If you require help analyzing the trace, send the following information to SAP Support:

    • dev_disp
    • errorlog.gui
    • created network traces of client and server
    • User name
    • IP address of the user
    • Time when you reproduced the error
    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Dear Manish

      I now set rdisp/keepalive on all my Systems (50+) to 280, and my connections are now stable. If you have got the described symptoms, try this work around. Please note: You have to REDUCE the value, not increase it.

      Regards, Dieter

  • avatar image
    Former Member
    Jul 19, 2013 at 09:24 AM

    The Windows Connection Reset by Peer (WSACONNRESET or error number 10053) indicates that the connection to a communication partner was broken for UNKOWN reasons.

    Possible reasons are:

    • communication partner program did crash or was manually aborted
    • computer where the communication partner was running on was shutdown
    • network connection lost (cable unplugged, switch down, WLAN device shutdown)
    • in very rare cases operating system problems
    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Update: I previously wrote:

      If you can't tweak your firewall, you could play around with the profile parameter rdisp/keepalive, which has a standard of 1200 (20 minutes). When this value is reached, the application server sends a ni_ping to the front-end, which should answer with a ni_pong. This traffic should reset the TTL-counter on the firewall, so that the firewall does not drop the connection. So one could try changing this parameter to 300 (5 minutes). I haven't tested this, but it should work.

      I now set rdisp/keepalive on all my Systems (50+) to 280, and my connections are now stable. If you have got the described symptoms, try this work around. Please note: You have to REDUCE the value, not increase it.

      Regards, Dieter

  • avatar image
    Former Member
    Aug 07, 2014 at 11:25 AM

    Connection Reset by Peer (WSACONNRESET or error number 10053)

    I agree, had this error serveral times on some customer systems. It´s because some network errors (Connection reset). You have to find where the Network error happens for example in the Network of customer, Network Errors in the way between (Providers) or at your local data center.
    As Basis admin it´s almost unpossible to find the root cause, please ask your responsible Network Support contact.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Mar 10, 2016 at 11:10 AM

    Hi,

    we did all the stuff mentioned above. Finally a network analysis showed us, that one of our providers set the MTU to 1200 instead of the standard of 1500. This interferes very badly with SAP-GUI. So check this parameter with your providers, if all the steps above do not help.

    Best,

    Tammo

    Add comment
    10|10000 characters needed characters exceeded