Forum Discussion
On-premises Data Gateway not starting workers
Hi tayloramy,
We have an old SAP ECC based on a Sybase ASE environment. I have set up an ODBC connection from a local VM to Sybase, and am using that with the gateway. From Fabric, the test does validate (both to Sybase and to the Fabric SQL Server that I have set up in the cloud to store data). Indeed, the pipeline was successful for some time; a couple of days ago it started to give problems, as mentioned in my first post.
Task manager does not show any bottleneck in CPU or memory, also in the situations where workers do start.
Today I opened a ticket with Support. After some investigation, we decided to uninstall and reinstall the gateway. That worked. So for the moment the problem is solved, although we could not figure out what was happening exactly. If anybody has any idea... I'm still pretty convinced that it has something to do with the perf counters, possibly some corrupted cache that has been wiped off by the fresh installation.
The fact remains that when I issue a restart of the gateway service, the existing workers crash instead of shutting down gracefully.
- arabalca
Super User
Hi EMenotti ,
One of the most silent issues you can have with the Gateway is precisely this: Fabric does not always clearly alert you that the problem is there.
The connection may appear to be correct, the Gateway may be online, and everything may seem to be working properly in the portal. But when it comes to actually moving the data, it simply does not work.
That is why, in this case, the classic IT solution of “restart it and it works again” makes more sense than it might seem. Restarting the service can restore connectivity, but it can also hide the real problem: an outdated Gateway.
If the Gateway has not been updated for more than six months, you may already be running a version that is outside the support lifecycle. Microsoft officially supports only the latest six monthly versions of the on-premises data gateway and, in the case of Fabric, recommends using the latest version to benefit from improvements in compatibility, reliability, and security.
So, the recommendation should not be to wait until it fails before updating it. At a minimum, you should have a process in place to update it before it goes out of support—approximately every six months—although for me, the ideal approach would be to establish a quarterly update schedule.
More information about Gateway updates: https://learn.microsoft.com/es-es/data-integration/gateway/service-gateway-monthly-updates
If this helped, please consider giving it a Like. If it solved your issue, please mark it as the Accepted Solution to help others facing the same problem
Thanks
