Forum Discussion

Rakuka's avatar
Rakuka
Frequent Visitor
3 months ago
Solved

Issue while trying to use an on-premises SQL Server source in Microsoft Fabric pipeline

Hi Fabric team, Good morning I am facing an issue while trying to use an on-premises SQL Server source in Microsoft Fabric through an on-premises data gateway.   Environment Fabric trial capacit...
Data Pipeline
  • v-tejrama's avatar
    v-tejrama
    3 months ago

    Hi Rakuka ,

     

    I would take a moment to thank Lodha_Jaydeep  , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

    I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

    Thank you.

Lodha_Jaydeep's avatar
Lodha_Jaydeep
Solution Sage
3 months ago

Hi Rakuka,

 

Thanks for reaching to community, will happy to assist. Localhost on the gateway configuration would not be work I think. Below is the reasons and fixes you can try.

Root Cause

localhost doesn't work with the on-premises data gateway. The gateway runs as a Windows service under a different identity and cannot resolve localhost the same way SSMS does on your machine. This is why the connection appears created and online but never becomes fully usable.

 

Fix - Replace localhost with Machine Name (Do This First)

Instead of localhost,1433 use your actual machine hostname:

  1. Find your machine name:
 
   Run → cmd → type: hostname
  1. In Manage Connections and Gateways, delete the current OBT_SQL_Local_1433_OneBridge connection
  2. Recreate it with:
    • Server:  YOUR-PC-NAME,1433 or YOUR-PC-NAME\INSTANCENAME
    • Database: OBT
    • Gateway: OneBridge
    • Authentication: Basic (sa)\Any if you create new.

 

Probably this will fix your issue. Please have a look at the below screenshots for the same.

 

Note: New connection with the machine name should be tested with the SSMS first if you are able to connect. Also, as you are able to create gteway connection so, I am assuming that Remote/TCP connections are allowed for your SQL server.

  • Rakuka's avatar
    Rakuka
    Frequent Visitor
    3 months ago
    Hi Jaydeep,
     
    Thank you for your suggestion.
     
    We had already tested these paths during troubleshooting. Port 1433 is confirmed to be working, and SQL Server is successfully reachable from SSMS using the same machine where the gateway is installed. We also tested multiple server name variations, including localhost,1433, host/machine-name based formats, and named-instance style formats.
     
    In addition, we verified that the OneBridge gateway is online, the gateway network diagnostics completed successfully (34/34 tests passed), and the Fabric SQL connection is bound to the gateway cluster. We also tested in different workspaces and browsers, deleted and recreated the faulty connections, and re-created a clean on-prem SQL Server connection several times.
    Despite all of this, the connection still does not become fully usable inside Fabric Copy activity, and we also encountered the errors like error 26 and “undefined not found in linked-service-registry.” Because of that, this now appears to be beyond a basic hostname, port, or TCP configuration issue.
     
    I also doubted that because Fabric trial version is having some inherent features' non-availability. 
     
    But when I tried your solution I got error 26 saying "Fabric cannot locate the specified SQL Server instance or database" in source section of the pipeline's copy activity.
     
    Regards
    ~~~~~~~~~~~~~~~~~~~~
    Rakuka
    • Lodha_Jaydeep's avatar
      Lodha_Jaydeep
      Solution Sage
      3 months ago

      Hi Rakuka,

       

      Thanks for getting back to me. I’m also using a Free Trial capacity, and the configuration shown in my screenshots is working as expected.

      Before we try the new Server/Machine name in Fabric again, could you confirm if you can successfully connect using that same name within SSMS? This helps us rule out any local connectivity issues.

      Regarding the error message 'undefined not found in linked-service-registry,' this actually appears to be a Fabric backend service registration failure rather than a misconfiguration on your end or a network issue.

      Since you’ve already attempted to re-configure the gateway multiple times without success, we might want to try a different authentication approach.

      could you test using Windows Authentication with your specific username to see if that bypasses the registry error? Be make sure to not skip connection you can get the window Auth user name from the SSMS and password should be used for the log-on to the machine.

       

       

       

       

      I’m happy to keep digging into this with you. If this helps resolve the issue, please consider marking this as the Accepted Solution so it can help other community members. Kudos are always appreciated!

      • Rakuka's avatar
        Rakuka
        Frequent Visitor
        3 months ago

        Thank you for the follow-up, Lodha_Jaydeep

        Yes, we already completed that validation. Connectivity was tested from SSMS on the same machine where the gateway is installed, and port 1433 is working. Multiple server-name formats were also tested during troubleshooting, including localhost,1433, machine-name based formats, and named-instance style formats. In addition, the OneBridge gateway is online and the gateway Network ports test completed successfully (34/34 passed).

        We also agree that the undefined not found in linked-service-registry message looks more like a Fabric backend/service registration issue than a local SQL Server, gateway, or firewall issue. That is consistent with the fact that the problem persists even after repeated reconfiguration, connection recreation, workspace changes, and browser changes.

        Windows Authentication was also attempted earlier, in addition to SQL authentication, and neither path made the connection fully usable inside Fabric Copy activity. Based on the full set of checks completed so far, this now appears to be beyond a basic connectivity or authentication configuration issue.