Forum Discussion
Model Refresh Errors after June 2026 Gateway Upgrade Resolved Themselves?
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.
I just had to roll back our gateway servers to before the June update. I did the other workarounds to fix data import reports for Oracle but none of the workarounds I could find fix DQ to Oracle. I can fix it in power BI desktop when I turn off 'Enable using Bundled Oracle Managed ODP Provider for Import Mode' & for Direct Query Mode but when the report it published to Fabric it breaks again ... I dont see any option in Fabric Admin Portal to turn this off