Forum Discussion
On-Prem Data Gateway errors
Hi Power BI forum!
I'm seeing errors in the diagnostic file for one of our gateways. here is a snippit of the error
DM.EnterpriseGateway Error: 0 : 2026-03-09T18:36:53.0088260Z DM.EnterpriseGateway fdc1ed57-16b4-43c3-bf07-f31b86a489e3 da2d981e-8a28-4ff7-8eee-6a68a457ae28 MGAP
There are others with MGCC and MDSR.
This seem to stop the gateway from communicating with the service. Restarting the gateway service seems to resolve the issue for a while.
Any clue on what those codes indicate?
Thanks,
DKHughes55
Hi v-hashadapu,
After digging into the logs of the gateway service we found the issue was not being able to start a new worker. Resource limits. We have added more memory which has solved the issue.
Yes this has been resolved.
DKHughes55
3 Replies
Hi DKHUghes55 , Thank you for reaching out to the Microsoft Community Forum.
Those codes in the logs of the On premises data gateway are internal gateway trace tags. Microsoft does not publish documentation for them and by themselves they don’t indicate a specific error. They usually appear in the gateway’s internal communication pipeline with the Microsoft Power BI Service, so they’re mainly useful for Microsoft support when analyzing full diagnostic logs.
Since restarting the gateway temporarily restores connectivity, I suggest you update the gateway to the latest version, verify if the server can reach required Power BI/Azure Service Bus endpoints over HTTPS (443) and check the gateway machine for resource or network interruptions. If it keeps happening, collect the full gateway logs and open a Microsoft Support ticket so they can interpret those internal traces and resolve it on their end.
Below is the link to help create Microsoft Support ticket:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft LearnHi DKHUghes55 , hope you are doing well. may i know if the information provided here solved your issue or if you have raised the support ticket as suggested? If your issue's solved either way, please share the insights here, so others with similar issues may find the solution easily.
Thank you.Hi v-hashadapu,
After digging into the logs of the gateway service we found the issue was not being able to start a new worker. Resource limits. We have added more memory which has solved the issue.
Yes this has been resolved.
DKHughes55
