What causes DataSource.Error?

The data source server is down, restarting, or under maintenance. A firewall rule is blocking connections from the gateway or Power BI cloud. The database or file path in the connection string no longer exists. Network timeout between the query engine and the data source. An API endpoint (REST, OData) returned an unexpected status code or error body

How do I fix DataSource.Error?

Read the full error message carefully — DataSource.Error always includes an inner error with more detail.. Identify whether this is a connectivity issue (can't reach server) or a data issue (server reachable, query fails).. Test connectivity from the gateway machine or from Power BI Desktop using the same connection string.. For REST/OData sources, test the URL in a browser or Postman to confirm the endpoint is healthy.. Check the data source's own logs or status page for outage or maintenance windows.. If intermittent, consider scheduling refreshes at off-peak hours when the source system is more stable.

High severitydata source

Power BI Refresh Error:
DataSource.Error

What does this error mean?

Power Query could not connect to or read from the data source. This is a wrapper error that usually contains a more specific inner message about what went wrong at the source level.

Common causes

1The data source server is down, restarting, or under maintenance
2A firewall rule is blocking connections from the gateway or Power BI cloud
3The database or file path in the connection string no longer exists
4Network timeout between the query engine and the data source
5An API endpoint (REST, OData) returned an unexpected status code or error body

How to fix it

1Read the full error message carefully — DataSource.Error always includes an inner error with more detail.
2Identify whether this is a connectivity issue (can't reach server) or a data issue (server reachable, query fails).
3Test connectivity from the gateway machine or from Power BI Desktop using the same connection string.
4For REST/OData sources, test the URL in a browser or Postman to confirm the endpoint is healthy.
5Check the data source's own logs or status page for outage or maintenance windows.
6If intermittent, consider scheduling refreshes at off-peak hours when the source system is more stable.

Frequently asked questions

Does this error affect multiple datasets at once?

If multiple datasets connect to the same data source, yes — all of them will fail until the source connectivity is restored.

Can this error be caused by a server migration or rename?

Yes — if the server name, database name, or connection string changed (e.g., during a cloud migration), Power BI still holds the old connection details. Update the connection in Power BI Desktop and republish.

Does this error appear in Power BI Desktop?

Sometimes — if you open the .pbix file and attempt a refresh, Desktop will surface the same connection error. This is useful for debugging without affecting the Service dataset.

Will the error resolve automatically once the source is back online?

Only if it was a temporary outage. The next scheduled refresh will succeed automatically. If the connection string changed or credentials expired, manual intervention is needed.

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