This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
Hi - I'm having issues
DataSource.Error: 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)
Details:
DataSourceKind=PowerPlatformDataflows
DataSourcePath=PowerPlatformDataflows
DataSourceKind.2=Lakehouse
DataSourcePath.2=Lakehouse
DataSourceKind.3=SQL
DataSourcePath.3=zrw6n6nljmuutk2l55ymzhwclu-vbiutreee3surcdky5emx347oa.datawarehouse.fabric.microsoft.com;DataflowsStagingLakehouse
Message=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)
ErrorCode=-2146232060
Number=53
Class=20
State=0
Solved! Go to Solution.
Thanks for all the input - the issue ended up being an update to my orgs Zscaler client that blocked access to the needed endpoints. Issue resolved!
Thanks for all the input - the issue ended up being an update to my orgs Zscaler client that blocked access to the needed endpoints. Issue resolved!
Hi @Anonymous ,
I think you can start by checking your SQL Server configuration, and this document below provides some steps to help you troubleshoot these errors, which are provided in order of problem from simple to complex.
A network-related or instance-specific error occurred - SQL Server | Microsoft Learn
Best Regards,
Clara Gong
If there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @Anonymous ,
If you are seeing the issue on the dataflow this might be an issue related with your gateway.
https://learn.microsoft.com/en-us/fabric/data-factory/gateway-considerations-output-destinations
I hope it will be helpful.
Thanks,
Sai Teja
Is this a transient issue? Does the Lakehouse SQL Endpoint still exist? Do you have access to it?
Check out the April 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 11 | |
| 9 | |
| 9 | |
| 8 | |
| 8 |
| User | Count |
|---|---|
| 48 | |
| 27 | |
| 25 | |
| 24 | |
| 22 |