Forum Discussion
Issue while trying to use an on-premises SQL Server source in Microsoft Fabric pipeline
- 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.
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:
- Find your machine name:
Run → cmd → type: hostname- In Manage Connections and Gateways, delete the current OBT_SQL_Local_1433_OneBridge connection
- 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.