What causes DM_ErrorCode_BackEnd_QueryExecutionFailed?

A measure or calculated column uses a DAX function that references a column that no longer exists. Row-level security expressions contain syntax errors or reference invalid tables. A relationship in the data model references columns with incompatible data types. The data source returned values that cannot be cast to the column's defined type. A partition query failed because the underlying source schema changed

How do I fix DM_ErrorCode_BackEnd_QueryExecutionFailed?

Open the dataset in Power BI Desktop and attempt a manual refresh — the error trace in Desktop is usually more detailed.. Check for broken DAX measures using the 'Performance Analyzer' or by inspecting the Error list in the model view.. Verify all relationships point to columns that still exist and have compatible types.. Review any calculated columns or RLS expressions for references to removed columns.. If using partitions (Premium), check each partition's source query in Tabular Editor or SSAS Management Studio.

High severitydata source

Power BI Refresh Error:
DM_ErrorCode_BackEnd_QueryExecutionFailed

What does this error mean?

The Analysis Services engine (the backend that processes your data model) failed while executing a query against the data source. This error wraps backend execution failures that occur after the gateway has successfully retrieved the data.

Common causes

1A measure or calculated column uses a DAX function that references a column that no longer exists
2Row-level security expressions contain syntax errors or reference invalid tables
3A relationship in the data model references columns with incompatible data types
4The data source returned values that cannot be cast to the column's defined type
5A partition query failed because the underlying source schema changed

How to fix it

1Open the dataset in Power BI Desktop and attempt a manual refresh — the error trace in Desktop is usually more detailed.
2Check for broken DAX measures using the 'Performance Analyzer' or by inspecting the Error list in the model view.
3Verify all relationships point to columns that still exist and have compatible types.
4Review any calculated columns or RLS expressions for references to removed columns.
5If using partitions (Premium), check each partition's source query in Tabular Editor or SSAS Management Studio.

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