Refresh failed and solved re-entering credentials

[Anonymous]

Hi,

I'm having daily refresh errors from different PowerBI reports with single connections to an Azure SQL DB.

The message errors are of the type:

• The key didn't match any rows in the table.
• The SELECT permission was denied on the object

If I try to refresh the dataset manually it fails again with the same error message, but if I re-enter the credentials from the Azure SQL connection and I refresh the dataset it works correctly.

The different reports use different credentials in some cases, but the password hasn't changed in any case.

¿What can be the origin of this problem?

I'm finding more than 20 daily refresh errors.

[venal]

@Anonymous 

Please refer the links.

https://community.powerbi.com/t5/Desktop/Expression-Error-The-key-didn-t-match-any-rows-in-the-table/td-p/186522

https://community.powerbi.com/t5/Desktop/Expression-Error-The-key-didn-t-match-any-rows-in-the-table/td-p/493013

https://community.powerbi.com/t5/Desktop/The-key-didn-t-match-any-rows-in-the-table-Table/td-p/335889

https://community.powerbi.com/t5/Desktop/powerbi-com-only-The-key-didn-t-match-any-rows-in-the-table/td-p/28933

There were lot of causes to to get the above error.

If the error comes, please try to refresh the data model from Desktop and publish the same to the same workspace.

If this post helps, then please consider Accept it as the solution to help the other members find it more
If this post was helpful may I ask you to mark it as solution and click on thumb symbol?

[Anonymous · Accepted solution]

Hi @venal the posts you show are related with code problems.

On all my cases, the reports refresh correctly after renew the credentials on datasource.

[nickyvv]

I was having the exact same issue today for an on-premises SQL database with a Windows (service)account. Strange thing is it only happened with one source.

The things I found:

• The Power BI gateway entry was disconnected due to failed impersonation I believe.
• I tested the service account directly on the database and that worked.
• I re-entered the (same) credentials as were already in the gateway and the error was gone

I have no idea what happened.