Operating system call WSASend failed (error no. 10053) entries are appearing in the Syslog (transaction SM21) periodically, triggered by the user SMDAGENT_<SID>.
Note: SMDAGENT_<SID> user is the key point to check whether this KBA is relevant or not. For other users, it may be caused by other reasons.
The following (or similar) error can be seen in the corresponding work process trace file (dev_w*) in the work directory (LocalDrive\usr\sap\<SID>\SCS<XX>\work):
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]
In the level 2 Gateway trace file (dev_rd), it can be seen that the Gateway closed the connection due to idle monitoring timeout:
GwICheckMonitor: check idle monitor connections (timeout 300 secs)
- SAP system with kernel 72x or 74x, environment which has solman systems installed
- Operating System independent
- Database independent
Operating system call WSASend failed (error no. 10053), SM21, SMDAGENT_<SID>, work process trace file, LocalDrive\usr\sap\<SID>\SCS<XX>\work, WSASend (10053: WSAECONNABORTED: Software caused connection abort, NiIWrite, dev_rd, GwICheckMonitor, monitor connection closed, GwFreeHdlInfoMemory, GwSelClear, NiICloseHandle: shutdown and close, gw/monitor_timeout, instance profile, RZ11 , KBA , BC-CST-GW , Gateway/CPIC , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.