Share via

Error: 11402 -The value of the property '' is invalid: 'The remote name could not be resolved.

Rohit Kulkarni 686 Reputation points
2024-05-13T14:13:42.9766667+00:00

Hello Team,

I am using the private endpoints in Azure Data Factory and trying to connect On premises database and getting the error :

The value of the property '' is invalid: 'The remote name could not be resolved: 'ServerName''.

The remote name could not be resolved: 'ServerName'

Please advise

Thanks

Rohit

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
9,838 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. BhargavaGunnam-MSFT 28,061 Reputation points Microsoft Employee
    2024-05-13T20:39:07.67+00:00

    Hello Rohit Kulkarni,

    This seems to be an Network/DNS server issue.

    Open a Powershell command on your machine, and confirm that there is PE created (there is privatelink in the DNS resolution chain meaning there is PE created, like below) for this data store: image.png

    if there ia no managed PE created, then please create managed PE

    if there is a managed PE then please confirm managed PE is correct.

    for SQL: the zone name is<server>.privatelink.database.windows.net)

    Reference document:

    https://learn.microsoft.com/en-us/azure/azure-sql/database/private-endpoint-overview?view=azuresql

    for storage:
    User's image

    https://learn.microsoft.com/en-us/azure/storage/common/storage-private-endpoints#dns-changes-for-private-endpoints

    I hope this helps.

    0 comments
  2. Amira Bedhiafi 17,531 Reputation points
    2024-05-13T20:49:41.4733333+00:00

    Your issue must be related to :

    1. The server name cannot be resolved by the DNS.
    2. There might be an issue with the network setup, especially since you're using private endpoints.
    3. The server name specified might be incorrect.

    First, verify that the server name is correct and that the DNS can resolve the server name. You can try to resolve the server name from within the same virtual network where your private endpoint is set up. (You can use tools like nslookup or ping from a virtual machine in the same VNet.)

    Then check that the private endpoint is correctly configured and is in the same virtual network as your ADF :

    • The private endpoint is associated with the correct resource (your on-premises database).
    • The DNS configuration for the private endpoint is correctly set up.
    • Network Security Groups (NSGs) and firewalls are not blocking the traffic.

    If you're connecting to an on-premises database, ensure that you have a self-hosted integration runtime (SHIR) installed and configured correctly on a machine that has network connectivity to your on-premises database.

    
nslookup ServerName

    If nslookup fails, it indicates a DNS resolution issue.

    
telnet ServerName 1433

    Replace 1433 with the port number your database is listening on.

    More links: