Forum Discussion
Power BI Gateway Error: DM_GWPipeline_Gateway_DataSourceAccessError Occurring Sporadically
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?
Hi ollie_mills ,
Below are the steps you can follow to troubleshoot your issue:-
Update the Gateway
Ensure you are using the latest version of the on-premises data gateway.
Microsoft regularly releases bug fixes and stability improvements. -
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. -
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. -
Enable Gateway Logs at Verbose Level
Although the logs may not currently show this specific error, enabling detailed logging might reveal more insights.
Use theMicrosoft.PowerBI.DataMovement.Pipeline.GatewayDiagnosticsandEnterpriseGatewayConfigurator.exetool 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.
-
8 Replies
- lbendlin
Super User
If your data is on Azure SQL server then you should not need a gateway.
- ollie_mills
Helper I
Our sql server is hosted on an azure virtual private network due to security reasons, so the gateway is needed - i forgot to mention
- v-kathullac
Community Support
Hi ollie_mills ,
Below are the steps you can follow to troubleshoot your issue:-
Update the Gateway
Ensure you are using the latest version of the on-premises data gateway.
Microsoft regularly releases bug fixes and stability improvements. -
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. -
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. -
Enable Gateway Logs at Verbose Level
Although the logs may not currently show this specific error, enabling detailed logging might reveal more insights.
Use theMicrosoft.PowerBI.DataMovement.Pipeline.GatewayDiagnosticsandEnterpriseGatewayConfigurator.exetool 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.
-
- aguiar_davidNew Member
We are seeing the same issue in our environment.
The refresh fails sporadically with DM_GWPipeline_Gateway_DataSourceAccessError. There is no clear pattern. Sometimes the error happens in one semantic model, other times in a different one. Our gateway is currently on version 3000.298.8.
If we run the refresh again, it usually succeeds. Sometimes we can go several days without any error at all. Because of that, this does not look like a permanent dataset or query issue, but rather an intermittent gateway, network, or service-side problem.
We would also like to know whether anyone has identified the real root cause, since the issue is random and difficult to reproduce consistently.
- aguiarFrequent Visitor
Hi everyone,
I’m facing an intermittent refresh issue in Power BI Service with the following error:
Data source error:
{"error":{"code":"DM_GWPipeline_Gateway_DataSourceAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_DataSourceAccessError","parameters":{},"details":[],"exceptionCulprit":1}}}Some important details:
Gateway version: 3000.202.16
Data source types: SQL Server and Web
This started happening around March 2026, approximately.
Some semantic models use Excel files stored in OneDrive, connected in Power BI through a Web data source with OneDrive login.
However, the same error has also occurred in other semantic models that use only SQL Server.
SQL Server authentication: Basic authentication with username and password
The error is intermittent. Sometimes the refresh works normally for several days without any issue.
When the error happens, it always occurs right at the beginning of the refresh process.
It never happens after the refresh has been running for a long time.
After the error happens, if I manually click refresh again, the refresh always succeeds on the next attempt.
It happens with multiple semantic models, not only one.
I have already published the same semantic model to another workspace, and the same issue also occurred there.
I have also tested with another gateway on the same version, and the same behavior happened.
In both gateways, the pattern is the same: it works for days, then sometimes fails right at the beginning, and the next manual refresh succeeds.
The gateway machine remains online and available.
The data sources and credentials seem to be configured correctly, since successful refreshes happen using the same configuration.
Because the error happens only sometimes, always at the beginning of the refresh, and succeeds immediately on retry, I’m wondering if this could be related to a temporary gateway communication issue, network/authentication handshake, token/credential validation, or some transient issue in the Power BI Service/Gateway pipeline.
Has anyone experienced this behavior before?
What logs or specific information should I check to identify the root cause?
Any suggestions would be appreciated.
Thanks!
- ollie_mills
Helper I
We never got to the bottom of this by the way - this issue still happens sporadically. We always keep our gateway up to date - we have a dedicated VM for the gateway. I enabled verbose logging and tried to see what the issue was, but nothing stood out when these issues occured. Only thing I can think is we need to scale up our gateway VM