On premise Gateway refresh not working after changing computer password.

[Anonymous]

My organization has been using an on-premise data gateway (personal mode) from my laptop to upload an refresh data to PBI service. Recently, I had to change my computer password as required by out I.T. department. This caused several data sources (all are excel based files) to no longer automatically load. Thus impacted reports are no longer being refreshed automatically on a daily basis.
How can this be fixed? Has anybody else ran into this issue?

[v-jinweili-msft]

Hi @Anonymous ,

Would you Provide detailed information on the errors reported?

As the Power BI Personal Gateway is install as an application it will always run using the account and password you’re currently logged in with. So if you’re not logged into Windows the data won’t refresh and the scheduled will fail.

You need to go to refresh settings for the dataset. In Manage Data Sources, select Edit credentials to update the credentials for the data source to ensure that the username and password you use to log in to the data source are up to date.

Also, since you are changing the password for windows, we recommend that you download and install the Personal Gateway again and try it with your original Power BI account.

If the above methods still don’t resolve your issue, you can try clearing the cache of expired browser credentials.

For more information, you can refer to:

Troubleshooting Power BI gateway (personal mode)

Data refresh failure because of password change or expired credentials

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

[edhans · Accepted solution]

In personal mode, the service runs as you. Open the gateway on your PC and confirm you can still sign in to the service.

Once you've done that, go to the service and confirm all datasources are authenticated properly in the gateway config.

This is one reason it is best to use the Enterprise mode as it runs as a service and not as a user. And when possible, log into resources using a service account and not a user account.