Forum Discussion
Advocate VPERSONAL GATEWAY update: Your data source can't be refreshed because the credentials are invalid.
Trying to set up Pro version of Power BI - I already had the Personal Gateway setup - but on PowerBI.com it offered to update to a newer version of the gateway.
After I did this - on all my data sources it says my credentials are invalid. Please update credentials and try again. When I do this- I just keep getting the same error.
I try to do it from PowerBi.com (in the settings section for datasets) and I've also tried doing it from the Desktop and updating my data sources from there. Still doesn't work.
Any ideas on how to fix this issue and / or what caused it?
Are you only using services or are you using the desktop version as well? If your files are created in the desktop version and if that version does not match the version of the Gateway, they will not communicate. Update the desktop version and this should resolve . . . but only if you created the files in the desktop version.
If that doesn't work, clear your browser history, cache, and cookies to start fresh. If all else fails, run a Fiddler Trace and send in a ticket.
hi dbadmin - I had the same issue a while ago. Fixed by uninstalling Power BI and making sure to download the latest version. then reuploading the pbix files. Fixed it.
10 Replies
- elliotdixon
Responsive Resident
hi dbadmin - I had the same issue a while ago. Fixed by uninstalling Power BI and making sure to download the latest version. then reuploading the pbix files. Fixed it.
My error message read: "Your data source can't be refreshed because the credentials are invalid"
Babak Kakavand published a video on youtube that is shorter than one minute long that demonstrates how to resolve that issue. The title is "how to reset saved credentials in Power BI."
The error lies in the credentials set in the original source file, not in any settings reached within the workspaces. At least in my case, it has nothing to do with the gateway or permissions set there. The procedure demonstrated by Babak resolved my issue. Had the error message simply informed the user WHERE the credentials are invalid, that might have saved several days trying to resolve this issue.
Thank you BABAK KAKAVAND for the great video.
Please note however, this solution worked for me only with pbix files. I was unable to change the credentials to access an Excel file. Still looking for a solution when excel is the "end point."
Dasrotrad a/k/a Robert Cline
GTRHelper III
I had this same error not to long ago after changing my Windows password. After much research, the only thing that fixed it was resetting my PowerBI password and logging in again to the dataset settings. Hope this helps
- dbadmin
The only thing with that is I HAVEN'T changed my windows password - or Power BI password. They've stayed the same. The only thing I did different, was update the Personal Gateway.
That's when I started having issues with the datasets.
- kcantor
Community Champion
Are you only using services or are you using the desktop version as well? If your files are created in the desktop version and if that version does not match the version of the Gateway, they will not communicate. Update the desktop version and this should resolve . . . but only if you created the files in the desktop version.
If that doesn't work, clear your browser history, cache, and cookies to start fresh. If all else fails, run a Fiddler Trace and send in a ticket.
Hi,
I am also getting the same error after changing my Windows password. My PowerBI.com password is connected to the windows credential. So, after your review when I tried resetting my PowerBI.com password. It read something like this:
"Please contact your admin
We've detected that your user account password is not managed by Microsoft. As a result, we are unable to automatically reset your password.
You will need to contact your admin or helpdesk for any further assistance."Could you please help on this. Any suggestions are welcomed.Thanks & Regards,AaspruhaI had this issue a while a go. And I openon the edit crediential and changed Authontication method from Basic to OAuth2. It verified my credential and it worked.
