Potential errors include:
- 17832 Unable to read login packet(s)
- 17825 Unable to close server-side connection
- 17824 Unable to write to server-side connection
- 10058 Can't send after socket shutdown
- 10054 Connection reset by peer
- 10053 Software caused connection abort
- 1608 A network error was encountered while sending results to the front end
- 232 The pipe is being closed
- 109 The pipe has been ended
- 10008 Bad token from SQL Server: datastream processing out of sync
- 10010 Read from SQL Server failed
- 10018 Error closing network connection
- 10025 Write to SQL Server failed
SQL Server's use of this medium is somewhat analogous to two parties who purchase and use telephones. The telephones on each end of a connection rely on the telephone network to establish and maintain a reliable connection. Problems such as static, poor quality, lost connections and so forth can only rarely be traced to the user's telephone equipment. Most of the time, any connection problem must be resolved in the telephone network connecting the two users.
Similarly, most of the errors listed in this article are only manifestations at the SQL layer of an underlying connection loss. They do not by themselves indicate a problem with SQL Server. The connection loss is commonly caused by the client workstation rebooting, in which case the server would report a loss of connection to the client. Client application errors or system errors, such as running out of memory, can cause the client program to hang or abnormally terminate, which will also cause the server to report a connection loss. The client system can be debugged to check for this. These errors can also be caused by various hardware and software problems in the network connecting the client and the server. Successful problem resolution in these cases depends on acknowledging the network, application, or system nature of the problem and focusing efforts on that area.
Successful techniques include determining what users were doing on the client computers at the time of the problem, running the client application in a debugger, and using a network analyzer, such as the Network General Sniffer or Novell Lanalyzer, to monitor the traffic between client and server during the error.
Additional details on these errors are provided below.
Client-Side ErrorsThese DB-Library (DB-Lib) errors often correspond to the above server-side errors. They frequently indicate a network connection loss from the perspective of the client. This can happen if the network itself fails, the network connection or SQL process is terminated by an administrator, or the server-side SQL process aborts. You can easily check for it being a SQL problem by inspecting the SQL Server error log for an access violation or similar error. If this is not discovered to be the case, then you should pursue the problem as a network, network configuration, system or application problem.
If you see a server-side communications error corresponding in time to when a specific client-side communication error occurred, this often means a network problem.
Article ID: 109787 - Last Review: Jun 13, 2008 - Revision: 1