"The URL cannot be resolved" error in DirectAccess and routing failure on HNV gateway cluster in Windows Server 2012 R2

Gilt für: Windows Server 2012 R2 DatacenterWindows Server 2012 R2 EssentialsWindows Server 2012 R2 Foundation

Symptoms


Issue 1

When you set up a DirectAccess (DA) server on a Windows Server 2012 R2-based computer, you cannot complete the third Setup step when you try to provide the URL of the network location server. Instead, you receive the following error message:

The URL cannot be resolved to a valid IP address.

Issue 2

When the Remote Access configurations (routing domains) become unsynchronized between the active and passive nodes on an Windows Server 2012 R2 Hyper-V Network Virtualization (HNV) cluster gateway, in a failover scenario, the passive node becomes active, and the existing "Enabled but not available" routing domains on the passive node try to synchronize with the active node but fails that cause a memory leak issue. Memory consumes by RHS.exe and WMIPRVSE.exe increases every 30 seconds, eventually, it leads to a routing failure.

Cause


Cause for issue 1

This problem occurs because the host name does not resolve even though there is a valid CNAME record in DNS that can be successfully resolved from the DA edge server.

Cause for issue 2

This issue occurs because the routing compartments on the passive gateway node become unsynchronized with the routing compartments on the active gateway node.

Resolution


To resolve both issues, install the hotfix that is described in this article.

Hotfix information

A supported hotfix is available from Microsoft Support. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this update in Windows Server 2012 R2, you must first have update 2919355 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

Workaround


To work around the memory leak issue, disable the routing domains that are listed as "Enabled but not available" on both gateway nodes by using the Disable-RemoteAccessRoutingDomain -RoutingDomainName -Type All -Force command.

Note You may have to restart the RemoteAccess service to fully remove the routing domains. As soon as the configurations are synchronous, the memory leak issue should be corrected.

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References


Learn about the terminology that Microsoft uses to describe software updates.