Connectivity
DM_GWPipeline_Gateway_MashupDataAccessError
Power BI dataset refresh error: what it means and how to fix it.
What this means
The gateway's mashup engine could not negotiate TLS / a certificate with the source (e.g. Databricks: TLS 1.2 or certificate trust).
How to fix it
- Enable TLS 1.2 on the gateway host.
- Trust the source certificate chain on the gateway host.
- Update the gateway and the data-source driver; check for an HTTPS-inspection proxy in the path.
Frequently asked questions
- What does the "DM_GWPipeline_Gateway_MashupDataAccessError" error mean?
- The gateway's mashup engine could not negotiate TLS / a certificate with the source (e.g. Databricks: TLS 1.2 or certificate trust).
- How do I fix it?
- Enable TLS 1.2 on the gateway host. Trust the source certificate chain on the gateway host. Update the gateway and the data-source driver; check for an HTTPS-inspection proxy in the path.
- 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_DataSourceAccessError
- 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.