Upgraded gateways cannot refresh with iAuditor Connector ( 3000.194.16 )

[macmy034]

Hey all;

Our PowerBi Gateways have just been upgraded to version 3000.194.16 - which broke our iAuditor connector then. It was an old version from 2022-04 so a good opportunity to upgrade everything. At the same time, I noticed the regedit had not been performed - so I completed that on both servers - I managed to get a refresh occuring for all our PowerBi reports that source from iAuditor.

This morning I have been met with errors from every single one of our iAuditor PowerBi reports and cannot refresh them at all.

2 Gateways, both running 3000.194.16 and 1.23 iAuditor connector file with regedit.

Does anyone have any insight into the 3000.194.16 gateway clashing with the iAuditor connector?

Local refresh occurs fine on these PowerBi reports.

[macmy034]

This may be related to the latest Gateway release by Microsoft - people are rolling back to September versions; https://community.fabric.microsoft.com/t5/Service/October-Update-Gateway-Issue/m-p/3499448/highlight/true we may be doing the same in the future so ill retract this issue if its the cause.

[mrpleebus]

Hi everyone,

Is this still a known issue? I'm currently trying to configure our gateway to run the SafetyCulture connector in service and am getting strange errors. I'd rather not raise the request to roll back our gateway version until I'm certain it's the issue.

Can confirm that it's working in desktop fine.

Thanks

[macmy034]

Hi everyone,

Is this still a known issue? I'm currently trying to configure our gateway to run the SafetyCulture connector in service and am getting strange errors. I'd rather not raise the request to roll back our gateway version until I'm certain it's the issue.

Can confirm that it's working in desktop fine.

Thanks

Looks like all's going well on this end. We've done an update to the gateway latest version and I put in the newest safetyculture connector - just had to copy it across to the directory. Noticed a little issue where our gateways were storing the file in separate spots, so I sorted it out to make sure it's the same for both. All good since I did that. So, what problems are you encountering?