Forum Discussion
Data source connection on Power BI Report Server failed
- 4 years ago
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.
- 4 years ago
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:
- SQL Server are up are runing
- check the correct instance name
- add in exception in firewall
- check if anti virus is using it
- check the sql browser services
Please refer the following Microsoft document and cases that could also help you:
- https://community.powerbi.com/t5/Desktop/SQL-Connection-error-Named-Pipes/td-p/29203
- https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/troubleshoot-connecting-to-the-sql-server-database-engine?view=sql-server-ver15
- 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 RegardsLucien
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.