Forum Discussion

marcos-1992's avatar
marcos-1992
Regular Visitor
1 year ago
Solved

400 Error When Using On-Premises Data Gateway with Fabric Pipelines (SQL Server Source)

Hello everyone, We are encountering a persistent issue when trying to connect a Fabric Data Factory pipeline to an on-premises SQL Server database using the On-Premises Data Gateway. The same connec...
data engineering
data pipeline
  • marcos-1992's avatar
    marcos-1992
    1 year ago

    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

marcos-1992's avatar
marcos-1992
Regular Visitor
1 year ago

Hi v-lgarikapat,

Thank you for your response and for sharing the documentation.

We’ve followed all the recommended steps and are using the same login type that works successfully with both Dataflow Gen2 and Power BI. Unfortunately, the issue still persists within the Fabric Pipeline.

We also confirmed that the On-Premises Data Gateway instance running on the server is the only one configured and active.

We’ll continue testing with different configurations, and if we’re unable to resolve it, we’ll proceed with opening a support ticket.

Thanks again for your assistance!

 

Best regards,
Marcos

  • v-lgarikapat's avatar
    v-lgarikapat
    Community Support
    1 year ago

    Hi marcos-1992 ,

     

    Thanks for the update and for reviewing the setup on your end.

    We appreciate your efforts in testing different configurations. If the issue persists, opening a support ticket would be a good next step.

    Also, please continue to share any updates here, as it will help other community members find and follow the solution more easily.

    Feel free to reach out if you have any other questions.

     

    Best regards,
    Lakshmi Narayana

    • v-lgarikapat's avatar
      v-lgarikapat
      Community Support
      1 year ago

      Hi marcos-1992 ,

       

      I wanted to follow up and confirm whether you’ve had a chance to review the information we provided.
      If you have any questions or need further clarification, please don’t hesitate to reach out.

      Additionally, have you had a chance to raise a support ticket regarding this issue?

      If you’re still encountering any challenges, we’d be happy to assist you further.

       

       

      Best Regards,

      Lakshmi Narayana

      • marcos-1992's avatar
        marcos-1992
        Regular Visitor
        1 year ago

        Hi v-lgarikapat,

        Thank you for the follow-up.

        We haven’t yet been able to resolve the issue. We're currently in the process of making changes to the subscription associated with the Fabric instance, which are required to submit the support ticket. Our goal is to have the ticket created by tomorrow.

        As soon as we receive any insights or updates from the Microsoft Support team regarding the root cause, we’ll share the details here in the thread.

         

        Thanks again for your continued support.

        Best regards,
        Marcos