Forum Discussion

chelly911's avatar
chelly911
Copper Contributor
Oct 03, 2024

Issue with Azure Data Factory Pipeline Connection to SQL Server

 

Hi everyone,

I’m encountering an issue with my Azure Data Factory pipeline that uses a copy activity to transfer data from MariaDB. The connection is established using a self-hosted integration runtime, and everything seems to be configured correctly. The test connection is valid, and I can preview the data without any issues.

However, when I run the pipeline, I receive the following error:

```
ErrorCode=SqlFailedToConnect,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Cannot connect to SQL Database. Please contact SQL server team for further support.
Check the linked service configuration is correct, and make sure the SQL Database firewall allows the integration runtime to access.
'Type=System.Data.SqlClient.SqlException,Message=A network-related or instance-specific error occurred while establishing a connection to SQL Server.
The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server),'
```

The pipeline used to work fine before, and I haven't made any changes to the linked service configuration. I have also confirmed that the IP address used by the self-hosted IR has been added to the firewall rules of the SQL server, but I’m not an admin, so I can’t verify it fully.

Has anyone encountered a similar issue or have suggestions on how to troubleshoot further?

Thanks in advance!

 

  • MegaAstronomy's avatar
    MegaAstronomy
    Copper Contributor

    chelly911 

    I'm seeing this same issue on a CopyData task in DataFactory pipeline that had been running fine until 10/21/2024. No changes to production it just stopped working. I am getting the same error you are getting. I've tested the Linked Service and this connects to the Azure SQL Db successfully and we use this Linked Service elsewhere in the pipeline without incident, it is only in this CopyData shape that the problem happens. Please let me know if you figured this out. Thanks.

Resources