Fix for SQL Server SSL Security error ConnectionOpen (SECDoClientHandshake())

by APIJunkie 31. July 2008 00:45

Having an SSL certificate that does not match the server name or expired or is invalid for any other reason can cause this error.

You will receive the above error message when connecting to your SQL server.

Very annoying and hard to find especially if the server hasn't been started for a few weeks since the certificate was installed  ( it seems like the certificate usage is refreshed only when the SQL server service is restarted).

After a little searching, I found an article about this SQL error and how to solve it.

In our case we used a SelfSSL generated certificate.

Note that to fix the problem we had to delete certificates from:

Certificates (local computer)
  Personal
     Certificates

After deleting the certificate you need to stop and start the SQL server service.

Tags:

Microsoft

Comments

7/31/2008 12:50:27 AM #

trackback

Trackback from DotNetKicks.com

Fix for SQL Server SSL Security error ConnectionOpen

DotNetKicks.com

Comments are closed

About the author

Name of author

I was first wounded by x86 assembly, recovered and moved on to C. Following a long addiction to C++ and a short stint at rehab I decided to switch to a healthier addiction so I am now happily sniffing .NET and getting hooked on Silverlight.

I am mainly here to ramble about coding, various API’s, Junkies(me especially) and everything else that happens between coders and their significant other.

  James Bacon