Forum Discussion

evebarratt's avatar
evebarratt
Helper I
3 years ago

OLE DB or ODBC error when loading new or refreshing existing SQL Server database

Hi there,

 

I am hoping someone can point me to the right direction on how I can address this issue.

 

I have Azure SQL database connection set up in my Power BI desktop report and everything has been working fine and I was able to refresh data whenever I need until last Friday. Since then I keep getting the below error.

 

I tried creating a new data connection on a new report and the same thing happens. It has gone past creating connection in model, start loading rows from the database but then it stalls and this error message pops up.

 

The funny thing is that if I publish this report onto Power BI Service and refresh dataset from there it works fine. 

 

I spoke to our IT and data department but no one seems to know what could have caused this error. 

 

Has anyone ever come across issue like this and what would be my option to address this? 

 

Many thanks in advance!

 

Hoi

 

Need Help

4 Replies

  • foodd's avatar
    foodd
    Community Champion
    3 years ago

    Try connecting to the Azure SQL database using other tools like SQL Server Management Studio (SSMS) or Excel. This will help determine if the issue is specific to Power BI Desktop or if there is a broader connectivity problem.

     

    Have you recently updated Power BI Desktop?   Perhaps uninstall, and install Power BI Desktop from the Windows Store, as that receives the first updates as opposed to the MSI installer.

    • evebarratt's avatar
      evebarratt
      Helper I
      3 years ago

      Thanks foodd for your suggestion. I have tried excel and the same error pops up, so it seems to be a broader issue.

       

       

      • foodd's avatar
        foodd
        Community Champion
        3 years ago

        That is a good error!    TCP 0 is saying that No connection could be made because the target machine actively refused it.    No not an answer, though good to confirm.  Seems like a networking issue to me.

         

        Test Step 2:  Using SSMS from a remote machine, see if the connection is accepted.   I would rope in the DBA (who owns the box and instance), and the Network folks (who own the connectivity) to help with this if I were in your place.