Error in SQL server SSL Certificate Connection Since February '24 Release

[Jlindsey00]

Since the Power BI Feb 2024 release, all of the reports in our workspaces have had this SSL error: "The server name provided does not match the server name on the SQL Server SSL certificate ... " Everything was working fine and then all of a sudden this error showed up across our workspaces

Some notes and highlights:

• We use Azure sql databases
• No credentials were changed before this error occured and none have changed since
  • I have double checked the credentials and the server names match both in the desktop and in the service
• The error occurs both on desktop and in the service
• We connect through a sql privatelink (servername.privatelink.database.windows.net) and use a VNET data gateway
  • That gateway has not changed
• We tried disconnecting from the VNET data gateway and using an on-prem gateway, no luck connecting either
• We can connect to our Azure sql dbs with any other method
  • directly in SSMS
  • through excel
  • In web apps we use

Any idea what could be going on?

Thank you!

[muso_Q]

I am still experiencing the same issue at @Anonymous with the issue impacting Dataflows in the Fabric service.
Are there any updates on a solution or workaround yet?

[SuzyThys]

@andrew,

I'm using March 2024 release and the issue not yet fixed 😞

Regards

Suzy

[pineapple]

There is Apr 2024 release now but I still have the same issue. Anyone have it fixed?

[Anonymous]

On another thread, I saw a suggestion to add an environment variable PBI_SQL_TRUSTED_SERVERS.

In my case, I have multiple servers with a similar start (we have -dev, -qa, etc appended on the server name for the different environments). So I included the common prefix and added the * as a like indicator so it would cover all of these servers. 

Variable Name: PBI_SQL_TRUSTED_SERVERS

Value: myservername*

I am not sure if it needs to be a system variable or just a user level. I put it in both places. Someone else in my company just came to me with this issue and that solved it for them as well. 

[Anonymous]

@UOLandrewdale yes, each PC running PBI desktop would need to have this setup I presume. 

[Jlindsey00]

@Anonymous @UOLandrewdale We installed that environmental variable on the machine running the gateway, which was different than the machine that PBI desktop is installed on. We have had no issues in the service since, although the Apr 2024 desktop still will not refresh so we're using Dec 2023.

[Joshrodgers123]

We were able to fix this back in December by:

1) Adding the server names to the system environment variables on the machines running Power BI Desktop.

2) Adding the servers to the SQLTrustedServers entry in the gateway config file. 

All of the details are in the documentation.

https://learn.microsoft.com/en-us/power-query/connectors/sql-server

[Anonymous]

@Jlindsey00  another thing a microsoft tech had me try last month when I had a ticket open was to check the encrypt connections box on the data source settings in power bi desktop. Previously we never did this. Maybe that is also part of the solution, though my user today said he did not need to do that. We are running the April version. I think those are the only two changes I made at the time to my environment.

[Jlindsey00]

@Joshrodgers123 Thank you, we implemented these changes and that is what solved the service issue. We currently have Microsoft diving into the desktop issue. 

@UOLandrewdale I am not sure on that, will need to find out.

@Anonymous Thank you, we have tried checking and unchecking the encryption box, so far neither have worked. We have a ticket with Mircrosoft to dive in to this as well. 

[Anonymous]

Has anyone tried the new May 2024 desktop release to see if it resolves the SSL errors encountered in all versions after the Dec 2023 release?

• Version number: v: 2.129.905.0
• Date published: 5/21/24