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
Good Day Fabric Community,
I have been through your problem, that you have faced issue with On premises
Data Gateway to Fabric in "Copy Activity" inside a Pipeline , and i have seen that as a solution that
every time you have to uninstall and again install data gateway to connect , but i
have had face same almost issue while connecting On premises to Fabric.
From MY SQL to Fabric journey i have experienced below:
I would like to say that do not unistall and Install Data gateway everytime , when you get
new data connection, instead you do what i have posted in below Screen shot ,
what i did was My SQL server with different Database (ex:Databse 1 and Database 2)
(both Database located in same My SQL on premises server ) i transfer to different Fabric Workspace.
with same data gateway i have connected and do Copy Activity (Traditional)
Copy Activity ( inside a pipeline) without uninstall Gateway.
Gateway Link : https://www.microsoft.com/en-us/power-platform/products/power-bi/gateway
Sol : Plese do clean your browser catche memory first .
Sol: First try to test connection with Normal Copy Activity (traditional) not with inside pipeline.
Sol : hit and with refresh and Test connection
Sol: Wrost Sitution Change Pileline Name for Testing connection .
Sol: When you can establish a connection with Normal Copy Activity (traditional) then Duplicate the Tab and take a
pileline and do inside Copy Activity . and remove 1st tab source location and the connect 2nd Tab
Source and Test connection . ( So my intension , i dont want to unistall my Gateway)
I have store my data into Lakehouse in File (format .csv)
Sol : So what you have to do is : Activate the data gateway every time just before the connection and
do paste your email credential every time after open on prem data Gateway. just like my below
document . (Do refresh and test connection 5 to 10 times and then do test connection)
Please check my Screenshot , hope this can solve your issue.
Same Gateway use for this Activity,Workspace Different. (pic attached)
Same Gateway was use in Different Activity , Different Workspacce, (pic attached)
If you like my post , please like and send kudos.
Below Pic attached.
SQL AuthenticationGateway ConnectNormal Copy(traditional)Duplicare TabFill DestinationRun PipelineSame Gateway ,WS:TestcommunityWorkspaceThank You ,
Soova Kamall