Forum Discussion
400 Error When Using On-Premises Data Gateway with Fabric Pipelines (SQL Server Source)
Hi everyone,
We were finally able to identify the root cause of the issue and resolve it, with the support of the Microsoft team, after submitting a support ticket.
After several troubleshooting sessions and reviewing backend logs from the On-Premises Data Gateway, the Microsoft team discovered that, despite updating the Gateway to the latest version, the Fabric pipeline capability was not properly activated on the gateway instance.
To resolve this, we had to uninstall and then reinstall the On-Premises Data Gateway.
We used the recovery key available to restore and remap the existing connections during the reinstallation process.Once we reinstalled the gateway and confirmed the Fabric pipeline capability was correctly registered, the connection through the Fabric pipeline started working as expected.
I hope this helps anyone who might face a similar issue.
Thanks to everyone who supported this thread!
Marcos
Hi everyone,
We were finally able to identify the root cause of the issue and resolve it, with the support of the Microsoft team, after submitting a support ticket.
After several troubleshooting sessions and reviewing backend logs from the On-Premises Data Gateway, the Microsoft team discovered that, despite updating the Gateway to the latest version, the Fabric pipeline capability was not properly activated on the gateway instance.
To resolve this, we had to uninstall and then reinstall the On-Premises Data Gateway.
We used the recovery key available to restore and remap the existing connections during the reinstallation process.
Once we reinstalled the gateway and confirmed the Fabric pipeline capability was correctly registered, the connection through the Fabric pipeline started working as expected.
I hope this helps anyone who might face a similar issue.
Thanks to everyone who supported this thread!
Marcos