Created On:  05 January 2012

Problem:

We crashed when using fsmgr and received the return code 10053.  Why is this?

4:35:29 24.05.2006 CCITCP (tcpnet.c $Revision: 4.130 $:0066) 20000 E send(), called in mFt_net_Send_Header, failed with return code 10053.

04:35:29 24.05.2006 CCITCP (tcpnet.c $Revision: 4.130 $:0066) 20000 E send(), called in mFt_net_Send_Header, failed with return code 10053.

04:36:41 24.05.2006 CCITCP (tcpnet.c $Revision: 4.130 $:0066) 20000 E send(), called in mFt_net_Send_Header, failed with return code 10053.

Resolution:

The error 10053 almost always occurs because the remote end fails to respond with an acknowledgement of a data packet that has been sent to it. This error is not generated until retries have been attempted and the lack response to all of them has timed out.

In the really old days of DOS TCP/IP stacks and Windows 16-bit applications the stacks could sometimes get confused and issue this error timed from the initial attempt. Later stacks will time from the send of the final re-try.

In short, the logical or physical link to the server which is listening on the port at the far end of the link has been lost.

It could be a physical issue, or a logical issue such as resuming sessions on a client that had hibernated causing the server to time-out the session and thus ignore the incoming data, or there may be many other possible causes.

Pivotal ID: 22510 Author: Peter Kalfsbeek Created on: