Forum Discussion

hhchoi32's avatar
hhchoi32
Regular Visitor
4 years ago

PowerBI Desktop - ErrorCode=-2146232060

Hi everyone, 

 

All of sudden,  PowerBI reports using SQL DB server are not working on PowerBI Desktop or Service. I've seen this message on PowerBI Desktop.

 

 1. I tried refreshing the report in desktop and got the error - "A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The received certificate has expired.)". Details is below.
 2. If I uncheck the "Encrypt Connections" option in the "Edit Permissions" section in desktop the report refreshes however I still get the error once published to service.
 3. There has not been any SSL certificate related update to the SQL Server.
 

Here is the detailed message that I received from PowerBI Desktop. 

=================
DataSource.Error: 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 received certificate has expired.)
Details:
    DataSourceKind=SQL
    DataSourcePath=xxxxxxxxxxx
    Message=A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The received certificate has expired.)
    ErrorCode=-2146232060
    Number=-2146893016
    Class=20
===============

SQL Version : 15.0.2080.9

OS: Windows Server 2019 Standard (10.0)

 

We've found updates pending on our SQL server, installed them properly, and rebooted the server. But the issue is alive. 

What should we do? 

 

Thank you!

 

 

2 Replies

  • This is not really a Power BI issue as such, it's a SQL Server issue. Your DBA or whoever manages your SQL Server has let the certificate expire that encrypts the communications between the SQL Server and client applications. They will need to update that with a non-expired certificate.

  • This error means that the client can't find the SQL Server instance. This can happen when at least one of the following problems exists: The name of the computer hosting the SQL Server instance doesn't resolve the correct IP. The TCP port number isn't specified correctly.

     

     

    Hope this helps