cancel
Showing results for 
Search instead for 
Did you mean: 

Operating system call recv failed (error no. 73 )

Former Member
0 Kudos

Can any one help me finding this error? I could not find any note.

Here are some detail logs ..

-


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 73

Name for errno numbe ECONNRESET

Short text Connection reset by peer

No documentation available for error ECONNRESET

-


Entry type.......... m ( Error (Function,Module,Row) )

Message ID.......... Q0 I

Variable parts...... recv 73 NiPReadrecv niuxi.c 928#

-


Any body???

Points will be given for sure (any answer??)

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Actually when are u facing the above error, is it when starting SAP system and that too the central system? Do u have CI and DI on the same system?

If so there is no point in network problems, else u can have a loopback adapter and try to start the system.

Please let me know if u have any more queries.

Regards,

Phani

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi,

You can do the following

1)With transaction ST11 or AL11, read the developer trace in question (in most cases, this is dev_disp or dev_ms). This contains the complete message.

2) On UNIX systems, you can get information via the 'man' command at operating system level, for example:

man recv

the error code file:

/usr/include/sys/errno.h

Regards

Umesh

Former Member
0 Kudos

Dear Afi,

where did you get the error message from ? In which tracefile or syslog

is this error reported.

Kind regards

Thomas Alt

Former Member
0 Kudos

Hi,

Thanks for your reply. So what kind of trace should I do? such as sql trace? RFC trace? what exactly should I do to monitor or trace it?

Thanks,

norbert_sieker
Explorer
0 Kudos

The connection you are trying to access has been reset by the peer (remote) machine. This usually means that the program on the other end has crashed, or closed the socket unexpectedly for some reason.

As ECONNRESET points to a basic and low level event in TCP protocol, the reason can be any kind of network or application issue.

I am sorry, but this error is too generic to give more specific explanations.

You should try to monitor/trace the remote side to find a hint, what went wrong.