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!

[SuzyThys]

I tried yesterday but still the same issue 😞

[Anonymous]

Thanks for your input!

If anyone else has tried, please post your results...thanks!

[gavinfb]

May version of PBI and still getting the same error.

Any update from the engineers?

[Archyve]

Hello, 

I have a data synchronization problem since saturday for all of my Power BI files connected in web service.

I thought the problem was solved with may release but it seems it hasn't been fixed unless it's a different problem affecting our data synchronization.
Here below is the full error code I've experienced :

Erreur de source de données{"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"Microsoft SQL : A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - Le certificat reçu a expiré.)"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Class","detail":{"type":1,"value":"20"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind","detail":{"type":1,"value":"SQL"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath","detail":{"type":1,"value":"srvsem01\\x3v12;x3v12"}},{"code":"Microsoft.Data.Mashup.ValueError.ErrorCode","detail":{"type":1,"value":"-2146232060"}},{"code":"Microsoft.Data.Mashup.ValueError.Message","detail":{"type":1,"value":"A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - Le certificat reçu a expiré.)"}},{"code":"Microsoft.Data.Mashup.ValueError.Number","detail":{"type":1,"value":"-2146893016"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}},{"code":"Microsoft.Data.Mashup.ValueError.State","detail":{"type":1,"value":"0"}}],"exceptionCulprit":1}}} Table: Accounting Third Party

Does anyone found any clue to circumvent this problem please?

[CBO2404]

I have tried the June release and it is still not resolved. 🙄

Does anyone have an idea how long it will take to resolve this? In which release? And what is a possible solution (besides using the December release)?

[Joshrodgers123]

Have you tried the fix in the Power Query SQL Server documentation?

This worked for me when I started getting this issue.

[Anonymous]

We added an Environmental Variable on the local machine of the users using Power Bi Desktop. Adding the variable allowed us to move to the new June release!

Variable Name: PBI_SQL_TRUSTED_SERVERS
Variable Value: SQL Server Name <--enter your sql server name here

For multiple servers, you need to use a comma and space (, ) to separate each server in the value field. You can also use an asterisk (*) for servers of the same name.

Variable Name: PBI_SQL_TRUSTED_SERVERS
Variable Value: SQL Server Name01, SQL Server Name02, SQL Server Name03

or

Variable Name: PBI_SQL_TRUSTED_SERVERS
Variable Value: SQL Server Name*

Hope that helps!