Skip to main content
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.

Jlindsey00

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

Submitted by on ‎02-26-2024 06:47 AM

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

Screenshot 2024-02-26 at 9.37.14 AM.png

 

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!

Status: Accepted

Hi @Jlindsey00 

We have seen on the internal platform that other engineers have reported this issue and submitted it. 

The engineers on the product team are now aware and will do their best to resolve the issue. I will update here if there is any progress, so please be patient!

 

Best Regards,
Community Support Team _ Ailsa Tao

See more ideas labeled with:
22 Comments (22 New)
Comments
rbrocks
Advocate IV
Advocate IV
‎04-17-2024 08:21 AM

@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
Regular Visitor
‎04-17-2024 08:47 AM

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

 

@rbrocks 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. 

Idea Statuses