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
Copy file name to clipboardExpand all lines: articles/data-factory/includes/troubleshoot-shir-include.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -388,7 +388,7 @@ For failed activities that are running on a self-hosted IR or a shared IR, the s
388
388
389
389
3. Locate the bin\server folder in the following path:
390
390
391
-
`C:\Program Files\Java\jre1.8.0_74`
391
+
`C:\Program Files\Java\jre1.xx.xxx`
392
392
393
393
:::image type="content" source="../media/self-hosted-integration-runtime-troubleshoot-guide/folder-of-jre.png" alt-text="Screenshot showing the JRE folder.":::
394
394
@@ -397,7 +397,7 @@ For failed activities that are running on a self-hosted IR or a shared IR, the s
397
397
:::image type="content" source="../media/self-hosted-integration-runtime-troubleshoot-guide/file-location-image.png" alt-text="Screenshot showing a jvm.dll file location.":::
398
398
399
399
> [!NOTE]
400
-
> - If any of these configurations are not as described in these steps, use the [JRE windows installer](https://java.co../download/manual.jsp) to fix the problems.
400
+
> - If any of these configurations are not as described in these steps, use the [JRE windows installer](https://www.java.com/download/) to fix the problems.
401
401
> - If all the configurations in these steps are correct as described, there may be a VC++ runtime library missing in the system. You can fix this problem by installing the VC++ 2010 Redistributable Package.
402
402
403
403
## Self-hosted IR setup
@@ -655,7 +655,7 @@ For Azure Data Factory v1 customers:
655
655
656
656
> [!NOTE]
657
657
> Proxy considerations:
658
-
> * Check to see whether the proxy server needs to be put on the Safe Recipients list. If so, make sure [these domains](./data-movement-security-considerations.md#firewall-requirements-for-on-premisesprivate-network) are on the Safe Recipients list.
658
+
> * Check to see whether the proxy server needs to be put on the Safe Recipients list. If so, make sure [these domains](../data-movement-security-considerations.md#firewall-requirements-for-on-premisesprivate-network) are on the Safe Recipients list.
659
659
> * Check to see whether SSL/TLS certificate "wu2.frontend.clouddatahub.net/" is trusted on the proxy server.
660
660
> * 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."
661
661
@@ -823,11 +823,11 @@ This notification applies to the following scenarios:
823
823
824
824
How to determine whether you're affected:
825
825
826
-
- You *are not* affected if you're defining firewall rules based on fully qualified domain names (FQDNs) that use the approach described in [Set up a firewall configuration and allowlist for IP addresses](data-movement-security-considerations.md#firewall-configurations-and-allow-list-setting-up-for-ip-addresses).
826
+
- You *are not* affected if you're defining firewall rules based on fully qualified domain names (FQDNs) that use the approach described in [Set up a firewall configuration and allowlist for IP addresses](../data-movement-security-considerations.md#firewall-configurations-and-allow-list-setting-up-for-ip-addresses).
827
827
828
828
- You *are* affected if you're explicitly enabling the allowlist for outbound IPs on your corporate firewall.
829
829
830
-
If you're affected, take the following action: by November 8, 2020, notify your network infrastructure team to update your network configuration to use the latest data factory IP addresses. To download the latest IP addresses, go to [Discover service tags by using downloadable JSON files](../virtual-network/service-tags-overview.md#discover-service-tags-by-using-downloadable-json-files).
830
+
If you're affected, take the following action: by November 8, 2020, notify your network infrastructure team to update your network configuration to use the latest data factory IP addresses. To download the latest IP addresses, go to [Discover service tags by using downloadable JSON files](../../virtual-network/service-tags-overview.md#discover-service-tags-by-using-downloadable-json-files).
831
831
832
832
##### Scenario 2: Outbound communication from a self-hosted integration runtime that's running on an Azure VM inside a customer-managed Azure virtual network
833
833
@@ -841,7 +841,7 @@ How to determine whether you're affected:
841
841
842
842
- You *are* affected if you're explicitly enabling the allowlist for outbound IP addresses on your NSG rules setting on the Azure virtual network.
843
843
844
-
If you're affected, take the following action: by November 8, 2020, notify your network infrastructure team to update the NSG rules on your Azure virtual network configuration to use the latest data factory IP addresses. To download the latest IP addresses, go to [Discover service tags by using downloadable JSON files](../virtual-network/service-tags-overview.md#discover-service-tags-by-using-downloadable-json-files).
844
+
If you're affected, take the following action: by November 8, 2020, notify your network infrastructure team to update the NSG rules on your Azure virtual network configuration to use the latest data factory IP addresses. To download the latest IP addresses, go to [Discover service tags by using downloadable JSON files](../../virtual-network/service-tags-overview.md#discover-service-tags-by-using-downloadable-json-files).
845
845
846
846
##### Scenario 3: Outbound communication from SSIS Integration Runtime in a customer-managed Azure virtual network
847
847
@@ -853,7 +853,7 @@ How to determine whether you're affected:
853
853
854
854
- You *are* affected if you're explicitly enabling the allowlist for outbound IP addresses on your NSG rules setting on the Azure virtual network.
855
855
856
-
If you're affected, take the following action: by November 8, 2020, notify your network infrastructure team to update the NSG rules on your Azure virtual network configuration to use the latest data factory IP addresses. To download the latest IP addresses, go to [Discover service tags by using downloadable JSON files](../virtual-network/service-tags-overview.md#discover-service-tags-by-using-downloadable-json-files).
856
+
If you're affected, take the following action: by November 8, 2020, notify your network infrastructure team to update the NSG rules on your Azure virtual network configuration to use the latest data factory IP addresses. To download the latest IP addresses, go to [Discover service tags by using downloadable JSON files](../../virtual-network/service-tags-overview.md#discover-service-tags-by-using-downloadable-json-files).
857
857
858
858
### Couldn't establish a trust relationship for the SSL/TLS secure channel
0 commit comments