Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
KC_Wong
New Member

Data source connection on Power BI Report Server failed

Hello,

 

I have developed a Power Bi report using Power BI desktop and my project connects successfully to a SQL Server database using Windows credential and to a Postgres database using a standard credential. However, when I deploy my project on a Power BI Report Server ( Jan 22 version ), I am unable to connect to my data sources. For the SQL Server connection, i encounter the following message : 

Microsoft SQL: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

For the Postgres database connection, the following message popped up :

Please install Npgsql version 4.0.10.0 or earlier.

Do you have any solution or investigative steps that I can take to resolve the issue? Thanks in advance for your help.

 

 

2 ACCEPTED SOLUTIONS
d_gosbell
Super User
Super User

For the SQL issue you might need to talk to someone in your IT network team. It sounds like there could be a firewall issue or something like that preventing your Report Server from "seeing" the SQL Server.

 

For the Postgres issue it sounds like you do not have the Postgres drivers installed on the Report Server. Someone will need to install those in order for you to access data from Postgres.

View solution in original post

v-luwang-msft
Community Support
Community Support

Hi @KC_Wong ,

This error usually means that the client can't find the SQL Server instance. This normally happens when at least one of the following problems exist:

  • The name of the computer hosting the SQL Server
  • Instance does not resolve the the correct IP
  • The TCP port number is not specified correctly

Checklist:

  1. SQL Server are up are runing
  2. check the correct instance name
  3. add in exception in firewall
  4. check if anti virus is using it
  5. check the sql browser services

Please refer the following Microsoft document and cases that could also help you:

  1. https://community.powerbi.com/t5/Desktop/SQL-Connection-error-Named-Pipes/td-p/29203
  2. https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/troubleshoot-connecting-to-th...
  3. https://support.microsoft.com/en-us/help/4009936/solving-connectivity-errors-to-sql-server

Did I answer your question? Mark my post as a solution!


Best Regards

Lucien

View solution in original post

4 REPLIES 4
v-luwang-msft
Community Support
Community Support

Hi @KC_Wong ,

This error usually means that the client can't find the SQL Server instance. This normally happens when at least one of the following problems exist:

  • The name of the computer hosting the SQL Server
  • Instance does not resolve the the correct IP
  • The TCP port number is not specified correctly

Checklist:

  1. SQL Server are up are runing
  2. check the correct instance name
  3. add in exception in firewall
  4. check if anti virus is using it
  5. check the sql browser services

Please refer the following Microsoft document and cases that could also help you:

  1. https://community.powerbi.com/t5/Desktop/SQL-Connection-error-Named-Pipes/td-p/29203
  2. https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/troubleshoot-connecting-to-th...
  3. https://support.microsoft.com/en-us/help/4009936/solving-connectivity-errors-to-sql-server

Did I answer your question? Mark my post as a solution!


Best Regards

Lucien

Thanks a lot for your solution. I am following your checklist and the issue is arising in the exception in firewall. I will give an update once my network team is able to resolve the issue. 

d_gosbell
Super User
Super User

For the SQL issue you might need to talk to someone in your IT network team. It sounds like there could be a firewall issue or something like that preventing your Report Server from "seeing" the SQL Server.

 

For the Postgres issue it sounds like you do not have the Postgres drivers installed on the Report Server. Someone will need to install those in order for you to access data from Postgres.

Thanks a lot for your quick answer. It's indeed a route opening / firewall issue that my network team is trying to solve regarding the SQL Server issue.

The problem for Postgres issue is more complicated, somehow the plugin driver doesn't solve it hence someone pointed me towards an ODBC solution which I need some time to test.

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.