Sometime when you connect to SQL Server you may get communication that may be Client side or Server Side. Here is a list of some common errors with reasons:
Server-side errors109 The pipe has been ended - This generally happen if a named pipes connection is lost during a write.
232 The pipe is being closed - This generally occur if a named pipes connection is lost during a read.
10053 Software caused connection abort - This generally happen if a sockets client (which includes SPX) aborts the connection.
10054 Connection reset by peer - This generally happen if a sockets client (which includes SPX) is actively sending or receiving data to or from SQL Server, and the network connection is lost.
10058 Can't send after socket shutdown - This generally happen if a sockets client (which includes SPX) is actively sending or receiving data to or from SQL Server, and the client application hangs or traps, or is abruptly shut down.
17824 Unable to write to server-side connection - This generally happen when SQL Server attempts to write to a client connection and the write fails. This could be caused by the client computer being hung or shut down, or due to network problems.
17825 Unable to close server-side connection – This generally happen when SQL Server gets an error while attempting to close the network connection to the client.
17832 Unable to read login packet(s) - This generally happen when a client starts to connect, but never successfully completes the attempt because of a client operating system or application failure.
Client-Side Errors
10008 Bad token from SQL Server: data stream processing out of sync - Often caused by an abruptly terminated network connection, which causes a damaged Tabular Data Stream token to be read by the client.
10010 Read from SQL Server failed - The client was reading from the SQL Server network data stream, and the read returned a failure code.
10018 Error closing network connection - The client attempted to close a network connection and the close returned a failure code.
10025 Write to SQL Server failed - The client was writing to the SQL Server network data stream, and the write returned a failure code.
Besides communication errors, You may get some very serious error related to Data. For this you can use some third party software to recover data.
Server-side errors109 The pipe has been ended - This generally happen if a named pipes connection is lost during a write.
232 The pipe is being closed - This generally occur if a named pipes connection is lost during a read.
10053 Software caused connection abort - This generally happen if a sockets client (which includes SPX) aborts the connection.
10054 Connection reset by peer - This generally happen if a sockets client (which includes SPX) is actively sending or receiving data to or from SQL Server, and the network connection is lost.
10058 Can't send after socket shutdown - This generally happen if a sockets client (which includes SPX) is actively sending or receiving data to or from SQL Server, and the client application hangs or traps, or is abruptly shut down.
17824 Unable to write to server-side connection - This generally happen when SQL Server attempts to write to a client connection and the write fails. This could be caused by the client computer being hung or shut down, or due to network problems.
17825 Unable to close server-side connection – This generally happen when SQL Server gets an error while attempting to close the network connection to the client.
17832 Unable to read login packet(s) - This generally happen when a client starts to connect, but never successfully completes the attempt because of a client operating system or application failure.
Client-Side Errors
10008 Bad token from SQL Server: data stream processing out of sync - Often caused by an abruptly terminated network connection, which causes a damaged Tabular Data Stream token to be read by the client.
10010 Read from SQL Server failed - The client was reading from the SQL Server network data stream, and the read returned a failure code.
10018 Error closing network connection - The client attempted to close a network connection and the close returned a failure code.
10025 Write to SQL Server failed - The client was writing to the SQL Server network data stream, and the write returned a failure code.
Besides communication errors, You may get some very serious error related to Data. For this you can use some third party software to recover data.
I work for Dell and I liked reading through your blog on SQL server. It's very useful to learn about the common communication errors associated with SQL servers. Thanks for sharing the blog here.
ReplyDelete