Symptom
Operating system call WSASend failed (error no. 10053)
This error logged in SM21 log periodically with user SMDAGENT_<SID>.
*Note*
SMDAGENT_<SID> user is the key point to check whether this KBA is the case or not.
For other users, it may be caused by other reasons.
Error in the corresponding dev_w50 trace:
M ***LOG Q0I=> NiIWrite: P=127.0.0.1:3300; L=127.0.0.1:<port>: WSASend (10053: WSAECONNABORTED: Software caused connection abort) [nixxi.cpp 4615]
M *** ERROR => NiIWrite: SiSendV failed for hdl 16/sock 2036
If you raise trace level 2, you can see gateway closed the connection due to idle monitoring timeout in dev_rd trace:
GwICheckMonitor: check idle monitor connections (timeout 300 secs)
GwICheckMonitor: monitor connection closed (idle for 317 secs)
GwFreeHdlInfoMemory: free 0000000008E173D0 (data)
GwSelClear: clear RWC for hdl 167
NiICloseHandle: shutdown and close hdl 167/sock 2004
Read more...
Environment
SAP system with kernel 72x or 74x, environment which has solman systems installed.
Keywords
SMDAGENT, 10053, gateway, idle time out , KBA , BC-CST-GW , Gateway/CPIC , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.