Skip to content

Commit ec18e94

Browse files
authored
Update troubleshoot-shir-include.md
1 parent c6f4a44 commit ec18e94

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/data-factory/includes/troubleshoot-shir-include.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -388,7 +388,7 @@ For failed activities that are running on a self-hosted IR or a shared IR, the s
388388
389389
3. Locate the bin\server folder in the following path:
390390
391-
`C:\Program Files\Java\jre1.8.0_74`
391+
`C:\Program Files\Java\jre1.xx.xxx`
392392
393393
:::image type="content" source="../media/self-hosted-integration-runtime-troubleshoot-guide/folder-of-jre.png" alt-text="Screenshot showing the JRE folder.":::
394394
@@ -397,7 +397,7 @@ For failed activities that are running on a self-hosted IR or a shared IR, the s
397397
:::image type="content" source="../media/self-hosted-integration-runtime-troubleshoot-guide/file-location-image.png" alt-text="Screenshot showing a jvm.dll file location.":::
398398
399399
> [!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.
401401
> - 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.
402402
403403
## Self-hosted IR setup
@@ -655,7 +655,7 @@ For Azure Data Factory v1 customers:
655655
656656
> [!NOTE]
657657
> 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.
659659
> * Check to see whether SSL/TLS certificate "wu2.frontend.clouddatahub.net/" is trusted on the proxy server.
660660
> * 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."
661661
@@ -823,11 +823,11 @@ This notification applies to the following scenarios:
823823
824824
How to determine whether you're affected:
825825
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).
827827
828828
- You *are* affected if you're explicitly enabling the allowlist for outbound IPs on your corporate firewall.
829829
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).
831831
832832
##### Scenario 2: Outbound communication from a self-hosted integration runtime that's running on an Azure VM inside a customer-managed Azure virtual network
833833
@@ -841,7 +841,7 @@ How to determine whether you're affected:
841841
842842
- You *are* affected if you're explicitly enabling the allowlist for outbound IP addresses on your NSG rules setting on the Azure virtual network.
843843
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).
845845
846846
##### Scenario 3: Outbound communication from SSIS Integration Runtime in a customer-managed Azure virtual network
847847
@@ -853,7 +853,7 @@ How to determine whether you're affected:
853853
854854
- You *are* affected if you're explicitly enabling the allowlist for outbound IP addresses on your NSG rules setting on the Azure virtual network.
855855
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).
857857
858858
### Couldn't establish a trust relationship for the SSL/TLS secure channel
859859

0 commit comments

Comments
 (0)