Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now

Reply
DKHUghes55
Resolver I
Resolver I

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

1 ACCEPTED SOLUTION

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

View solution in original post

3 REPLIES 3
v-hashadapu
Community Support
Community Support

Hi @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

v-hashadapu
Community Support
Community Support

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 Learn

Helpful resources

Announcements
New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.

Join our Fabric User Panel

Join our Fabric User Panel

Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.

March Power BI Update Carousel

Power BI Community Update - March 2026

Check out the March 2026 Power BI update to learn about new features.

Top Solution Authors