1139596 - SAP GUI: Connection to partner 'sapserver:sapdp00' broken

Symptom

There is an error message of the following type in the SAP GUI:

  XYZ: Connection to partner 'sapserver:sapdp00' broken

After confirming the error message, SAPGUI is closed immediately.

Other Terms

Connection to partner broken, SAP GUI, error message, network, connection
Connection reset by peer WSAECONNRESET

Reason and Prerequisites

This error message can be caused by two factors:

1.

There is a crash in the dispatcher process of the instance to which the client was connected. This triggers a TCP package with an activated RST flag, which is sent to all connected communication partners and triggers the error message described above in the SAP GUI, among others. All connections are then automatically broken.

2.

Network problems

• Firewall idle timeout
  
  A firewall (or another active component) between client and server invalidates the affected connection if packages are not sent using this connection for a defined period.

• Black Hole Router
  
  See Note 155147.

• VPN, WAN problems

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

Header Data

Released On	06.11.2008 18:21:31
Release Status	Released for Customer
Component	BC-NET Network Infrastructure
Other Components	BC-FES-GUI Graphical User Interface
Priority	Recommendations / Additional Info
Category	Consulting