What causes OLE DB or ODBC error?

The ODBC or OLE DB driver on the gateway machine is outdated or incompatible with the data source version. The DSN (Data Source Name) configured for an ODBC connection is incorrect or missing. The driver was not installed for the same bitness (32-bit vs 64-bit) as the gateway service. A driver-level authentication failure when using Windows integrated security (Kerberos/NTLM). The ODBC/OLE DB driver returned a SQL error code — check the inner error for the specific SQL state

How do I fix OLE DB or ODBC error?

Check the full error message for a SQL State code (e.g., 28000 for auth, 42000 for syntax) — it points to the root cause.. Update the ODBC or OLE DB driver on the gateway machine to the latest version that supports your database.. Ensure the driver is installed as 64-bit — the gateway service runs in 64-bit mode.. If using DSN-based connections, verify the DSN is configured at the system level (not user level) in ODBC Data Source Administrator.. For Kerberos failures, use the Kerberos Configuration Manager tool to diagnose SPN and delegation issues.. Test the ODBC connection using the 'Test Connection' button in ODBC Data Source Administrator on the gateway machine.

High severitygateway

Power BI Refresh Error:
OLE DB or ODBC error

What does this error mean?

The ODBC or OLE DB driver used to connect to the data source returned an error. This is common with on-premises databases accessed through drivers installed on the gateway machine.

Common causes

1The ODBC or OLE DB driver on the gateway machine is outdated or incompatible with the data source version
2The DSN (Data Source Name) configured for an ODBC connection is incorrect or missing
3The driver was not installed for the same bitness (32-bit vs 64-bit) as the gateway service
4A driver-level authentication failure when using Windows integrated security (Kerberos/NTLM)
5The ODBC/OLE DB driver returned a SQL error code — check the inner error for the specific SQL state

How to fix it

1Check the full error message for a SQL State code (e.g., 28000 for auth, 42000 for syntax) — it points to the root cause.
2Update the ODBC or OLE DB driver on the gateway machine to the latest version that supports your database.
3Ensure the driver is installed as 64-bit — the gateway service runs in 64-bit mode.
4If using DSN-based connections, verify the DSN is configured at the system level (not user level) in ODBC Data Source Administrator.
5For Kerberos failures, use the Kerberos Configuration Manager tool to diagnose SPN and delegation issues.
6Test the ODBC connection using the 'Test Connection' button in ODBC Data Source Administrator on the gateway machine.

Frequently asked questions

Does this error affect all datasets using the same gateway?

Yes — all datasets routed through the affected gateway will fail simultaneously. Resolving the gateway configuration or credential issue restores all of them at once.

Does this error appear in Power BI Desktop?

No — Power BI Desktop connects directly to data sources. Gateway errors only occur when Power BI Service initiates a scheduled or manual refresh.

Can this error resolve itself without intervention?

No — gateway errors require manual action: re-entering credentials, restarting the gateway service, or correcting the network path between the gateway and the data source.

How long does it typically take to fix?

A simple credential refresh takes 5–10 minutes. Network or firewall issues can take 30–120 minutes depending on your infrastructure access.

Source · learn.microsoft.com/en-us/power-bi/connect-data/service-gateway-data-sources