Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Operating system call connect failed (error no. 79 ) How to resolve?

Hi Guru's,

we have often entrys like "Operating system call connect failed (error no. 79 )" in the Syslog (SM21).

How is the best way to find the cause of the messages?

In the detail of the Syslog-Message are only this...

Details Page 13 Line 24 System Log: Local Analysis of p51a004                 1                                                                                
Time     Type Nr Clt User TCode Grp N Text                                                                                
08:00:56 RD                     Q0  I Operating system call connect failed (error no. 79 )                                                                                
Operating system call connect failed (error no. 79 )                                                                                
Details                                                                                
Recording at local and central time........................ 12.03.2009 08:00:56                                                                                
Task...... Process User...... Terminal Session TCode Program Cl Problem cl         Package                                                                                
12575      Gateway                                           K  SAP Web AS Problem STSK                                                                                
Further details for this message type                                                                                
Module nam Line Error text        Caller.... Reason/cal                                                                                
nixxi.cp   2823        connect 79 NiPConn    connect                                                                                
Documentation for system log message Q0 I :                                                                                
The specified operating system call was returned with an error.                                                      
 For communication calls (receive, send, etc) often the cause of errors                                               
 are network problems.                                                                                
It could also be a configuration problem at operating system level.                                                  
 (file cannot be opened, no space in the file system etc.).                                                           
 Additional specifications for error number 79                                                                        
 Name for errno number ECONNREFUSED                                                                                
Interprocess communication (e.g. TCP/IP) connection refused by partner.                                                                                
This usually means that the necessary receiver program is not running.                                                                                
Technical details                                                                                
File Offset RecFm System log type             Grp N variable message data                                                                                
240 473220 m     Error (Function,Module,Row) Q0  I        connect 79                     NiPConnconnectnixxi.cp2823                                                                                

In the dev_ traces are not more informations.

regards

chris

Former Member
Former Member replied

Dear Chris,

more information should be in dev_rd. The error means that a TCP connection to the specified server/port could not be established. You will see the same error, when you do 'telnet <host> <port>' on a port that is not being used. If dev_rd does not give more info, then do the following:

1. Reset the trace file dev_rd (e.g. from transaction SMGW)

2. Set the profile parameters:

rdisp/TRACE_PATTERN_0 = Q0I

rdisp/TRACE_LOGGING = on, 20 m

3. Increase the trace level of the gateway

This will run the gateway in trace level 2 up to the point in time when there is another Q0I syslog. dev_rd should then tell you the server and port that is being used.

Best Regards,

Tim

0 View this answer in context

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question