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.
Welcome. I can also confirm no model errors here for a full week after making the change.
I am seeking guidance from Microsoft on whether future Gateway updates will overwrite this config setting, whether I'll need to continue to do it in the future, and what exactly it does.
Confirmed that my support engineer provided feedback to the dev team on this issue, and they hope to resolve it in future gateway releases. However, this config setting remains a viable tweak if needed in the future. There is no comprehensive documentation that I'm aware of regarding exactly what this or other settings in the config file do, so be sure to make a backup or check with MS before changing any others.