Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
Solved! Go to Solution.
Hi @yve214 ,
Cause:
When establishing encrypted connections to SQL Server, Secure Channel (Schannel) creates the list of trusted certificate authorities by searching the Trusted Root Certification Authorities store on the local computer. During the TLS handshake, the server sends its public key certificate to the client. The issuer of a public key certificate is known as a Certificate Authority (CA). The client has to ensure that the certificate authority is one that the client trusts. This is achieved by knowing the public key of trusted CAs in advance. When Schannel detects a certificate that was issued by an untrusted certification authority, such as in the above two cases, you get the error message listed in the Symptoms section.
Solution:
If you intentionally use either a certificate from a non-trusted authority or a self-signed certificate to encrypt connections to SQL Server, you can use one of the following options:
For Scenario 1: Add the certificate authority to the Trusted Root Certification Authorities store on the client computer initiating encrypted connection. To do this, complete the Export the server certificate and Install the root certificate authority (CA) on the client machine procedures listed below in that sequence.
The example uses a file named caCert.cer as a certificate file. You must obtain this certificate file from the server. The following steps explain how to export the server certificate to a file:
Click Start and then Run, and type MMC. (MMC is an acronym for the Microsoft Management Console.)
In MMC, open the Certificates.
Expand Personal and then Certificates.
Right-click the server certificate, and then select All Tasks->Export.
Click Next to move past the welcome dialog box of the Certificate Export Wizard.
Confirm that No, do not export the private key is selected, and then click Next.
Make sure that either DER encoded binary X.509 (.CER) or Base-64 encoded X.509 (.CER) is selected, and then click Next.
Enter an export file name.
Click Next, and then click Finish to export the certificate.
Start the Certificates snap-in for MMC on the client computer and then add the Certificates snap-in.
In the Certificates snap-in dialog box, choose Computer account, and then choose Next.
In the Select Computer pane, choose Local computer: (the computer this console is running on), and then choose Finish.
Choose OK to close the Add or Remove Snap-ins dialog box.
In the left pane of MMC, expand the Certificates (Local Computer) node.
Expand the Trusted Root Certification Authorities node, right-click the Certificates subfolder, select All Tasks, and then choose Import.
In the Certificate Import Wizard, on the Welcome page, choose Next.
On the File to Import page, choose Browse.
Browse to the location of the caCert.cer certificate file, select the file, and then choose Open.
On the File to Import page, choose Next.
On the Certificate Store page, accept the default selection, and then choose Next.
On the Completing the Certificate Import Wizard page, choose Finish.
For scenarios 1 and 2: Set Trust Server Certificate setting to true in your client application.
To learn more details ,refer to the official documentation:
And similar question refer:
Did I answer your question? Mark my post as a solution!
Best Regards
Lucien
Hi @yve214 ,
Cause:
When establishing encrypted connections to SQL Server, Secure Channel (Schannel) creates the list of trusted certificate authorities by searching the Trusted Root Certification Authorities store on the local computer. During the TLS handshake, the server sends its public key certificate to the client. The issuer of a public key certificate is known as a Certificate Authority (CA). The client has to ensure that the certificate authority is one that the client trusts. This is achieved by knowing the public key of trusted CAs in advance. When Schannel detects a certificate that was issued by an untrusted certification authority, such as in the above two cases, you get the error message listed in the Symptoms section.
Solution:
If you intentionally use either a certificate from a non-trusted authority or a self-signed certificate to encrypt connections to SQL Server, you can use one of the following options:
For Scenario 1: Add the certificate authority to the Trusted Root Certification Authorities store on the client computer initiating encrypted connection. To do this, complete the Export the server certificate and Install the root certificate authority (CA) on the client machine procedures listed below in that sequence.
The example uses a file named caCert.cer as a certificate file. You must obtain this certificate file from the server. The following steps explain how to export the server certificate to a file:
Click Start and then Run, and type MMC. (MMC is an acronym for the Microsoft Management Console.)
In MMC, open the Certificates.
Expand Personal and then Certificates.
Right-click the server certificate, and then select All Tasks->Export.
Click Next to move past the welcome dialog box of the Certificate Export Wizard.
Confirm that No, do not export the private key is selected, and then click Next.
Make sure that either DER encoded binary X.509 (.CER) or Base-64 encoded X.509 (.CER) is selected, and then click Next.
Enter an export file name.
Click Next, and then click Finish to export the certificate.
Start the Certificates snap-in for MMC on the client computer and then add the Certificates snap-in.
In the Certificates snap-in dialog box, choose Computer account, and then choose Next.
In the Select Computer pane, choose Local computer: (the computer this console is running on), and then choose Finish.
Choose OK to close the Add or Remove Snap-ins dialog box.
In the left pane of MMC, expand the Certificates (Local Computer) node.
Expand the Trusted Root Certification Authorities node, right-click the Certificates subfolder, select All Tasks, and then choose Import.
In the Certificate Import Wizard, on the Welcome page, choose Next.
On the File to Import page, choose Browse.
Browse to the location of the caCert.cer certificate file, select the file, and then choose Open.
On the File to Import page, choose Next.
On the Certificate Store page, accept the default selection, and then choose Next.
On the Completing the Certificate Import Wizard page, choose Finish.
For scenarios 1 and 2: Set Trust Server Certificate setting to true in your client application.
To learn more details ,refer to the official documentation:
And similar question refer:
Did I answer your question? Mark my post as a solution!
Best Regards
Lucien
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Prices go up Feb. 11th.
Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.