cancel
Showing results for 
Search instead for 
Did you mean: 

Operating system call connect failed (error no. 79 )

former_member184628
Participant
0 Kudos

Hi Team,

We are getting this error "Operating system call connect failed (error no. 79 )" in our ERP system in SM21 and when we check the gateway log it shows below log. Our instance number is 93 and gateway runs properly. But we see in the log that it is trying to connect to port 3330 instead of 3393.

Can anyone help me out in fixing this issue. I have checked all RFC connection and no where we have used sapgw30.

Need help as there are thousands of error in an hour time. I have checked all post on SCN but not able to get the solution.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

***LOG Q0I=> NiPConnect: 127.0.0.1:3330: connect (79: Connection refused) [nixxi.cpp 2896]

*** ERROR => NiPConnect: SiConnect failed for hdl 2129/sock 179

    (SI_ECONN_REFUSE/79; I4; ST; 127.0.0.1:3330) [nixxi.cpp    2896]

*** ERROR => GwIAsyncConn: GwBufConnect to 127.0.0.1 / 3330 failed (rc=NIECONN_REFUSED) [gwxx.c       1281]

***LOG S0T=> GwIAsyncConn, GwBufConnect (-0010) [gwxx.c       1283]

***LOG S0R=> GwIAsyncConn, GwBufConnect () [gwxx.c       1285]

***LOG S0S=> GwIAsyncConn, GwBufConnect (3330) [gwxx.c       1287]

*****************************************************************************

*

*  LOCATION    SAP-Gateway on host abcd.xxx.net / sapgw93

*  ERROR       partner 'loopback:sapgw30' not reached

*

*  TIME        Wed Mar 23 21:33:57 2016

*  RELEASE     721

*  COMPONENT   NI (network interface)

*  VERSION     40

*  RC          -10

*  MODULE      nixxi.cpp

*  LINE        2896

*  DETAIL      NiPConnect: 127.0.0.1:3330

*  SYSTEM CALL connect

*  ERRNO       79

*  ERRNO TEXT  Connection refused

*  COUNTER     4909664

*

*****************************************************************************

Thanks.

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Check the value mapping in your /etc/services file

raquel_gomez
Employee
Employee
0 Kudos

Hi team,

You're getting error:

***LOG Q0I=> NiPConnect: 127.0.0.1:3330: connect (79: Connection refused) [nixxi.cpp 2896]

*** ERROR => NiPConnect: SiConnect failed for hdl 2129/sock 179

    (SI_ECONN_REFUSE/79; I4; ST; 127.0.0.1:3330) [nixxi.cpp    2896]

*** ERROR => GwIAsyncConn: GwBufConnect to 127.0.0.1 / 3330 failed (rc=NIECONN_REFUSED) [gwxx.c       1281]

***LOG S0T=> GwIAsyncConn, GwBufConnect (-0010) [gwxx.c       1283]

***LOG S0R=> GwIAsyncConn, GwBufConnect () [gwxx.c       1285]

***LOG S0S=> GwIAsyncConn, GwBufConnect (3330) [gwxx.c       1287]

So, connection from SAP Gateway (sapgw93) fails when connecting to localhost, service 3330.

*****************************************************************************

*  LOCATION    SAP-Gateway on host abcd.xxx.net / sapgw93

*  ERROR       partner 'loopback:sapgw30' not reached

*  DETAIL      NiPConnect: 127.0.0.1:3330

*  SYSTEM CALL connect

*  ERRNO       79

*  ERRNO TEXT  Connection refused

*****************************************************************************

Check if entry from SM21 points to a particular work process,so we can analyze if work process trace file refers to any RFC Destination.

Is there any pattern/frequency of those enties in SystemLog? In that case, there could be a Job involved.

Regards,

Raquel

isaias_freitas
Advisor
Advisor
0 Kudos

Hello,

Besides using "sapgw30" at the "gateway options" of the destinations, the gateway will also use "sapgw30" if the "Instance No" is set to 30:

You can also use information from the transaction STAD to identify what is calling the wrong target system.

Regards,

Isaías

AtulKumarJain
Active Contributor
0 Kudos