Issue Accessing On-Premise Teradata Source via Data Pipeline in Microsoft Fabric

[nauduberteau78]

Hi everyone,

I'm encountering an issue when trying to access an on-premise Teradata data source from the Data Pipeline component in Microsoft Fabric. This source is accessible via the Power BI gateway, and I can successfully connect to it from other components such as Semantic Models, Dataflows Gen1, and Dataflows Gen2—so the gateway setup seems to be working correctly in general.

However, when using the Data Pipeline, the connection fails. Based on the error messages and behavior, it appears that the Integration Runtime is unable to resolve the DNS of the on-premise Teradata server.

I attempted to configure my company's proxy settings in the FabricWorker.exe.config file, but this did not resolve the issue. It's possible that the proxy configuration is either incorrect or not applied in the right section of the config file.

Has anyone else experienced a similar issue or found a workaround for DNS resolution problems in the Data Pipeline component when using on-premise sources via gateway? Any guidance or documentation references would be greatly appreciated.

Thanks in advance!

[v-pagayam-msft]

Hi @nauduberteau78 ,
I hope the suggested solution worked for you. If your issue is resolved, kindly accept the post as a solution — it helps the community identify helpful answers more easily.
Thank you.

[v-pagayam-msft]

Hi @nauduberteau78 ,
Just checking in — did the solution provided help resolve your issue? If yes, please consider marking it as the accepted answer so it can help others facing a similar challenge.If still needed further assistance, feel free to reachout!

Thank you.

[nauduberteau78]

Hi @v-pagayam-msft ,

I'll tried to add my proxy settings in Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config and it still not working.

Regards

[v-pagayam-msft]

Hi @nauduberteau78 ,
Thank you for confirming you updated the GatewayCore.dll.config file. Since it is still not working, please double check that the proxy settings are added correctly under the <system.net> section, and restart the gateway service after changes.
Try running ping or nslookup for your Teradata server from the gateway machine to check if it is a DNS issue. If that fails, consider adding the hostname to the hosts file or testing with the server's IP address.
Finally, ensure your Data Pipeline activity is configured to use the on-prem gateway, as not all pipeline activities do by default. 
Please refer the below documents for detailed understanding:
service-gateway-install
service-gateway-proxy
netsh


I hope this resolve your query.If this answer meets your requirements,consider accepting it as solution.

Regards,
Pallavi G.

[v-pagayam-msft]

Hi @nauduberteau78 ,
Have you got an opportunity to review the information provided. Please feel free to contact us if you have any further questions. If the response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.

[v-pagayam-msft]

Hi @nauduberteau78 

Can you please confirm once

Which Integration Runtime are you using for the Data Pipeline?
Is it the same on-premises data gateway that supports other components, or are you using a self-hosted Integration Runtime (SHIR) configured via Azure Data Factory?

[nauduberteau78]

Hi @v-pagayam-msft 

Thanks for your reply.

I'm using the IR integrated with the on-premise gateway (April version)

Regards,

[v-pagayam-msft]

Hi @nauduberteau78 ,

Thanks for letting us know you are using the April version of the gateway's Integration Runtime.

Since your Teradata source works in other Fabric components but not the Data Pipeline, and you’re hitting a possible DNS issue, please find the below steps :

1.Make sure the Data Pipeline uses the same gateway as the other components. Verify the Teradata connection settings.

 2.Check the below guide to update Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config instead. Restart after changes.
https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-proxy

Hope this resolve your query.If so,give us kudos and consider accepting it as solution.

Regards,
Pallavi.