Forum Discussion
Advocate VData Refresh Errors after Enterprise Gateway upgrade
Same error here too of:
| Data source error: | {"error":{"code":"DM_GWPipeline_Gateway_DataSourceAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_DataSourceAccessError","parameters":{},"details":[],"exceptionCulprit":1}}} Table: Specialists where "Table" is always listed as something different. Have done everything you listed as well: configured CPUUtilizationPercentageThreshold to 70 from 0 Enabled query caching on jobs using import mode Enabled Large Semantic Model Storage Format Enabled Query Scale out Error is completely random, no consistent time or reason. Semantic model is nowhere near exceeding the 25GB size limit. MS just keeps requestintg logs, logs, logs but because the refresh failure throws randomly, we are having a hard time capturing it in logs and when we do submit, no reason is provided from Microsoft. Frustrating! |
Advocate Vhave been experiencing the exact same issue here for weeks. Error logs are of no help at all. Have you found a solution, or even a way to diagnose the problem?
motorayWe were given a solution that's worked well enough for us with the promise of Microsoft doing some kind of more permanent fix in a future gateway.
There's a configuration file--Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config. On our servers, it's here "C:\Program Files\On-premises data gateway."
Open the config file in a text editor and scroll down to almost the bottom. Find the "NextResultSkipped" setting and change the value from False to True. After that, restart your gateway and see if the failures stop. They did for us. I never got a satisfactory answer about why they stopped.
- kymramosrpo
Thanks for sharing! I've set it up just now. Hope to see some improvements soon. Will share the results here!
Was it more stable, kymramosrpo ? We did this today as well.