How to solve Microsoft SQL Server. Error 233. Provider: SSL Provider
After much tinkering I found out that the Windows update have modified the TLS and SSL settings wrong. I had to specifically make changes to the Cipher Suits and Protocols in the registry in order to make it work and now we can log in to SSMS successfully (both locally and remote log in). So the specific changes I have made to registry is as follows:
Changes in Schannel:: (Inlcuding Client Side Protocols)
Protocols Enabled: Multi-Protocol Unified Hello, PCT 1.0, TLS 1.0
Protocols Disabled: SSL 2.0, SSL 3.0, TLS 1.1, TLS 1.2
Ciphers Enabled: NULL, DES 56/56, RC2 40/128, RC2 56/128, RC2 128/128, RC4 40/128, RC4 56/128, RC4 64/128, RC4 128/128, Triple DES 168, AES 128/128, AES 256/256
Hashes Enabled: MD5, SHA, SHA 256, SHA 384, SHA 512
Key Exchanges Enabled: Diffie-Hellman, PKCS, ECDH
Cipher Suite Changes::
Disabled: SSL_CK_RC4_128_WITH_MD5, SSL_CK_DES_192_EDE3_CBC_WITH_MD5
Enabled: Everything else realted to TLS
To achieve this easily (changes to security and modification of registry) I also used this tool (IISCrypto): https://www.nartac.com/Products/IISCrypto
Do make sure that each cipher or protocols mentioned here are specifically enabled or disabled, or else the issue won't be resolved.
Hope this helps!
Somdip Dey
CEO @ Nosh Technologies Artificial Intelligence Scientist @ University of Essex TED speaker Love and Hate relationship with Technology because it makes us lazy but improves our lives a lot at the same time. So focusing on 'How technology can improve lives?!' ###Drink Tea and Code ;) ###Always busy but I am happy to help whenever I have some spare time. You can also follow me on here on MSDN (Microsoft Developer Network) Oh, I also happen to have a personal website: http://somdipdey.co.uk/ We coders sometimes love to boast our coding skills and so I will leave it here anyway .... Top 13% for C# in United Kingdom: Top Users Per Country & Tag Top 4% for C# in India Top 5% for C# Globally: Top Users For A Tag Care about Performance and Optimisation of your Software? I know you do. Why not use this Nuget Package to track your system performance (in CSharp)?! Some of my free-to-use codes/programs are also available on GitHub. My Favourite Top Queries on Stack Exchange: ###Find Stack Overflow Users In Your City (with user-links) With Their Score For One Particular Tag ###Find Top 30K Stack Overflow Users (with user-links) With Their Score Globally For One Particular Tag ###Find A Stack Overflow User's (with user-links) Score For One Particular Tag - Globally In case you are interested on my Research Contributions in different topics of Computer Science please have a look at My Google Scholar Profile Or My ResearchGate Profile
Updated on July 05, 2022Comments
-
Somdip Dey almost 2 years
After the global RansomeWare attack, we updated our Windows Server 2012 R2 only to find out that our SQL Server Management Studio (SSMS) stopped working. Whenever we try to connect to SSMS locally or remotely it provides us the following Error:
A connection was successfully established with the server, but then an error occured during the login process. (Provider: SSL Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)
I tried logging in with "Windows Authentication" and the error was same. I also tried solutions for similar SQL Error 233 issues but with no result. All the SQL Error 233 issues I came across on Stack Overflow are related to Shared Memory provider but not SSL Provider.
Finally I came across this post: https://www.sqlservercentral.com/Forums/Topic1810025-3411-1.aspx and tried the following solutions:
- Enabled Ciphers RC4 128/128, RC4 50/128, RC4 56/128
- Enabled TLS 1.0 Server Protocol
- Disabled SSL 2.0 (Registry does not have SSL 3.0) [also tried
enabling SSL 2.0 but didn't work as well] - Enabled TLS 1.0,1.1,1.2 Protocols althogether as well.
But none of them worked and we still couldn't log in to SQL Server Management Studio. Any help or suggestion is highly appreciated. Thank you in advance.