Forum Discussion
Model Refresh Errors after June 2026 Gateway Upgrade Resolved Themselves?
- 1 month ago
Hi Karl-D1,
From what you've described, the gateway installation appears to have completed successfully, other semantic models and paginated reports continued to refresh successfully, and the affected semantic models eventually refreshed without any configuration changes .There is currently no published Microsoft Known Issue that describes intermittent DM_GWPipeline_Gateway_DataSourceAccessError failures following the June 2026 On-premises Data Gateway upgrade.
Since the issue resolved on its own, it appears to have been a transient condition rather than an ongoing gateway configuration issue.I'd recommend monitoring future refreshes to see if the behavior recurs. If it does, please capture the Activity ID, Request ID, Correlation ID (if available), Timestamp (UTC), and the gateway logs, then open a Microsoft Support ticket so the backend diagnostics can be investigated.
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn
Thank you.
Hi,
It looks like you already covered all the right troubleshooting steps. Since both your Dev and Prod models started refreshing successfully without any changes, it doesn't seem like there's an issue with your gateway installation or the semantic model itself.
This was most likely a temporary Power BI Service or gateway-related issue. I'd keep an eye on the refresh history over the next few days. If the same error starts happening again, then it's worth opening a Microsoft support ticket and sharing the gateway logs you already collected.
Hopefully it was just a one-time glitch, but it would be helpful to know if anyone else who upgraded to the June 2026 gateway has experienced the same issue.
Hope this helps!
Thanks!