What causes DM_GWPipeline_Gateway_UnknownError?

The gateway process crashed or was forcefully terminated during a refresh. A memory overflow on the gateway machine during the processing of a large dataset. A bug or unhandled exception in the gateway version currently installed. Antivirus software quarantined a gateway component mid-operation. The gateway's working directory ran out of disk space

How do I fix DM_GWPipeline_Gateway_UnknownError?

Check Windows Event Viewer on the gateway machine for crash or error entries at the time of the failure.. Review the gateway's own log files (typically in %LocalAppData%\Microsoft\On-premises data gateway\).. Ensure the gateway machine has sufficient free disk space (at least several GB for temp files).. Update the gateway to the latest version — many unknown errors are fixed in subsequent releases.. If the error is intermittent, add more memory to the gateway VM or reduce the number of concurrent refreshes.

High severitygateway

Power BI Refresh Error:
DM_GWPipeline_Gateway_UnknownError

What does this error mean?

An unclassified error occurred within the on-premises data gateway pipeline. This error code is a catch-all when the gateway cannot map the failure to a more specific error category.

Common causes

1The gateway process crashed or was forcefully terminated during a refresh
2A memory overflow on the gateway machine during the processing of a large dataset
3A bug or unhandled exception in the gateway version currently installed
4Antivirus software quarantined a gateway component mid-operation
5The gateway's working directory ran out of disk space

How to fix it

1Check Windows Event Viewer on the gateway machine for crash or error entries at the time of the failure.
2Review the gateway's own log files (typically in %LocalAppData%\Microsoft\On-premises data gateway\).
3Ensure the gateway machine has sufficient free disk space (at least several GB for temp files).
4Update the gateway to the latest version — many unknown errors are fixed in subsequent releases.
5If the error is intermittent, add more memory to the gateway VM or reduce the number of concurrent refreshes.

Frequently asked questions

Does this error affect all datasets using the same gateway?

Yes — all datasets routed through the affected gateway will fail simultaneously. Resolving the gateway configuration or credential issue restores all of them at once.

Does this error appear in Power BI Desktop?

No — Power BI Desktop connects directly to data sources. Gateway errors only occur when Power BI Service initiates a scheduled or manual refresh.

Can this error resolve itself without intervention?

No — gateway errors require manual action: re-entering credentials, restarting the gateway service, or correcting the network path between the gateway and the data source.

How long does it typically take to fix?

A simple credential refresh takes 5–10 minutes. Network or firewall issues can take 30–120 minutes depending on your infrastructure access.

Source · learn.microsoft.com/en-us/power-bi/connect-data/service-gateway-onprem-tshoot