Connectivity

Power BI connectivity refresh errors

Connectivity errors happen when Power BI can't establish or keep a connection to the underlying data source, directly or through a data gateway, such as a network, firewall, DNS, SSL/TLS, or listener problem.

The 8 catalogued errors in this category, each with its plain-English cause and fix:

• DM_GWPipeline_Gateway_DataSourceAccessErrorThe gateway was reached but could not access the on-premises source (wrong connection details, source unreachable, or a permission problem).
• DM_GWPipeline_Gateway_MashupDataAccessErrorThe gateway's mashup engine could not negotiate TLS / a certificate with the source (e.g. Databricks: TLS 1.2 or certificate trust).
• Login timeout expiredThe SQL connection could not be established in time (network unreachable, firewall, or a slow server).
• The server was not found or was not accessible (SQL error 40)SQL "error 40": wrong instance, server down, remote connections disabled, or a firewall block.
• Connection denied: Deny Public Network Access (Azure SQL)Azure SQL is blocking public-endpoint connections.
• The certificate chain was issued by an authority that is not trustedAn on-prem SQL self-signed certificate is not trusted (encrypt-by-default).
• The server name doesn't match the SQL Server SSL certificateA short server name was given but the certificate CN is the FQDN.
• Oracle TNS error (ORA-12154 / ORA-12514 / ORA-12541)Oracle TNS errors (ORA-12154/12514/12541/12170/12504): a bad connect identifier, or the listener/port is down or firewalled.

Browse all Power BI refresh errors