Forum Discussion
Advocate Ierratic connection Power BI Desktop --> Fabric SQL DW
We have an ongoing issue that when you connect to Fabric SQL DW via Power BI Desktop through imported mode ONLY SOMETIMES it gives this error below and other times you can connect easily. this is not for a big dataset it is literally 2000 rows.
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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
I have changed the timeout values it makes no difference. When i look at the monitor in the SQL DW it doesn't even show that its querying. Not sure where this is getting stumped.
any ideas of where i can diagnose what is going on?
2 Replies
Shubham_rai955Super User
This looks more like an intermittent connectivity issue than a dataset size or query timeout problem, especially since the SQL Warehouse does not show the failed requests.
I would check the following:
- Verify the SQL endpoint: Copy the server name directly from the Fabric Warehouse settings and ensure Power BI Desktop is using the correct SQL endpoint and database name.
- Check network connectivity: Verify VPN, firewall, proxy, and outbound TCP port 1433 settings. If possible, test the connection from another network.
- Test using SSMS: Connect to the same endpoint using SQL Server Management Studio. If the same error occurs intermittently, the issue is likely outside the Power BI query itself.
- Clear cached credentials: In Power BI Desktop, go to File > Options and settings > Data source settings, clear the permissions for the endpoint, and reconnect.
- Check the connection path: The Named Pipes Provider error can appear even when the underlying issue is network connectivity. Confirm that the SQL Server driver is using TCP/IP and that the client and driver are up to date.
- Capture diagnostic logs: Use Power BI Desktop diagnostics to capture a failed connection attempt. Note the timestamp and correlation details, then compare them with Fabric monitoring and capacity metrics.
- Check for capacity or service issues: Review Fabric capacity utilization and Microsoft Fabric service health around the failure times.
My first step would be to test the same endpoint in SSMS during a failure. Since the request does not appear in Warehouse monitoring, I would focus on connection establishment, DNS, firewall, and network routing before investigating query performance.
- tayloramy
Hi vanessa_fvg
Are there any patterns to when it is not accessible? Perhaps when you are connected to a company VPN or in office? Connecting to Fabric databases does require that port 1433 is open on your network, and a lot of companies block that.
