title: How to solve Microsoft SQL Server. Error 233. Provider: SSL Provider
body: <p>After the global RansomeWare attack, we updated our <strong>Windows Server 2012 R2</strong> 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:</p>
  
  <blockquote>
    <p>A connection was successfully established with the server, but then
    an error occured during the login process. (Provider: <strong>SSL  Provider</strong>,
    error: 0 - No process is on the other end of the pipe.) (<strong>Microsoft SQL
    Server, Error: 233</strong>)</p>
  </blockquote>
  
  <p>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.</p>
  
  <p>Finally I came across this post: <a href="https://www.sqlservercentral.com/Forums/Topic1810025-3411-1.aspx" rel="nofollow noreferrer">https://www.sqlservercentral.com/Forums/Topic1810025-3411-1.aspx</a> and tried the following solutions:</p>
  
  <ul>
  <li>Enabled Ciphers RC4 128/128, RC4 50/128, RC4 56/128</li>
  <li>Enabled TLS 1.0    Server Protocol</li>
  <li>Disabled SSL 2.0 (Registry does not have SSL 3.0) [also tried<br>
  enabling SSL 2.0 but didn't work as well]</li>
  <li>Enabled TLS 1.0,1.1,1.2 Protocols althogether as well.</li>
  </ul>
  
  <p>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.</p>