Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Operating system call connect failed (error no. 79 )

Former Member

‎05-12-2015 8:18 AM

0 Kudos

I had 2 instances, instance number 41 and 42. I just remove instance 42 (dialog instance).

After that, every 5 minutes I receive error in SM21. The error :

Operating system call connect failed (error no. 79 )

NiConnect Unsuccessful, Return Code: -0010

> Host: SAPEPRD10

> Service: sapgw42

I check trace in SMGW :

(SI_ECONN_REFUSE/79; I4; ST; 10.91.10.59:3342) [nixxi.cpp2897]
*** ERROR => GwIAsyncConn: GwBufConnect to SAPEPRD10 / sapgw42 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 (sapgw42) [gwxx.c   1287]

It's the same content in dev_rd :

(SI_ECONN_REFUSE/79; I4; ST; 10.91.10.59:3342) [nixxi.cpp2897]
*** ERROR => GwIAsyncConn: GwBufConnect to SAPEPRD10 / sapgw42 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 (sapgw42) [gwxx.c   1287]

How can I fix this problem?

Thank you

2 REPLIES 2

Former Member

‎05-20-2015 6:41 PM

0 Kudos

Hello,

Error 79 means Connection Refused.

The "Connection Refused" error  means that the host can be reached but the port is not bound on this host. If you check the gateway trace file dev_rd you should find more details on the error, for example
you should be able to see the host and port number involved.

When the problem happens try and connect to the server and port from where the error occurs:

niping -c -H hostname -S portnumber

Also check if the host and port are resolved to the correct value (also on the host where the error occurs)

> niping -v -H hostname
> niping -v -S sapgwXX

If the niping fails, please check the Network for errors and also
ensure that the correct port is used.

Also ensure there is an entry for sapgwXX in the services file.

Regards,

Fionnuala

Former Member
In response to Former Member

‎05-21-2015 3:53 AM

0 Kudos

The problem is not "How to connect sapgw42" but, "why is sapgw42 still being accessed after I uninstalled instance number 42".