Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What would the reason of getting the following error?

Microsoft OLE DB Provider for SQL Server error '80004005'

[DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error.

share|improve this question

A couple of things come to mind:

  1. The name specified for the SQL Server (sqlserver.mydomain.com) does not match the name on the certificate (sqlserver.mydomain.net, for instance).
  2. The certificate is issued by a certificate authority the client doesn't trust.

Are either of these the case?

share|improve this answer
    
Could be quite a few other causes. The built-in SQL provider seems to return messages that are vague. I've seen more descriptive messages using the SQL Native Client. – Greg Askew Apr 3 '10 at 17:48
    
True, but these are the usual two suspects to check for first. – K. Brian Kelley Apr 6 '10 at 21:14
    
We are not using any certificates for web server and SQL server. – shah Apr 7 '10 at 13:35

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.