Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Since February, I can no longer connect my Power BI Desktop report on my client to the MSSQL database and I get the following error:
Microsoft SQL: 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 untrusted certification authority).
It can be connected directly to the source on the server and everything still worked until January. Apparently the security settings have been changed. I have already tried all the settings regarding encryption and data protection level in Power BI Desktop. The problem seems to be due to a self-signed certificate on the SQL Server. That is no longer trusted. The settings in the registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQLServer\SuperSocketNetLib) under are unfortunately not so easy to implement on the client and I am looking for another solution. Is there a setting somewhere where I can go back to the old security settings? It would be great if you could help me and preferably also send me a screenshot where I can make the adjustment. Many thanks and best regards Franzi
Solved! Go to Solution.
Hi @Franzi710 ,
Please try the method in the screenshot below:
If the above solution does not resolve the issue or if you're looking for a more permanent solution, consider procuring a certificate from a trusted Certificate Authority or updating the existing self-signed certificate to ensure it's trusted by the client machines. This process involves generating a new certificate and configuring SQL Server to use it.
Best Regards,
Dino Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Unfortunately, that didn't help. We have now set up an ODBC connection and linked the report to it, which worked. There are too many other things connected to the SQL server and the certificate. Thanks for your answer anyway.
Hi @Franzi710 ,
Please try the method in the screenshot below:
If the above solution does not resolve the issue or if you're looking for a more permanent solution, consider procuring a certificate from a trusted Certificate Authority or updating the existing self-signed certificate to ensure it's trusted by the client machines. This process involves generating a new certificate and configuring SQL Server to use it.
Best Regards,
Dino Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
105 | |
94 | |
75 | |
63 | |
62 |
User | Count |
---|---|
137 | |
105 | |
104 | |
80 | |
63 |