Forum Discussion
semantic model refresh fail after credential update
Hi All,
Our business analist reset his office365 password and with that his fabric and powerbi. The semantic model for our master dashboard now fails to refresh with an error. I suspect this was caused by the credential change.
When he opened his app on his laptop, indeed some of the queries in his model had exclemation marks , stating a credential error. Selecting those queries, clicking sign in, allowed the queries to refresh, but the semantic model in fabric (powerbi.com) still fails to refresh. Is there a location where we can reset all his credentials so it starts working again at powerbi.com (or do we need to do something on the app and republish?)?
We see that some tables work, but as soon as it reaches one it cant authenticate , the whole refresh fails. Below a sample of the error, with at the end the actual table that has the credential issue.
{"type":1,"value":"-.xyzabc123.fabric.microsoft.com;wh"}},{"code":"Microsoft.Data.Mashup.CredentialError.Reason","detail":{"type":1,"value":"AccessUnauthorized"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.DataSources","detail":{"type":1,"value":"[{\"kind\":\"SQL\",\"path\":\"xyzabc123-.datawarehouse.fabric.microsoft.com;wh\"}]"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.Reason","detail":{"type":1,"value":"AccessUnauthorized"}}],"exceptionCulprit":1}}} Table: Incidents - Incident type subcategory.
Any help appreciated a lot!
Thanks Hans
Hi smeetsh
This usually happens because the password change invalidates the stored credentials in the Power BI / Fabric service. Fixing it in Desktop only helps locally the refresh in the service still uses the old credentials.
Go to your semantic model in the Power BI service >> Settings >> Data source credentials >> re-enter the updated login details for each data source (SQL, Warehouse, etc.). Once those are saved, the refresh should start working again.
If a gateway is involved, make sure credentials there are also updated. In most cases you don’t need to republish the PBIX just updating the service credentials is enough.
3 Replies
Hi smeetsh
This usually happens because the password change invalidates the stored credentials in the Power BI / Fabric service. Fixing it in Desktop only helps locally the refresh in the service still uses the old credentials.
Go to your semantic model in the Power BI service >> Settings >> Data source credentials >> re-enter the updated login details for each data source (SQL, Warehouse, etc.). Once those are saved, the refresh should start working again.
If a gateway is involved, make sure credentials there are also updated. In most cases you don’t need to republish the PBIX just updating the service credentials is enough.
Hi smeetsh
Have you tried the fix below? If not please follow these stepsIn Power BI Service
- Sign into powerbi.com and go to the workspace containing the master dashboard semantic model.
- Click the ellipsis (…)/More options beside your dataset (semantic model) and select Settings.
- Under Data source credentials, look for any sources with errors or prompts.
- Click Edit Credentials. Re-enter the correct authentication details, choosing OAuth2 > Organizational Account where applicable, then sign in with the updated Office 365 credentials.
- Click Apply to save.
- Manually trigger a refresh after updating the credentials to ensure refresh now succeeds.
- If there are multiple data sources, repeat the process for each connector listed with an error.
Credential updates must be completed in the Power BI Service, as changes in Power BI Desktop alone will not resolve service/cloud refresh issues. Completing these steps should restore the automatic refresh and resolve credential-related failures.
🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.
💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.
🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.
🔗 Curious to explore more? [Discover here].
Let’s keep building smarter solutions together!
Update on this from my end. There was actually also an on-prem gateway connection in there (which I wasn't aware off), even though it wasn't actualy used to pull data, that is the connection that caused an error. We updated the connector it used and that solved it. rohit1991 provided the last bit of the puzzle, much thanks 🙂
