Forum Discussion
Microsoft SQL: A connection was successfully established with the server, but then an error occurred
Hi. I am getting the following error on ALL of my power bi desktop packages:
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 authority that is not trusted.)
I've seen posts about this and people recommending using an MSFT account to log into the SQL server. However, I use a VPN directly to the SQL server with database credentials. Any ideas? Thx
13 Replies
I just solved the issue by creating a self signed certificate on the database server.
I used the IIS method: 7 ways to create self-signed certificates on Windows (passwork.pro)
Worked like a charm!
ugh...I don't have access to the db server to create the cert. So frustrating, I've been connecting for more than a year and all of the sudden this happened. I've got to think its something with the latest Power BI desktop update.
Hi JaviGoldstein ,
Please try updating Power BI Desktop to the latest version.
Other than that please refer to the replies to this post, he may be helpful to you.Best Regards,
Neeko Tang
If this post  helps, then please consider Accept it as the solution  to help the other members find it more quickly.
This worked for me. Thanks a lot!
I am experiencing a similar issue. I have connected in PBI Desktop to an azure based SQL server. Encryption box is not checked. Today when I refresh the dataset locally in PBI desktop, I am getting this issue. This has never happened before. I have tried changing encryption to be turned on and off (which it was originally). I have also tried using Microsoft account and also databse credentials and neither works. I can connect in SSMS to the same database.
- Greg_Deckler
Community Champion
Anonymous Did this just start happening with the Feb update? You could check the Issues forum here:
https://community.powerbi.com/t5/Issues/idb-p/Issues
And if it is not there, then you could post it.
If you have Pro account you could try to open a support ticket. If you have a Pro account it is free. Go to https://support.powerbi.com. Scroll down and click "CREATE SUPPORT TICKET".Greg_Deckler it just started for me in the lastest update. I went back to the Oct 2023 version and everything works fine. 😕
- Greg_Deckler
Greg_Deckler unfortunately, that doesn't work for me. The really strange thing is that I can connect via SSMS but not via PowerBI.
Experiencing the same issues, since yesterday ...
jmaloneResolver III
This is happening to me as well. It's absolutely something with the February 2024 desktop release. I also installed the latest gateway release (Feb 2024) and had the same issue with the service. Had to roll back to previous versions on each.
I tried the recommended fixes with the ado.net (use FQDN, check server certificate), but nothing is working. Very frustrating.
I opened a ticket with Microsoft a couple of weeks ago about this issue. They just called to inform me that this issue exists in the Feb version and will be resolved with the March release. In the meantime, they advised to roll back to the December 2023 version which I have done and that is working. However, I did have to get my local IT assistance to install the December 2023 version from the manual install because I needed admin rights to install on my work computer. Usually I use the store version which has no option to roll back.
-----------------------
UPDATE: Right after I posted this a different Microsoft tech just called me and said a newer Feb version number was released 3/2 and does work. But you have to check encrypt connection on your data source settings. I tried this on the call and it did work. Apologize for the confusion, two different techs with different information.
This just started happening with me out of the blue. It looks like my system was just updated with June 2024 version. Looks like they haven't fixed the problem. I tried adding environment variable to my computer system but that didn't resolve it. IT is contacting Microsoft to resolve.
