Power BI Gateway Error: DM_GWPipeline_Gateway_DataSourceAccessError Occurring Sporadically

[ollie_mills]

We're experiencing an intermittent issue with our Power BI datasets refreshing through an Azure VM gateway. We're seeing the following error randomly across different datasets:

	{"error":{"code":"DM_GWPipeline_Gateway_DataSourceAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_DataSourceAccessError","parameters":{},"details":[],"exceptionCulprit":1}}} Table: my_table_name.

When we re-trigger the refresh on the failed datasets, they refresh fine, indicating that it isn't a data related issue, but more likely something related to network/gateway/VM/power bi service

Environment details:

• Using the Power BI Refresh API to trigger refreshes
• Gateway is hosted on an Azure VM
• All data comes from Azure SQL Server
• Error appears sporadically with no consistent pattern
• Different tables/datasets are affected (not specific to any single dataset)

I've searched the gateway error log files (the ones named like this: 'GatewayErrors20250410') for that ^ specific error code but there's nothing in the error log file that matches that error code, or anything else that would explain the intermittent failures. The sporadic nature suggests it's some kind of transient issue rather than a problem with specific datasets or queries.

Has anyone encountered this specific error code and found a solution? Any recommendations for troubleshooting steps or gateway configurations that might help resolve these random failures?

[v-kathullac · Accepted solution]

Hi @ollie_mills ,
Below are the steps you can follow to troubleshoot your issue:

1. Update the Gateway
   Ensure you are using the latest version of the on-premises data gateway.
   Microsoft regularly releases bug fixes and stability improvements.

2. Check Azure VM Performance
   Monitor CPU, RAM, and disk I/O during refresh windows.
   High CPU spikes or memory pressure can cause the gateway to time out or drop requests.
   Consider scaling the VM size or increasing the performance tier if it’s under strain.

3. Use a Dedicated Gateway VM
   If the VM is also running other workloads (e.g., SQL Server, SSIS, IIS), they might interfere.
   Using a dedicated VM solely for the Power BI Gateway can reduce contention and increase stability.

4. Enable Gateway Logs at Verbose Level
   Although the logs may not currently show this specific error, enabling detailed logging might reveal more insights.
   Use the Microsoft.PowerBI.DataMovement.Pipeline.GatewayDiagnostics and EnterpriseGatewayConfigurator.exe tool to configure verbose logging.

Providing the links to check the details of latest gateway,vm monitoring,troubleshooting guide lines

Download latest gateway version : https://www.microsoft.com/en-us/power-platform/products/power-bi/gateway

Monitor Azure VM with Azure Monitor : https://learn.microsoft.com/en-us/azure/azure-monitor/fundamentals/overview

Power BI Gateway Troubleshooting Docs : https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-tshoot

Regards,

Chaithanya.

[lbendlin]

If your data is on Azure SQL server then you should not need a gateway.

[ollie_mills]

Our sql server is hosted on an azure virtual private network due to security reasons, so the gateway is needed - i forgot to mention