monitor
#monitor#10054

10054

This article details various scenarios and provides resolutions for the following errors: A connection was successfully established with the server, but then an error occurre

This article details various scenarios and provides resolutions for the following errors:

A connection was successfully established with the server, but then an error occurred

during the login process. (provider: SSL Provider, error: 0 - An existing connection was

forcibly closed by the remote host.)

A connection was successfully established with the server, but then an error occurred

during the pre-login handshake. (provider: TCP Provider, error: 0 - An existing

connection was forcibly closed by the remote host.)

The operating system error 10054 is raised in the Windows sockets layer. For more information,

see

Windows Sockets Error Codes: WSAECONNRESET 10054.

Secure Channel, also known as

Schannel

, is a

Security Support Provider

(SSP). It contains a set

of security protocols that provide identity authentication and secure private communication

through encryption. One function of Schannel SSP is to implement different versions of the

Transport Layer Security (TLS) protocol. This protocol is an industry standard that’s designed to

protect the privacy of information communicated over the Internet.

The TLS Handshake Protocol is responsible for the key exchange necessary to establish or

resume secure sessions between two applications communicating over TCP. During the pre-

login phase of the connection process, SQL Server and client applications use the TLS protocol

to establish a secure channel for transmitting credentials.

The following scenarios detail errors that occur when the handshake can’t be completed:

Note

Before you start troubleshooting, we recommend that you check the

and go

through the checklist.