INF: How to Troubleshoot Communication Error 17824

ID: Q165158


The information in this article applies to:


SUMMARY

In some circumstances, the following communication errors are logged in the SQL server error log:

Error : 17824, Severity: 10, State: 0
Unable to write to ListenOn connection '<servername>', loginname '<login
ID>', hostname '<hostname>'.
OS Error : 64, The specified network name is no longer available.

Error 1608 A network error was encountered while sending results to the front end

Other relevant errors may follow, depending on the network library used for the connection. In case of Named Pipes connections, errors "232 The pipe is being closed" or "109 The pipe has been ended" may be logged. In case of sockets based connections (TCP/IP or IPX/SPX), errors "10054 Connection reset by peer" or "10053 Software caused connection abort" may be logged.

These errors indicate that the connection between the client and SQL Server was broken for some reason while SQL Server was writing data to the front end. Depending on the circumstances, a certain number of these errors may be normal, and eliminating them is not always necessary. If you do not receive any end user complaints or experience general connection problems, you can ignore these errors.


MORE INFORMATION

Error 17824 "Unable to write to ListenOn connection" indicates that problems have occurred while SQL Server attempted to write to a client connection and failed. These communication problems may be caused by network problems, or if the client computer has stopped responding or been restarted. For more information regarding other communication errors, please refer to the following article in the Microsoft Knowledge Base:

Q109787 : INF: SQL Communication Errors 17832, 17824, 1608, 232, and 109

Error 17824 does not always indicate a network problem. The following are the most common situations under which the error 17824 is generated, along with the corresponding troubleshooting procedures.
For more information on detecting and resolving blocking problems, please refer to the following article in the Microsoft Knowledge Base:
Q162361 : INF: Understanding and Resolving SQL Server Blocking Problems

If you have checked all of the above points and the problem still persists, contact SQL Server support for further troubleshooting assistance.

Additional query words: Internet IIS WAN symmetric multiprocessor SEM Advanced options


Keywords          : kbtshoot kbusage SSrvGen 
Version           : 6.5 6.0 4.21a
Platform          : WINDOWS 
Issue type        : kbhowto 

Last Reviewed: April 9, 1999