Operating system call connect failed (error no. 111 )

[Former Member]

In my ECC-PRD System, there are lots of system log error :Operating system call connect failed (error no. 111 ).

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 111
Name for errno number E_UNKNOWN_NO
The meaning of the value stored in 'errno' is
platform-dependent.
The value which occurred here is unknown to the SysLog system.
Either there is an incorrect error number in the SysLog message, or
the tables TSLE2 or TSLE3 are not completely maintained.

Do anybody see it?

[Former Member · Accepted solution]

When the jobs of MRP start to run , they will run in parallel manner. We define Parallel Processing in MRP , the number of server is 10. But two servers are not startup, when one of the server try to connect to the server which is not started, it issue the error log. Then we delete the two servers in spro-->Production-->Material Requirements Planning -->Define Parallel Processing in MRP. Now it is ok .

[Former Member]

According to a preliminary inspection, when the dia work processes were very busy, then the error log was issed. I suspect that the reason is the dia wps are too little.