Operating system call connect failed (error no. 79 )

[Former Member]

Hello,

we get lots of errors in TA sm21 - systemlog...

It says Operating system call connect failed (error no. 79 ).

Detailed information:

Module nam Line Error text Caller.... Reason/ca

nixxi.cp 2769 connect 79 NiPConn connect

Name for errno number ECONNREFUSED

Interprocess communication (e.g. TCP/IP) connection refused by partne

This usually means that the necessary receiver program is not running

This error occurs hourely ( + / - a few seconds ) and more than one time... for example at 1 pm there was 1 error, but on 2 pm there had been 5...

What can it be?

[antonio_voce]

Hi ,

there is any dump ? check st22 and post here.

so also check in sm37 hourly jobs : maybe it is a background jobs that go in error.

Antonio

Edited by: Antonio Voce on Jun 5, 2008 5:48 PM

[Former Member]

Hello,

there are no dumps in the system, also no cancelled jobs.

[antonio_voce]

It is not necessary that the job is cancelled.

Then , note the workprocess number that goes in error , go in st11 and post here the wp log.

antonio.

[Former Member]

Hello,

where can i find the workprocess number?

In the syslog entry i cant find it:

Time Type Nr Clt User TCode Grp N Text

15:02:01 RD Q0 I Operating system call connect failed (error no. 79 )

Task...... Process User...... Terminal Session TCode Program Cl Problem cl Packag

34734 Gateway K SAP Web AS Problem STSK

Module nam Line Error text Caller.... Reason/ca

nixxi.cp 2769 connect 79 NiPConn connect

File Offset RecFm System log type Grp N variable message data

12956 425520 m Error (Function,Module,Row) Q0 I connect 79 NiPConnconnectnixxi.cp2769

Thats all i can see...

[antonio_voce]

Hi ,

go to transaction SM21 then double click on the log . here you will find the column N. ,this is the WP number. then run t.code st11 and double click on dev_wN ( where N is the previous number withouth 0 ).

Antonio.

[holger_mundhahs]

Hello Benjamin,

because it's type "RD" you can check the SAP Gateway trace dev_rd. Use TA SMGW

Goto->Trace->Gateway->Display File

Jump to the corresponding date. Are there more information in this file?

Maybe you can increase the trace level to get more information.

Regards

Holger

[antonio_voce]

yes yes , as you tell !

sorry for the missunderstandig.

Post here the log.

[Former Member]

Hi,

Please chekc the transactional RFC in SM58, they must be failed IDOC which is stuck due to unavilable RFC destination.

Generally

When IDocs are sent by SAP while the external system is not available at this moment, these IDocs / calls are flagged with error im SM58 (tRFC monitor). The calls are resent automatically after minutes depending on the system configuration

so delete the failed IDOCS which are not able to reach the target system due to RFC failures. and make sure no idoc's will be send to the system which is not avialable.

Hope this help you.

Mahesh Babu Gutta.