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
AmilaAkalanka
New Member

Issue With Dataflow Gen2 Lakehouse Connection

Hi,

I am executing several Dataflow Gen2 tasks from my Fabric pipelines. Since 11/24/2024, I have been randomly getting the below error on Dataflows. When I manually refresh it, sometimes it works, and sometimes it fails with a random entity in the Dataflow. All connection strings are correct, and since this works intermittently, it means there's nothing wrong with the credentials. Lakehouse is the destination for all Dataflows. Does anyone have any clues as to why this suddenly happening?


Mashup Exception Data Source Error Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: 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: Reason = DataSource.Error;ErrorCode = 10478;DataSourceKind = Lakehouse;DataSourcePath = Lakehouse;DataSourceKind.2 = SQL;DataSourcePath.2 = ccccxxx.datawarehouse.fabric.microsoft.com;my_datalakehouse;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;Microsoft.Data.Mashup.Error.Context = User

2 REPLIES 2
ChielFaber
Super User
Super User

I'm getting the exact same errors. Also since approximatly 26 september 2024. Some dataflows run fine and others keep giving this error... Could this be a more common issue?


[Tip] Keep CALM and DAX on.
[Solved?] Hit “Accept as Solution” and leave a Kudos.
[About] Chiel | SuperUser (2023–2) |
Anonymous
Not applicable

Hi @AmilaAkalanka ,

 

It appears that there may be network related issues or instance specific errors when trying to establish a connection to SQL Server. There are several things to be aware of:

  • Intermittent Network Issues: Since the error occurs randomly, this may be due to an intermittent network issue. Ensure that your network connection is stable and uninterrupted.
  • SQL Server Configuration: Verify that the SQL Server instance is configured to allow remote connections. This includes checking the SQL Server configuration settings and ensuring that the Named Pipes Provider is enabled.

 

Also, you can refer to below similiar solution:

Solved: Re: Couldn't refresh the entity because of an issu... - Microsoft Fabric Community

 

Best Regards,
Adamk Kong

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

Announcements
FabCon and SQLCon Highlights Carousel

FabCon &SQLCon Highlights

Experience the highlights from FabCon & SQLCon, available live and on-demand starting April 14th.

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.

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 Fabric Update Carousel

Fabric Monthly Update - March 2026

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

Top Solution Authors
Top Kudoed Authors