Network Management

Cannot connect to the SQL server. The certificate chain was issued by an authority that is not trusted.

This article is about fixing the SSL error message during Configuration Wizard.

First published date

5/19/2020 1:51 PM

Last published date

2/8/2025 12:22 AM

Overview

The following error appears when SSL is enabled on the client's SQL Configuration Manager.

Cannot connect to the SQL server. The original error is: A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error:0 - The certificate chain was issued by an authority that is not trusted.)
 
 
image.png

Product section

Orion Platform

Cause

  • SSL encryption is enabled on the SQL server and/or the certificate on the SQL server is not trusted by the Polling Engine.
  • Authentication by SQL server is not enabled.
  • Multiple SQL Instances.

Resolution

Configuring the clients to use trust encrypted SQL connections

You should export the certificate from your SQL Server and install it on the client computer to establish the encryption.

1. Open the MMC Certificates Snap-in.
2. Right-click the Certificate, point to All Tasks and then click Export.
3. Complete the Certificate Export Wizard, storing the certificate file in a selected location.
4. Copy the certificate to the client's computer.
5. Use the MMC Certificates Snap-in on the client computer to install the exported certificate file.
6. In the SQL Server Configuration Manager right-click SQL Server Native Client Configuration, and then click Properties.
7. On the Flags tab, select Yes in the ForceEncryption box, then click OK.

(© 2020 MSSQLTips, available at https://www.mssqltips.com/, obtained on May 19, 2020)


Configuring SQL Server to accept encrypted connections

You can configure SSL using the SQL Server Configuration Manager. First, you should run SQL Server Configuration Manager under the SQL Server service account. The only exception is if the service is running as LocalSystem, NetworkService, or LocalService, in this case, you can use an administrative account.

1. Expand SQL Server Network Configuration and right-click on Protocols for <YourMSSQLServer>, then click Properties.
2. On the Certificate tab, select the certificate you would like to use.
3. On the Flags tab, select Yes in the ForceEncryption box, then click OK.
4. Restart the SQL Server service.

image.png

You can also encrypt the connection from SQL Server Management Studio:

1. Click Options in the Connect to Server dialog.
2. On the Connection Properties tab, tick the Encrypt connection checkbox.

How to Configure SSL encryption in SQL server (© 2021 Edgewood Solutions, LLC, available at https://docs.stelodata.com. obtained on February 27, 2024)


Configuring SQL Server Authentication

The issue could be presented when SQL server Authentication, is set as Windows Authentication Mode Only, and without SQL Server Authentication.

1. Open SQL Server Management Studio (SSMS) and right-click on SQL Server, and select Properties
2. Under Server properties. Select from the Page Colum the option: Security
3. Validate values under Server Authentication, and if you are going to use a SQL account instead of a Windows account to connect to SQL Server, during the configuration Wizard. then select the option: SQL Server and Windows Authentication mode, Click OK to save options, and Restart SQL Server will be required. 

Note: Issue could be presented when migrating a database. or new installations.


Multiple SQL Instances

If there are multiple SQL Instances, enter the <SQLServerName\InstanceName> in the Configuration Wizard.

image.png

image.png

Create Orion DB user using Configuration Wizard

In this article you will learn the process or requirements for SQL credentials during Orion Configuration wizard to connect the application with SQL server and logic behind the process.

Why do I need SQL SA level account credentials for Configuration Wizard 

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.