Share via

Check the linked service configuration is correct, and make sure the SQL Database firewall allows the integration runtime to access

Ravi Alwal 20 Reputation points
2025-02-26T11:21:04.7733333+00:00

Currently we are migrated all ADF pipeline, Datasets, linked service etc to the new Fabric environment. and during testing, we encountered an connectivity issue. As I am trying to create new linked service to point to the on-Prem Sql server. however getting below error:

Cannot connect to SQL Database. Please contact SQL server team for further support. Server: 'USSECVMPARASQ01.EY.NET\INST1,1367',

Database: 'AMT_Source', User: 'US\YJ861JD'. Check the linked service configuration is correct,

and make sure the SQL Database firewall allows the integration runtime to access.

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: TCP Provider, error: 0 - The wait operation timed out.), SqlErrorNumber=258,Class=20,State=0,

The wait operation timed out

Note: We created SHIR into the New VM and IR also running successfully.

SQL Server on Azure Virtual Machines

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. J N S S Kasyap 1,715 Reputation points Microsoft External Staff
    2025-02-27T06:55:11.18+00:00

    Hi @Ravi Alwal

    Thanks for posting your query!

    This issue facing a connectivity issue while attempting to establish a connection to your on-premises SQL Server from Azure Data Factory (ADF). The error indicates that the SQL Server may be inaccessible due to a network-related issue, such as an incorrect server name, disabled remote connections, or a firewall blocking access.

    To resolve this:

    Ensure that the SQL Server firewall allows inbound traffic on the relevant port (e.g., 1367) and that the on-prem network firewall is not blocking the connection from the SHIR machine.

    Ensure that the SQL Server is configured for remote connections and that the instance is reachable from the integration runtime machine.

    Test the connection to the SQL Server from the VM running the SHIR to ensure that network routes are properly configured.

    Double-check the SHIR setup and ensure it is running properly and can access the on-prem SQL Server.

    Increase the timeout settings in the ADF linked service configuration, as the issue might be caused by timeouts during the connection attempt.

    I hope this information helps. Please do let us know if you have any further queries.

    Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.

    Thank you.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.