Connectivity
DM_GWPipeline_Gateway_DataSourceAccessError
Power BI dataset refresh error: what it means and how to fix it.
What this means
The gateway was reached but could not access the on-premises source (wrong connection details, source unreachable, or a permission problem).
How to fix it
- Validate the data-source connection details.
- Confirm the source is reachable and the gateway service account has access.
- Check the gateway logs for the specific access error.
Frequently asked questions
- What does the "DM_GWPipeline_Gateway_DataSourceAccessError" error mean?
- The gateway was reached but could not access the on-premises source (wrong connection details, source unreachable, or a permission problem).
- How do I fix it?
- Validate the data-source connection details. Confirm the source is reachable and the gateway service account has access. Check the gateway logs for the specific access error.
- Where does this Power BI refresh error appear?
- It appears in a Power BI semantic model's refresh history when a scheduled or on-demand refresh fails.
Related connectivity errors
- DM_GWPipeline_Gateway_MashupDataAccessError
- Login timeout expired
- The server was not found or was not accessible (SQL error 40)
- Connection denied: Deny Public Network Access (Azure SQL)
- The certificate chain was issued by an authority that is not trusted
- The server name doesn't match the SQL Server SSL certificate
Catch this automatically
RefreshRadar monitors every Power BI dataset refresh and emails you when one fails, with the likely cause and the fix, so you are not hearing about a broken refresh from your stakeholders first.