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 VI hear you on with the frustration. I did finally get to the next level of tech support...and they wanted more logs. I've found two things that brought some relief--but we still see daily refresh failures.
1. For some reason we get Personal mode connections occasionally in our gateway connections list. We do not use Personal gateways. The Personal mode connections don't connect to anything and can't be changed. If we are careful to check and remove these connections, we get fewer failures.
2. I found that one of the gateway cluster servers was very low on hard drive space. I had our server folks increase HDD space on both servers in the cluster and bring them up to a higher spec in line with what Microsoft recommends for gateway cluster servers. There was a noticeable difference in # of refresh failures.
Maybe take a look at those and see whether you can get any relief that way.
