SQL Server: A connection was successfully established with the server, but then an error occurred during the login process

0

Our application sometimes throws out this error:

System.Data.SqlClient.SqlException (0x80131904): 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.) ---> System.ComponentModel.Win32Exception (10054): An existing connection was forcibly closed by the remote host.

The application runs perfectly fine for some time, but just sometimes throws the exception above. Until now it is pretty hard to find the cause of this. Some say that it has to do with the amount of connections, but we have it set at zero and therefor it should be maximized at around 32k connections which we think we do not use.

EDIT: Seen the SSL provider is used and the client OS version is lower than the SQL server OS version I am thinking about the TLS version or cipher suite. I still cannot figure out why the same client is sometimes using a different/incompatible cipher suite or TLS version.

sql
.net
sql-server
.net-core
asked on Stack Overflow Sep 29, 2019 by Kees de Wit • edited Sep 29, 2019 by Kees de Wit

1 Answer

0

I had the same experience when my source os version was windows server 2016 and destination os was windows 2012, after windows update it happened, check windows recent updates.

answered on Stack Overflow Sep 29, 2019 by nimajv

User contributions licensed under CC BY-SA 3.0