2

During my SQL Server 2014 Enterprise installation efforts, I encountered an error near the end of the install that has prevented completion.

A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.).

There is currently no cert on the server so it looks as though SQL Server has generated a self signed cert to connect with, but isn't being trusted.

Note that all this is happening before the install is complete, so configuration manager isn't available yet. My thought is to turn encryption off, but with no config manager, I am not sure where there may be a config file for the install somewhere that I can edit. Or maybe I would need to put a trusted cert on the server, but without configuration manager fully available, there isn't a way to tell SQL Server to use this the trust cert.

  • Having no idea what "the server" is that the error message is talking about, or what setup could possibly need to use SSL for, can you give us a better idea of what features you selected? If your answer is "all of them," go back to the beginning, and select only the features you need. It's possible this is some connection attempt required by a feature you're not even going to use. – Aaron Bertrand Aug 24 '15 at 19:25
  • I only selected the database engine features. Also the server is Windows 2008 R2. – Steve DBA Aug 24 '15 at 19:35
  • Did you look at this or this or this? – Aaron Bertrand Aug 24 '15 at 19:40
1

Tom Li- MSFT described a solution to what sounds like your problem, but his solution was for SQL Server 2008. (But just how much has the installer been improved since then?)

https://social.msdn.microsoft.com/forums/sqlserver/en-US/f009e660-503a-4569-a92d-9cc2ef790ca3/install-failure-certificate-chain-trust

Key points from his post include:

  1. This certificate is used as a mechanism to protect SQL Server's login information(including password) when using SQL authentication.

    By default this self-signed certificate should only affect the login information and only when using SQL authentication.

    Edit: My certificate name usually matches the SQL Server's login account.

  2. Export the certificate and delete it by using "certmgr.msc". Then run "setup.exe" to install SQL Server 2008 again.

    You also can add this certificate to the Trusted Root Certification Authorities store to solve this issue. In order to do this, please execute:

    Certutil -Addstore -f Root <File.Cer>

  3. Run "cliconfg.exe" from a Windows run dialog to determine that you did not check "Force protocol encryption".

  • In step2 of exporting and deleting the cert. I am not sure of what the naming convention of a MSSQL self signed cart would be. Any ideas? – Steve DBA Aug 24 '15 at 20:06
  • do you know what a SQL self signed certificate could be identified as. I'm not exactly able to identify it in the cert store. – Steve DBA Aug 25 '15 at 17:21

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.