March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
This has been happening for a few weeks but it fluctuates in severity although lately I'm getting this error on a daily basis now:
{"error":{"code":"DM_GWPipeline_Gateway_TimeoutError","pbi.error":{"code":"DM_GWPipeline_Gateway_TimeoutError","parameters":{},"details":[],"exceptionCulprit":1}}}
There doesn't seem to be any pattern as it happens on different reports on different days from different workspaces, some complex, some simple, never the same table(s) causing the issue.
I've checked gateway and server health and both are fine (the server is only 8 months old and has plenty of resource), no firewall issues and all the necessary ports are open.
I've tried rolling back to the March gateway as suggested but so far I don't see any difference.
Additionally publishing to PBI service is taking unusally long in some instances (and again, with no discernable pattern) and sometimes we recive an error stating "Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host."
I've gone through the troubleshooting guides but everything we check indicates that everything is running fine.
Solved! Go to Solution.
Hi @wjeanes
1. Could you please also try to disable the feature "Auto Detched column type" in the Options - Current File - Data Load - Type Detection
2. please try clearing the Power BI cache.
3. Check the space in your system.
4. Too large data model may be a reason for your scenario, maybe you can try to cut down you data size and try again.
5. If publishing is too slow, would you try to get the pbix from service directly?
In addition, you can also take a look at following link who faced similar issue:
Issue with Publishing PBIX File
For the error: "Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host."
You might refer to the thread:
@wjeanes I have the same timeout problem.
Would you please let me know how you solved this issue?
Thanks in advance
Hi @wjeanes
1. Could you please also try to disable the feature "Auto Detched column type" in the Options - Current File - Data Load - Type Detection
2. please try clearing the Power BI cache.
3. Check the space in your system.
4. Too large data model may be a reason for your scenario, maybe you can try to cut down you data size and try again.
5. If publishing is too slow, would you try to get the pbix from service directly?
In addition, you can also take a look at following link who faced similar issue:
Issue with Publishing PBIX File
For the error: "Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host."
You might refer to the thread:
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
User | Count |
---|---|
36 | |
27 | |
19 | |
11 | |
8 |
User | Count |
---|---|
54 | |
43 | |
24 | |
13 | |
12 |