Refesh Error: The key didn't match any rows in the table.

[ElieK]

Hello,

I've been getting the following error when I try to refresh a dataset on Power BI Service.

Processing error: The key didn't match any rows in the table.
Cluster URI: WABI-CANADA-CENTRAL-redirect.analysis.windows.net
Activity ID: 334087f1-c7a0-4690-a362-c154e309f101
Request ID: 53827af0-728d-4c98-4d6d-494fdef65650
Time: 2022-06-14 18:00:00Z

The Refresh works with no issues when I do it on the Desktop version of Power BI.

Is there anyway to get a more detailed error message? Which table was the one that failed?

[v-henryk-mstf · Accepted solution]

Hi @ElieK ,

Generally, for this type of error message, the problem is caused by a Power Query query that is trying to join to a table or worksheet or something that has been deleted or renamed in the data source.
If this condition occurs in the service, ensure that the gateway connection is normal and then reconfigure the data source credential information.

Also refer to the following specific steps for possible causes of errors.

similiar solution as below:

Solved: Expression Error.: The key didn't match any rows i... - Microsoft Power BI Community

[Solved] Power BI Dataset Refresh Error – The key didn’t match any rows in the table | Data Awarenes...

If the problem is still not resolved, please provide detailed error information and related operation screenshoots. Looking forward to your reply.

Best Regards,
Henry

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[collinq]

Hi @ElieK ,

Unfortunately, this is not something that is always identical and easy to find.  I would start by making sure that you have the right credentials (re-enter them).

Then, confirm that the data source is actually accessible - is it still there?  Is the Gateway reaching it (if Gateway needed)?  Does the user you are using have permissions to that Gateway?

Then, is there a column in the Source that is not matching a step in the Applied Steps?  The desktop is more forgiving for this than the Service.  Double check that the Source didn't have a field name changed, then confirm that you don't have a step that is changing the name or step that uses a name that is no longer there (like a removed column or a step that is out of sync).