Forum Discussion
Report Refresh Failures due to Timeout
Hi Everyone,
We have been facing this issue from last couple of days. The source of the reports are Power BI Dataflows(main data source snowflake).
We have an on-premises data gateway, which has been updated to the latest version as well.
Error bsnapshot below :
Data source error: {"error":{"code":"DM_GWPipeline_Gateway_AdoNetProviderOpenConnectionTimeoutError","pbi.error":{"code":"DM_GWPipeline_Gateway_AdoNetProviderOpenConnectionTimeoutError","parameters":{},"details":[],"exceptionCulprit":1}}} Table: Sort Order Unique L2 Codes
Can someone please help us to resolve this error? The table name changes every now and then.
It is creating a lot of hassle for us.
Regards,
Sanjyot
6 Replies
Hello sanjyot_firke ,
I think it's a connection error, check the refresh on the desktop version if it's working then it might be a connection error or the data is large then you might remove some unused columns and filter the data to minimize it.
The reports refresh on desktop with no issues at all. The data is also not much,a round 2 million records.
The reports were running fine for sometime now and suddenly we are facing with this issues more frequently now.
We have premium capacities for the workspaces and each user has Premium per user license type.
We have the same issue with another data source (Exasol). Refreshes have been running stable for a long time, since a few days we often have the above mentioned error.
Hello Generic_name ,
then this might be a bug, you can open an issue with what are you facing in the following link and microsoft support will investigate it and report it to the production team for fix.
https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues
Is this a new dataflow or an existing one?
Did you import the dataflow from a JSON file, or have you made changes to an existing dataflow?
The table "Sort Order Unique L2 Codes" is causing the issue. Could you try removing this table and then re-run the dataflow?
What are the results?
This is a table in an existing dataflow, created from scratch. We have not imported any JSON file for the dataflow creation.
Also this error pops up sporadically and points to a different table everytime. So the table is not causing any issue. The report when refreshed on Dektop, it runs absolutely fine and with no errors.
