5 replies
by microsloth
Source: Server
Reason: Server closes the connection unexpected (sends reset)
Severity: Server mistake (congestion) 10054 Connection reset by peer.
This can 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. This error is usually seen in conjunction with
error 17824 when on sockets-based connections. For example, an NT client
using the NWLink SPX transport could be selecting data from SQL Server, and
if the network cable is unplugged from the SQL Server machine, you will see error 10054.
An existing connection was forcibly closed by the remote host. This normally occurs if the peer application on the remote host is suddenlystopped, the host is rebooted, or the remote host used a "hard close" (see setsockopt(SO_LINGER)) on the remote socket.
This discussion is closed to new replies.
Trending Community archive posts
Sort by Trending