Forum Discussion
Invalid Connection Credentials
I recently updated my M365 credentials and now my reports published in Power BI service will not refresh. The error received is:
'Something went wrong, Invalid connection credentials'
We have an on-prem gateway which is showing as available, and the reports refresh fine through PowerBI Desktop. Any ideas where I need to update my credentials to allow the automated refresh to work again?
Thank-you, not quite the answer but put me on the right path! My datasource credentials are set to windows authentication. I had put my M365 details there when I updated, however I had also updated my on prem creds, which is what should be there. Your comments helped me investigate further and this is now resolved.
Appreciate your time in helping out.
2 Replies
Hi swhistance ,
If the source for your data is an excel file , csv file or something stored on disk, the service account that the Gateway is running under should have access to that share. Usually, the best way to do this when using gateways is to have a central share where you store files that Power BI uses to refresh its datasets.
I have also found a similar post, please refer to it to see if it helps you.
Solved: Invalid connection credentials - Microsoft Power BI Community
-
Based on error message, it seems like your credentials not have permission to access your dataset, I'd like to suggest you double check on your database setting if any changes on it.
In addition, please share more detail content to help us clarify your scenario.(e.g. datasource type, connection mode, snapshots, datasource credentials settings, refresh log, gateway logs...)
If it still does not help, please provide more details.
Best Regards
Community Support Team _ Polly
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thank-you, not quite the answer but put me on the right path! My datasource credentials are set to windows authentication. I had put my M365 details there when I updated, however I had also updated my on prem creds, which is what should be there. Your comments helped me investigate further and this is now resolved.
Appreciate your time in helping out.
-
