Forum Discussion
Advocate VData Refresh Errors after Enterprise Gateway upgrade
Super UserAfter upgrading to the October 2024 gatewaywhich one?
Did you notice the "Trusted Server" discussion in the release notes?
Advocate VI've just upgrade to 242.8. I hadn't seen the "Trusted Sever" discussion. Can you point me to that?
- lbendlin
I have had the same issue, but adding all the servers in the Config file as Trusted SQL servers, have resolved it! It doesnt look like a bug but something that we actually have to do going forward?? Can anyone confirm? Thanks
Link:On-premises data gateway October 2024 release | Microsoft Power BI Blog | Microsoft Power BI
- motoray
Wish that had resolved it for me. We'd skipped several versions of the upgrade since June in the hopes one of the newer versions would fix it.
- motoray
I have a ticket open now. I figured I'd try from both directions. At the moment, Microsoft is still having me troubleshoot really basic things and I'm hoping someone in the community has already seen (and fixed) this.
AMD0791Advocate IV
Did you ever get more information or resolution? I am seeing the same issue.
I haven't checked on the config for trusted servers, but that seems like it would be an all-or-nothing proposition and it would never work instead of random, sporadic errors.
Thank you!
- motoray
Never mind, I did find how to set it up over here:
https://learn.microsoft.com/en-us/power-query/connectors/sql-server#sql-server-certificate-isnt-trusted-on-the-client-power-bi-desktop-or-on-premises-data-gatewayWe don't use encrypted connections internally yet, so this may very well have something to do with it.
Your solution is so great lbendlin
Hi, motoray
The current error is that it is now the default behavior for all PBI desktop and gateway versions that are equal to or higher than the February 2024 release.
Solved: Assistance Required with SQL Server Standard Mode ... - Microsoft Fabric Community
Best Regards
Jianpeng Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- motoray
Unfortunately in my case this did not correct the problem. I continue to have refresh failures after adding trusted SQL servers to the config. Same error as below--with the name of the table randomly being a table from the model.
{"error":{"code":"DM_GWPipeline_Gateway_DataSourceAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_DataSourceAccessError","parameters":{},"details":[],"exceptionCulprit":1}}} Table: Random Table Name.
Hi ,please let me know if you found any solutions for this ,I am facing similar issue.
- motoray
I was just on a call with Microsoft again this morning. Have to upgrade to the latest Gateway again and they grabbed log files, but no real progress.
