Certificate Chain Not Trusted Error affecting PBI only, can't switch credentials to Windows.

[Azam_]

Hi, I'm getting the following error when connecting to a SQL server running on an Azure VM.

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.)

Previous posts have said the fix could be either switching credientials to windows (which I can't do as I use the database login method with a simple username and password), or making sure I am using the most recent version of PowerBI (which I am).

The refresh to this SQL database used to work fine 3 weeks back, and no updates have been made to the dashboard (or the SQL database as far as I'm aware). When trying to connect through MySQL with the same credentials it works fine, as far as I'm aware the issue is localised to PowerBI.

Any help would be greatly appreciated.

[Roy_tap]

Hi,

Does anyone has the link to the December 2023 version as we are currently encountering this issue with April 2024 version?

The dataset is still working perfectly yesterday without any issue and out of the blue, the connection issue just strike without any warning..... Have microsoft managed to resolve this already

Thanks in advanced.

[1powerbiaccount]

I have encountered the same issue. There are two solutions (workarounds)

1) Roll-back to Dec 2023 (Micrsoft support has confirmed this to me)

2) I was able to bypass the error by inserting a space before the port# in connection string (connecting to SQL):
old connection: SV944007\CR1001,27692

modified conneciton: SV944007\CR1001, 27692

Note - if you have an alreay published old connection string, it wont be recognized in the Gateway. You have to create a new gateway connection with the modified connection string.

please try this and confirm if this works

[Azam_]

I spoke to microsoft support and they told me it's an issue that they're aware of. A workaround can be found here:

https://learn.microsoft.com/en-us/power-query/connectors/sql-server#sql-server-certificate-isnt-trus...

However this did not work for me, but may be helpful to other people. Support couldn't confirm when the issue would be resolved but I'm hoping the March 2024 PowerBI desktop release fixes the issue.

[plynn]

Workaround: I downloaded the December 64-bit version and the problem disappeared.... 
https://learn.microsoft.com/en-us/power-bi/fundamentals/desktop-latest-update-archive?tabs=powerbi-d...

[1powerbiaccount]

I have the same issue with March 202r version. Miscrsoft's workaround solution was to rollback to DEC 2023.

[Azam_]

Can confirm this workaround works, however it is not ideal as Microsoft guidance is to use the newest version of PowerBI as it is the only one technically supported.

[1powerbiaccount]

I have encountered the same issue. There are two solutions (workarounds)

1) Roll-back to Dec 2023 (Micrsoft support has confirmed this to me)

2) I was able to bypass the error by inserting a space before the port# in connection string (connecting to SQL):
old connection: SV944007\CR1001,27692

modified conneciton: SV944007\CR1001, 27692

Note - if you have an alreay published old connection string, it wont be recognized in the Gateway. You have to create a new gateway connection with the modified connection string.

please try this and confirm if this works

[plynn]

Yes, it works. You don't have much choice until someone provides a resolution for the Feb 24 version.

[plynn]

I'm also experiencing the same error for new and existing reports since the latest Power BI Desktop version update (2.126.927.0 64-bit (February 2024))

[Azam_]

Yes will be happy to, what more information do you require? Unfortunately I cannot share the file due to privacy issues and do not have admin rights over the SQL server.

I also just downgraded my PowerBI to the December 2023 version (I was previously using the February 2024 version), and the error no longer happened. Are you aware of any updates that have been made to PowerBI in the newest release related to handling of certificates when trying to connect to a SQL Server?

[v-shex-msft]

Hi @Azam_ ,

Can you please share some more detail information about this issue? They should help us clarify your scenario and test to troubleshoot.

How to Get Your Question Answered Quickly  

Regards,

Xiaoxin Sheng