Forum Discussion
Urgent: Power BI Fabric Dataflow Refresh Failures - MashupException.Error with a 403
Hi tayloramy ,
I have checked and tried all things you listed above. Currently, the owner of dataflows/data warehouses/lakehouses is also Admin of the workspace with full access rights.
About the DataflowStagingLakehouse has been taken over by the Admins of the workspace after facing with the issues and after that we have raised ticket to Microsoft Support team.
- We have already tried to process somethings:
Access Manage connections and Gateways >> Check status to ensure all connections from Web/SharePoint are Online and active with Signed In of Admin Account with Authentication method: OAuth 2.0 / Privacy level: Organizational. - Inside the dataflows, we have unlinked all connection and re-link again with the Authentication: OAuth 2.0 , some dataflows can refresh successfully some tables inside the dataflows but with the last table which is ready to load to the data warehouse failed again with the error message: MashupException with “Microsoft SQL: Internal system error (0xa) (MWC service error: Server responded with error: 403)
- Re-entered all AOuth account, refresh successfull inside the dataflows, preview data table without errors... Published the dataflow again and still failed in refresh after that with the same error
Thanks again for your resoponse and guidances, but could you please recommend any other solutions which are able use PowerShells to investigate or detect all thing behind the scense and transfer the identity users / owner to the right one to solve the current problems?
Hope to hear from you soon!
Many thanks!
Hi BanNguyen9708,
At this point I think more telemetry from your environment is needed to troubleshoot what is happening.
Hopefully the support engineers who pick up your ticket are able to shed some light on it.
Once they are able to help you solve it, please post the solution here so future forum members willl be able to find it.
- BanNguyen970811 months agoFrequent Visitor
Sure! I'll but this is really a critical issue because a lot departments in my company rely on the HR data to build the closing month report. But at this time we must do everything manually and waiting for final solutions! If we fix it completely, I'll share in here to other memebers!
Thanks