The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
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
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?
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:
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.