Gateway Update causes DataFormat.Error when Refreshing
We are having an issue with our On-Premise Data Gateway when upgrading to the latest version (August 2018). We currently have the February 2018 version installed and everything works perfectly fine and as intended. However, when we upgrade our gateway, we get a DataFormat.Error as soon as we attempt to refresh. The specific error code we get is "-2147467259". We have tried everything from a reboot to updating the Access Engine, but the only fix is to uninstall the gateway and revert back to the February edition that we have saved. Has anybody else had this problem/know what is causing it? We'd like to be able to keep up to date with the gateways but we can't do that if it breaks our data refreshes.
I've done some research on this problem and seen that the gateway doesn't support connections to Access, but this can't be entirely true because that is the only way that our data is connected to the cloud and it works fine in the old gateway. We cannot figure out why this new version breaks it.
There is no Access connector under the supported data source list for On-premise Data Gateway. Do your report connect to local Access file as data source? If yes, would you please try On-premise gateway Personal mode to set scheduled refresh? If the access file is hosted online, there is no need to configure data gateway.
Community Support Team _ Yuliana Gu If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
The current version of the gateway that we are using supports Access integration and running the installer for the new gateway doesn't allow us to select which mode we wish to install. It only prompts us to update it, so I believe that what we are updating to should also support Access. However, our data refreshes still fail, even with the newest gateway installation.
If we uninstall our current version completely and then install the personal gateway, our fear is that it will not automatically run when our server starts up since it runs as a user application and not a service. What is the best way to continue updating our gateway so that it can integrate with Access and be guaranteed to start and run with the server in the event of a reboot? I'm hesitant to belive that Microsoft would remove a feature that integrates with their own product (Access), so what other approaches can we take to make this work the same way that it has been?