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
Hi,
We have 3 different SQL servers in different environments that we're getting data from using the on-premise gateway.
Two of these are working fine, however all dataflows that link to the third server are failing to refresh.
This setup has been working for few years without issue, only from yesterday has the refresh started to fail.
The error I'm getting when the refresh fails is:
AzureBlobs failed to get the response: 'Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.'. Request ID: 8eac2358-a7c9-456f-9f19-94f8912192a9 Activity ID: b396b3fa-18db-46f7-a804-d546993366b
I'm running the latest version of the on-premise gateway.
Does anyone have any advice?
Thanks.
Solved! Go to Solution.
Issue turned out to be a degraded line with the upstream internet provider.
This was causing intermittent drops and unusual behaviour.
Issue turned out to be a degraded line with the upstream internet provider.
This was causing intermittent drops and unusual behaviour.
Hi @v-cboorla-msft,
Thanks I have tried what you recommended, however this is related the the dataflow refresh, which runs on a schedule as well and fails with this too. So it's not related to the machine I'm working from.
I have looked at this from the remote server I'm connecting to over the on-prem gateway and have the same result there.
I've also created a completely new Dataflow and am having the same result.
The dataset that is being returned is very small and would complete in less than 1 minute.
The refresh now runs for 5 minute and 30 seconds and then fails.
The latest failure message is:
Error: AzureBlobs failed to get the response: 'The request was aborted: The request was canceled.
Hi @Morallis
Can you please share me the screenshots of the error that you are encountering in dataflow, in order to understand your query and guide you in a better way.
Thank you.
Hi @Morallis
Thanks for using Microsoft Fabric Community.
Can you please confirm the on-premise gateway version that you are using?
Thank you.
hi,
Version 3000.222.5
Something I didn't mention in my original post, is that I am able to setup new dataflows linked to the SQL server without issue.
When in the Power Query editor creating the Dataflow, i am able to refresh and see the data. Once this is saved and the Dataflow itself is refreshed, this is when it fails.
Hi @Morallis
Thanks for sharing the details.
There might be a chance of an intermittent issue could you please follow the below steps that might help you.
Temporary Glitch: Clearing cookies and caches can sometimes resolve temporary glitches within the application that might be causing the issue.
Corrupted Data: In rare cases, corrupted data stored in the browser's cache related to Microsoft Fabric might be causing the issue. Clearing the cache removes this potentially problematic data.
Hard Refresh: A hard refresh bypasses the cached version of the webpage and forces the browser to download the latest version from the server. Press Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac).
Try Microsoft Edge: If you are currently using Chrome or Firefox, try switching to Microsoft Edge to see if the issue persists. Edge is the native browser for Microsoft products and might have better compatibility with Microsoft Fabric.
If the issue still persists, please do let us know. Glad to help.
I hope this information helps.
Thank you.
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.
User | Count |
---|---|
2 | |
1 | |
1 | |
1 | |
1 |
User | Count |
---|---|
4 | |
3 | |
1 | |
1 | |
1 |