You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Troubleshoot self-hosted integration runtime in Azure Data Factory
3
-
description: Learn how to troubleshoot Self-hosted integration runtime issues in Azure Data Factory.
3
+
description: Learn how to troubleshoot self-hosted integration runtime issues in Azure Data Factory.
4
4
services: data-factory
5
5
author: nabhishek
6
6
ms.service: data-factory
@@ -15,115 +15,120 @@ This article explores common troubleshooting methods for self-hosted integration
15
15
16
16
## Common errors and resolutions
17
17
18
-
### Error message: Self-hosted integration runtime is unable to connect to cloud service.
18
+
### Error message: Self-hosted integration runtime can't connect to cloud service
19
19
20
-
-**Symptom**:
20
+
21
21
22
-
22
+
#### Cause
23
23
24
-
-**Cause**: The self-hosted integration runtime isn't able to connect to data factory service (backend). Most often than not it's caused due to network settings in Firewall.
24
+
The self-hosted integration runtime can't connect to the Data Factory service (backend). This issue is typically caused by network settings in the firewall.
25
25
26
-
-**Resolution**:
26
+
#### Resolution
27
27
28
-
1. Check if the windows service "Integration Runtime Service" is running.
28
+
1. Check whether the integration runtime service is running.
29
29
30
-
30
+
31
31
32
-
2. If the windows service as shown in [1]is running, follow below instructions as appropriate:
32
+
1. If the service is running, go on to step 3.
33
33
34
-
1. If "proxy" is not configured on self-hosted integration runtime (default settings is no proxy configuration), run the below PowerShell command on the machine where self-hosted integration runtime is installed:
> The service URL may vary based on your data factory location. You can find the service URL under ADF UI -> Connections -> Integration runtimes -> Edit Self-hosted IR -> Nodes -> View Service URLs.
34
+
1. If there's no proxy configured on the self-hosted integration runtime (which is the default setting), run the following PowerShell command on the machine where the self-hosted integration runtime is installed:
> The service URL may vary, depending on your Data Factory location. You can find the service URL under **ADF UI** > **Connections** > **Integration runtimes** > **Edit Self-hosted IR** > **Nodes** > **View Service URLs**.
If the response is different, then follow the below instructions as appropriate:
47
+
1. If you don't receive the expected response, use one of the following methods as appropriate to your situation:
47
48
48
-
* If you get error "the remote name could not be resolved", there is an issue with DNS. Please get in touch with network team to get the DNS resolution issue fixed!
49
-
* If you get error "ssl/tls cert is not trusted", please check if the Certificate for "https://wu2.frontend.clouddatahub.net/" is trusted on the machine, install the public certificate using cert manager, which should mitigate this issue.
50
-
* Check Windows -> Event viewer (logs) -> Applications and Services Logs -> Integration Runtimefor any failure, mostly caused by DNS, firewall rule, and network settings of the company (Forcedly close the connection). For this issue, please engage your network team for further troubleshot, because every company has customized network settings.
49
+
* If you receive a "Remote name could not be resolved" message, there's a Domain Name System (DNS) issue. Contact your network team to fix this issue.
50
+
* If you receive an "ssl/tls cert is not trusted" message, check whether the certificate for https://wu2.frontend.clouddatahub.net/ is trusted on the machine, and then install the public certificate by using Certificate Manager. This action should mitigate the issue.
51
+
* Go to **Windows** > **Event viewer (logs)** > **Applications and Services Logs** > **Integration Runtime** and check for any failure that's caused by DNS, a firewall rule, or company network settings. (If you find such a failure, forcibly close the connection.) Because every company has customized network settings, contact your network team to troubleshoot these issues.
51
52
52
-
2. If "proxy" has been configured on the self-hosted integration runtime, verify whether your proxy server is able to access our service endpoint. For a sample command, refer [this](https://stackoverflow.com/questions/571429/powershell-web-requests-and-proxies).
53
+
1. If "proxy" has been configured on the self-hosted integration runtime, verify that your proxy server can access the service endpoint. For a sample command, see [PowerShell, web requests, and proxies](https://stackoverflow.com/questions/571429/powershell-web-requests-and-proxies).
> * Check if the proxy server requires whitelisting. If so, have [these domains](https://docs.microsoft.com/azure/data-factory/data-movement-security-considerations#firewall-requirements-for-on-premisesprivate-network) whitelisted.
78
-
> * Check TLS/SSL cert for "wu2.frontend.clouddatahub.net/" is trusted on proxy server.
79
-
> * If you are using active directory authentication in proxy, then change the service account to the user account that can access the proxy as "Integration Runtime Service".
76
+
> [!NOTE]
77
+
> Proxy considerations:
78
+
> * Check whether the proxy server needs to be put on the Safe Recipients list. If so, make sure [these domains](https://docs.microsoft.com/azure/data-factory/data-movement-security-considerations#firewall-requirements-for-on-premisesprivate-network) are on the Safe Recipients list.
79
+
> * Check whether the TLS/SSL certificate "wu2.frontend.clouddatahub.net/" is trusted on the proxy server.
80
+
> * If you're using Active Directory authentication on the proxy, change the service account to the user account that can access the proxy as "Integration Runtime Service."
80
81
81
82
### Error message: Self-hosted integration runtime node/ logical SHIR is in Inactive/ "Running (Limited)" state
82
83
83
-
- **Cause**: You may see Self-hosted IR node in Inactive status as shown in the screenshot below:
84
+
#### Cause
84
85
85
-
86
+
The self-hosted integrated runtime node might have an **Inactive** status, as shown in the following screenshot:
86
87
87
-
It happens so when nodes are not able to communicate with each other.
88
+
88
89
89
-
- **Resolution**:
90
+
This behavior occurs when nodes can't communicate with each other.
90
91
91
-
Log into the node hosted VM, and open Event View, under the Applications and Services Logs -> Integration Runtime, filter all the error logs.
92
+
#### Resolution
92
93
93
-
1. If the error log contains:
94
-
95
-
**Error log**: System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://xxxxxxx.bwld.com:8060/ExternalService.svc/WorkerManager. The connection attempt lasted for a time span of 00:00:00.9940994. TCP error code 10061: No connection could be made because the target machine actively refused it 10.2.4.10:8060. --->
96
-
System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.2.4.10:8060
97
-
98
-
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
99
-
100
-
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
101
-
102
-
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
94
+
1. Log in to the node-hosted VM. Under **Applications and Services Logs** > **Integration Runtime**, open Event Viewer, and filter all the error logs.
95
+
96
+
1. Check whether an error log contains the following error:
103
97
104
-
**Solution:** launch the command line: telnet 10.2.4.10 8060
98
+
```System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://xxxxxxx.bwld.com:8060/ExternalService.svc/WorkerManager. The connection attempt lasted for a time span of 00:00:00.9940994. TCP error code 10061: No connection could be made because the target machine actively refused it 10.2.4.10:8060.
99
+
System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it.
100
+
10.2.4.10:8060
105
101
106
-
If you get below error, please contact your IT guys for help with fixing this issue. After you could successfully telnet, contact Microsoft support if you still have issues for the IR node status.
102
+
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
103
+
104
+
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
105
+
106
+
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
107
+
108
+
1. If you see this error, run the following on a command line:
109
+
110
+
**telnet 10.2.4.10 8060**.
111
+
1. If you receive the following error, contact your IT department for help with fixing this issue. After you can successfully telnet, contact Microsoft Support if you still have issues with the integrative runtime node status.
**Error log:** Cannot connect to worker manager: net.tcp://xxxxxx:8060/ExternalService.svc/ No DNS entries exist for host azranlcir01r1. No such host is known Exception detail: System.ServiceModel.EndpointNotFoundException: No DNS entries exist for host xxxxx. ---> System.Net.Sockets.SocketException: No such host is known at System.Net.Dns.GetAddrInfo(String name) at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6) at System.Net.Dns.GetHostEntry(String hostNameOrAddress) at System.ServiceModel.Channels.DnsCache.Resolve(Uri uri) --- End of inner exception stack trace --- Server stack trace: at System.ServiceModel.Channels.DnsCache.Resolve(Uri uri)
115
+
1. Check whether the error log contains the following:
116
+
117
+
```Error log: Cannot connect to worker manager: net.tcp://xxxxxx:8060/ExternalService.svc/ No DNS entries exist for host azranlcir01r1. No such host is known Exception detail: System.ServiceModel.EndpointNotFoundException: No DNS entries exist for host xxxxx. ---> System.Net.Sockets.SocketException: No such host is known at System.Net.Dns.GetAddrInfo(String name) at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6) at System.Net.Dns.GetHostEntry(String hostNameOrAddress) at System.ServiceModel.Channels.DnsCache.Resolve(Uri uri) --- End of inner exception stack trace --- Server stack trace: at System.ServiceModel.Channels.DnsCache.Resolve(Uri uri)```
113
118
114
-
**Solution:** One of the below two actions can help resolve the issue:
115
-
1. Put all the nodes in the same domain.
116
-
2. Add IP to host mapping in all the hosted VM's hosts file.
119
+
1. To resolve the issue, try one or both of the following methods:
120
+
- Put all the nodes in the same domain.
121
+
- Add the IP to host mapping in all the hosted VM's host files.
117
122
118
123
119
124
## Next steps
120
125
121
-
For more troubleshooting help, try these resources:
126
+
For more help with troubleshooting, try the following resources:
0 commit comments