SSMS stopped connecting to the server

Question

SSMS stopped connecting to the server

Antony 1

I've just installed the latest Windows 11 update and SSMS has stopped connecting to SQLEXPRESS Server 2005 with error

TITLE: Connect to Server

------------------------------

Cannot connect to ..*.10\SQLEXPRESS, 1049.

------------------------------

ADDITIONAL INFORMATION:
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.) (Microsoft SQL Server, Error: 10054)
For help, click: https://learn.microsoft.com/sql/relational-databases/errors-events/mssqlserver-10054-database-engine-error

------------------------------

An existing connection was forcibly closed by the remote host

------------------------------

BUTTONS:
OK

------------------------------

If i follow the abouve ling it shows "404 - Page not found"

NOT updated systems are still able to connect without any issues. How can I fix this problem?

Versions:
SQL Server Management Studio 15.0.18424.0
SQL Server Management Objects (SMO) 16.100.47021.0+7eef34a564af48c5b0cf0d617a65fd77f06c3eb1
Microsoft Analysis Services Client Tools 15.0.19750.0
Microsoft Data Access Components (MDAC) 10.0.22621.819
Microsoft MSXML 3.0 6.0
Microsoft .NET Framework 4.0.30319.42000
Operating System 10.0.22621

Windows specification:
Edition Windows 11 Pro
Version 22H2
Installed on ‎10/‎11/‎2022
OS build 22621.819

Ryan Waddell 66 Reputation points

2022-11-18T17:06:59.847+00:00

I'm getting the same 10054 error - but I get it operating-system wide. We have a SQL2008 R2 (SP3) server that I could connect to fine prior to installing the Windows 11 22H2 update. But as soon as I updated to that, I can no longer connect via ANY method (SSMS, installed Toad to try it out, my local build of our app, even just setting up an ODBC connection in Windows itself). So it's pretty clear that SOMETHING in the 22H2 update broke things, and I'm guessing it's somehow TLS/SSL related but I'm not sure what changed in 22H2 that could be causing this.

I can connect to a SQL2019 database fine, but our current prod environment is still on SQL2008 and it's not gonna get updated any time soon, as that's a massive undertaking to make sure everything works properly.
Seeya Xi-MSFT 16,586 Reputation points

2022-11-23T08:33:17.357+00:00

Hi @Antony ,

Hope everything goes well. We have not received a response from you. Just very concerned if your problem is solved. If there are new progress, you can also post it.

Best regards,
Seeya

7 answers

Your answer

Ryan Waddell 66 Reputation points

2022-11-18T17:06:59.847+00:00

I'm getting the same 10054 error - but I get it operating-system wide. We have a SQL2008 R2 (SP3) server that I could connect to fine prior to installing the Windows 11 22H2 update. But as soon as I updated to that, I can no longer connect via ANY method (SSMS, installed Toad to try it out, my local build of our app, even just setting up an ODBC connection in Windows itself). So it's pretty clear that SOMETHING in the 22H2 update broke things, and I'm guessing it's somehow TLS/SSL related but I'm not sure what changed in 22H2 that could be causing this.

I can connect to a SQL2019 database fine, but our current prod environment is still on SQL2008 and it's not gonna get updated any time soon, as that's a massive undertaking to make sure everything works properly.
Seeya Xi-MSFT 16,586 Reputation points

2022-11-23T08:33:17.357+00:00

Hi @Antony ,

Hope everything goes well. We have not received a response from you. Just very concerned if your problem is solved. If there are new progress, you can also post it.

Best regards,
Seeya

Answer 1

Maire Olivier 21

Got the same issue on a Windows 11 computer trying to connect to an old SQL 2005 DB.
It looks like some ciphers are disabled on Windows 11 and prevent the connection with the Database.

In Powershell (as admin) after running the following command, I could connect to the DB.
Hope this helps.

Enable-TlsCipherSuite -Name "TLS_RSA_WITH_3DES_EDE_CBC_SHA"

Vishal Himane 0 Reputation points

2024-12-20T11:28:01.3+00:00

This command run resolved issue at my end.

Thank you Maire Olivier.

Thanks

Vishal

Answer 2

Hi @Antony ,

SQL Server Management Studio 15.0.18424.0

You can try to install the latest GA version: SSMS 18.12.1
Use different authentication methods to troubleshoot. sqlcmd can help you troubleshoot if SSMS has a problem.
In addition, please check the errorlog of SQL Server. If you see errors related to misaligned sector IOs, please refer to this thread:
SQL Server not connected after windows 11 update

Best regards,
Seeya

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

Antony 1

Hi @Seeya Xi-MSFT ,

Thank you for the reply. Both v8.12.1 and v19.0 Preview 3 show the same error. Connection is established, but then remote side breaks it.

Seeya Xi-MSFT 16,586 Reputation points

2022-11-18T06:17:41.043+00:00

Please refer to this link about Operating Systems Compatible with SQL Server 2005. As JingyangLi said, you need update your SQL Server.
Antony 1 Reputation point

2022-11-18T08:47:53.94+00:00

I'm not able to update SQL Server because it is running under Windows XP. We have a network with 45 XP computers and SQL Server 2005

Answer 4

Jingyang Li 5,896 Volunteer Moderator

SQLEXPRESS Server 2005 is very old.
Don't know how to reproduce the issue you are running into today.

By the way, SQL Server 2022 was released yesterday.

Answer 5

Antony 1

Any more options to fix SSL related problem?

Share via

SSMS stopped connecting to the server

7 answers

Your answer