SAP Knowledge Base Article - Preview

3393957 - WSAETIMEDOUT: Connection timed out in the RFC-Gateway trace from an inactive host


Upon review of the gateway log, the following entry was observed. It appears that the SAP system is trying to establish a connection with an old SAP host of IP address on Gateway Port 3301. Regardless, this host is currently offline. 

This connection attempt is for example initiated by the user SAPServiceDA at five-minute intervals. It is unclear why a connection is being attempted with the old server. 

The following can be seen in the gateway log (dev_rd):

***LOG Q0I=> NiPConnect2: connect (10060: WSAETIMEDOUT: Connection timed out)
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 295/sock 1608
(SI_ECONN_REFUSE/10060; I4; ST; [nixxi.cpp 3454]
GwTraceHdlInfo: hdl 295

It is crucial to determine why SAPServiceDA is trying to connect to the old server and how to redirect this to the correct server.



  • Operating System independent
  • Database independent
  • SAP NetWeaver
  • SAP Web Application Server for SAP S/4HANA
  • ABAP Platform 


server decommission, gateway connect, 10060: WSAETIMEDOUT: Connection timed out , KBA , BC-CST-GW , Gateway/CPIC , BC-NET , Network Infrastructure , BC-CST , Client/Server Technology , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.