VIP Validation Server will not start on Server 2012r2

Products

• VIP Enterprise Gateway

Issue/Introduction

The Enterprise Gateway Validation server will not start. However, user store test binding works. The Domain Certificate is loaded in the Gateway but the Validation server still will not start.

Windows Event Log errors:

Events 36884 and 36888 on the Application server

Radius Validation Server:

Server was not started

 

Cause

This problem occurs because of an error in Windows 7 and in Windows Server 2008 R2. The LDAP client stores the node's canonical name in the alias field. This problem occurs if the node alias and the node name are different.

Registry missing value:

• Locate the following subkey in the registry:
• HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LDAP
• Registry value  REG_DWORD UseHostnameAsAlias is missing or set to 0.

 

Resolution

This issue requires a registry change..

Important: This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

How to back up and restore the registry in Windows: https://support.microsoft.com/en-us/kb/322756

 

1. Start Registry Editor.
2. Locate the following subkey in the registry. HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LDAP
3. Create a new REG_DWORD value that is named UseHostnameAsAlias, and set the value to anything other than zero.
4. Exit Registry Editor, and then restart the computer.

Note: You must restart the computer after you apply this hotfix.

Referenced from, https://support.microsoft.com/en-us/kb/2275950

If the issue still is occurring use the attached LDP.exe to bind to the SSL port used for LDAP normally port 636. Note the error that occurs.