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

by APIJunkie 7/31/2008 12:45:00 AM

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.

Currently rated 4.0 by 1 people

  • Currently 4/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

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

Add comment


(Will show your Gravatar icon)  

  Country flag





Live preview

11/19/2008 7:45:43 PM

Powered by BlogEngine.NET 1.2.0.0
Theme by Mads Kristensen

About the author

Name of author

My name is Bacon…James Bacon.

I am an API wars veteran I was wounded by x86 assembly, recovered and moved on to C. I am currently stuck in C++ and sniffing .NET.

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.

E-mail me Send mail


Calendar

<<  November 2008  >>
MoTuWeThFrSaSu
272829303112
3456789
10111213141516
17181920212223
24252627282930
1234567

View posts in large calendar

Recent comments

Authors

Disclaimer

The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

© Copyright 2008

Sign in