Forum Discussion

Chitemerere's avatar
Chitemerere
Responsive Resident
6 years ago
Solved

Failure to Connect to MS SQL Server

All my Power BI models are failing to connect to my MS SQL Server after a recent Power BI update.  I am getting the following error message with Windows authentication:

 

 

If I try and use the Microsoft Account authentication, i get the following error message:

 

 

However, i can manage to connect to the Server via SQL Management Studio.  Please assist.

 

Best regards.

Chris

 

  • Hello, managed to troubleshoot the problem.  It was actually a conflict with a newly installed SQL Server 2017 Developer Edition on top of SQL Server 2014.  When i uninstalled SQL Server 2017 Developer Edition, everything was now working.

     

    Regards,

    Chris

5 Replies

  • Chitemerere was it working before? Do you use mixed authentication on sql server? Can you try database credentials?

     

    I would  Kudos if my solution helped. 👉 If you can spend time posting the question, you can also make efforts to give Kudos whoever helped to solve your problem. It is a token of appreciation!

    • Chitemerere's avatar
      Chitemerere
      Responsive Resident

      Many thanks for your prompt resonse, most appreciated.  Yes i was able to connect to the Server before the update.  Yes i have mixed mode authentication.  If i try using the database option i get the following error message:

       

       

      Best regards,

      Chris

      • parry2k's avatar
        parry2k
        Super User

        Chitemerere can you try to use 127.0.0.1 instead of localhost.

         

        I would  Kudos if my solution helped. 👉 If you can spend time posting the question, you can also make efforts to give Kudos whoever helped to solve your problem. It is a token of appreciation!

         

    • Chitemerere's avatar
      Chitemerere
      Responsive Resident

      Hello, managed to troubleshoot the problem.  It was actually a conflict with a newly installed SQL Server 2017 Developer Edition on top of SQL Server 2014.  When i uninstalled SQL Server 2017 Developer Edition, everything was now working.

       

      Regards,

      Chris