Forum Discussion
Gateway Error - Can't Refresh Published Dashboards : Non-gateway network exception encountered in ac
I'm experiencing issues with the scheduled refresh on my Power BI dashboards. I have six published dashboards that have been running smoothly since January, but since last week, I've been encountering gateway errors. My gateway starts running at 12:10 AM, followed by a scheduled refresh at 1:30 AM. However, only one dashboard completes the refresh, while the others crash. Interestingly, I have another scheduled refresh at 1:30 PM, and this one runs without any problems.
While reviewing the error logs, I found the following:
DM.EnterpriseGateway Error: 1 : 2024-09-06T04:31:30.3353144Z DM.EnterpriseGateway [DM.NetworkCore] Non-gateway network exception encountered in activity scope: System.ServiceModel.CommunicationException: The socket connection has been disposed. Timestamp:2024-09-06T04:31:30 ---> System.IO.IOException: The write operation failed, see inner exception. ---> System.ServiceModel.CommunicationException: The socket connection has been disposed. ---> System.ObjectDisposedException: Cannot access a disposed object.
This error occurred exactly when my dashboards were scheduled to refresh. Can anyone help me understand what's going on?
4 Replies
My gateway starts running at 12:10 AM,What made you choose that? Why not keep it running 24x7 ?
Are you on Atlantic time?
Due to company preference, it was decided that the machine would turn on at 12:00 AM and turn off at 2:00 AM. My ETL finishes running at 1:00 AM, and my Power BI updates at 1:30 AM, with the update finishing around 1:45 AM. I am not in the Atlantic time zone.
The reason I was asking was that the error showed it as 4:31 UTC
2024-09-06T04:31:30.3353144Z
Recommendation would be to keep the gateway running for testing purposes and see if the error goes away.
Thank you lbendlin
Hi, petersenpedrog
Do you use the verification method in the image below:
Microsoft Entra ID OAuth？
In this case, the data loading process may fail due to a credential error (the problem you are experiencing).
Usually the workaround for this error is:
Make sure your refresh time is less than an hour and optimize its datasets/queries for this data source.Troubleshoot refresh scenarios - Power BI | Microsoft Learn
In addition, you can view the error information from the logs of the on-premises data gateway by following the document below
Troubleshoot the on-premises data gateway | Microsoft Learn
Follow the following documents to test the gateway's network:
Adjust communication settings for the on-premises data gateway | Microsoft Learn
Later, if you find more useful error information, it will help troubleshoot the core of the error.
Best Regards
Jianpeng Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
