on 08-01-2008 7:22 AM
Dear All,
I m getting error in sm21 Operating system call connect failed (error no. 10061)in evry half an hrs.The job log is below...
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 10061
Name for errno number WSAECONNREFUSED
No documentation available for error WSAECONNREFUSED
Note :When i m checking the background job i found a new job which is runninmg there.The log is below.
ARFC:C0A810D40938488722D748C2 CORETEAM Finished 01.08.2008 10:52:25
ARFC:C0A810D40938488722D748C2 CORETEAM Finished 01.08.2008 11:08:24
ARFC:C0A810D40938488722D748C2 CORETEAM Finished 01.08.2008 11:24:25
ARFC:C0A810D4094048872303544A CORETEAM Released
ARFC:C0A810D4094048872303544A CORETEAM Finished 01.08.2008 10:52:25
ARFC:C0A810D4094048872303544A CORETEAM Finished 01.08.2008 11:08:24
ARFC:C0A810D4094048872303544A CORETEAM Finished 01.08.2008 11:24:25
ARFC:C0A810D410A8489299DA4DE9 CORETEAM Released
ARFC:C0A810D410A8489299DA4DE9 CORETEAM Finished 01.08.2008 10:52:25
ARFC:C0A810D410A8489299DA4DE9 CORETEAM Finished 01.08.2008 11:08:24
ARFC:C0A810D410A8489299DA4DE9 CORETEAM Finished 01.08.2008
plz suggest me what is this and how to rectify this......
Regard's
Hi Ashok,
the problem you are facing is OS and DB dependent. Let us know what is your OS and on What DB you are working.
Also let us know the sap ver you're using.
Check for any gateway/netwrok/RFC issues.
As a quick note, search in the market place for notes with the string "Operating system call connect failed". You will find lots of notes and you segregate based on your os/db.
Regards,
Srihari
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Ashok,
check the dev_rfc log file, check any of the program was using any RFC (for example SM_P14CLNT500_READ RFC)
and check the RFC Target Host , if it is different change to the correct RFC target host( if you are using virtual host).
It will assure that you wont face this error again.
Let me know if still issue exists.
Thanks
kishore
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
10 | |
10 | |
8 | |
7 | |
7 | |
7 | |
6 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.