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.
We are experiencing the same issue. We run two Capacities and two clusters of on-prem data gateways. Following successful updates on both clusters on Friday (17/07) we have been experiecing multiple model refresh failures across both clusters.
- Different models each day
- Different gateway data sources (many models use the same source, most refresh some fail)
This morning a model refresh failed TEN times before succeeding on the 11th attempt. This is significantly impacting our ability to deliver our products.
Error sample:
Data source error: 0xC1450012: {"error":{"code":"DM_GWPipeline_Gateway_DataSourceAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_DataSourceAccessError","parameters":{},"details":[],"exceptionCulprit":1}}} 0xC112001C: The operation was canceled.. The exception was raised by the IDbCommand interface. 0xC11C0006: The current operation was cancelled because another operation in the transaction failed.
Hi pixmeister ,
Thanks for letting me know I'm not alone here.
I ended up opening a support case.
I don't fully understand how all of these settings work, or what this really changes, so I don't want to encourage you to do this unless you are comfortable with it.Below is what I was advised to do. I've not had a refresh error on the two gateways since doing this on Monday. However, even when I was experincing the problem, I had a couple days when it didn't happen. So if I make it to Monday the 27th without any refresh errors, it would lead me to belive that this resolved the issue.
Suggestions:
To mitigate this issue, we suggest updating the Gateway configuration by enabling the following setting:
"NextResultSkipped = True" ------ intially it is set to False, need to change it to True and save the changes to the file.
This setting should be added to the configuration file located at: C drive or whichever drive your gateway is installed in ----C:\Program Files\On-premises data gateway\Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config
Thanks so much for posting this. I've had a support ticket open for days but the support has not been great. I implemented this fix and have not had a refresh failure since. You'd think MS would have a knowledge base for this kind of thing and, your engineer having provided the resolution, it would be a short hop for my engineer to find the same info. Oh well.
Fabric Community wins the day
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.
