SAP Knowledge Base Article - Preview

2678014 - Operating system call connect failed (error no. <nnn> )

Symptom

In the transaction SM21, there are many 'Operating system call/write connect failed' entries, triggered on the RFC-Gateway (RD).

In example:

<Application server> RD 000 @5C\Qvery high priority@ Q0I Operating system call connect failed (error no. <nnn>)

While in the Gateway log (dev_rd) at the same timestamp, similar to the following entries can be seen (the error numbers can vary as they depend on the actual Operating System):

***LOG Q0I=> NiPConnect2: <IP address>:<port>: connect (<nnn>: Connection refused) [/bas/745_REL/src/base/ni/nixxi.cpp 3375]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 1438/sock 44
(SI_ECONN_REFUSE/<nnn>; I4; ST; <IP address>:<port>) [nixxi.cpp 3375]
GwTraceHdlInfo: hdl 1438


Read more...

Environment

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

Product

ABAP platform all versions ; SAP NetWeaver all versions ; SAP Web Application Server for SAP S/4HANA all versions

Keywords

inactive, invalidate, reset host name buffer, internal system copy, delete RFC destination, call, write, connect failed, operating system connect failed , KBA , BC-NET , Formerly used for network tests , BC-CST-GW , Gateway/CPIC , 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.