Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
I've been trying to get a medium-sized (100,000 records for now) dataset to load from a SQL database (on prem and Azure) to a Fabric Warehouse from a Gen2 dataflow. I can get it to load 1000 or 10000 records, but once I step up to higher numbers, I get the error below. And yes--port 1433 is open. Also--I can load all the data no problem with a native Power BI dataset or a Gen1 dataflow.
It's almost like the connection to the source database times out after a certain period of time.
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 transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) Details: DataSourceKind = Lakehouse;DataSourcePath = Lakehouse;Message = A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.);ErrorCode = -2146232060;Number = 10054;Class = 20
And as of right now, I still can't get any Gen2 dataflows to complete--not since last Thursday around 1 pm PST. Something is hard broken now. Have built new workspaces, lakehouse, dataflows...nothing works. The refreshes simply spin on forever now.
Hey!
Could you please share a screenshot of the error message that you're seeing inside of the refresh history dialog?
Here are a couple of screenshots--same message, different dataflows and requests.
Hi motoray,
If you could please also paste the Request ID for some of your failed dataflow refreshes that would be appreciated.
There are some known ongoing issues with SQL endpoints and we would like to see whether you are impacted by those or encountering separate issues.
Thanks
Here are some request IDs:
30ea6d08-cd77-439d-b094-1c3a9c3222ca
a103dcc1-d9cd-4f20-9848-539af2c6be68
cc31824d-9766-4dac-8c66-affda2fe69ce
e8ac09a0-f667-4f88-a3bf-c94a531b2827
9db665b1-3ea9-4ee0-a9c6-ec2133fe5227
d4f414ea-8f21-4bde-8130-9155dcc3f1f2
6751049f-79ff-44ae-9bca-3cab134cbcf6
c7eca806-2a1f-4443-b040-7811607935d9
Thank you for taking a look.
We will share the screenshots of our error screens.
Since the error message is identical to what motoray posted, we believe our situation is similar to motoray's.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Fabric update to learn about new features.