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

We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now

Reply
Anonymous
Not applicable

Error 40 SQL Issue Connecting to Dataflows

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

zgrecohw_0-1730405470364.png

 

1 ACCEPTED SOLUTION
Anonymous
Not applicable

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!

View solution in original post

4 REPLIES 4
Anonymous
Not applicable

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!

Anonymous
Not applicable

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.

SaiTejaTalasila
Super User
Super User

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

https://community.fabric.microsoft.com/t5/Dataflow/Dataflows-Gen2-not-connecting-to-lakehouse/m-p/3574263

I hope it will be helpful.

 

Thanks,

Sai Teja 

 

mattiasdesmet
Resolver II
Resolver II

Is this a transient issue? Does the Lakehouse SQL Endpoint still exist? Do you have access to it?

Helpful resources

Announcements
New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.

Join our Fabric User Panel

Join our Fabric User Panel

Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.

March Power BI Update Carousel

Power BI Community Update - March 2026

Check out the March 2026 Power BI update to learn about new features.

Top Solution Authors