Symptoms
In a Connection Server's debug logs, log lines similar to this are seen:The debug log is located in the folder C\:ProgramData\VMware\VDM\logs folder.Please refer to Location of Horizon (VDM) log files (1027744) for more details.Example 1:
[AdamEntityManager] Search ADAM object failed: com.vmware.vdi.logger.Logger.debug(Logger.java:44)
javax.naming.CommunicationException: vdiglobal.vmware.int:389 [Root exception is java.net.UnknownHostException: vdiglobal.vmware.int]
at java.naming/com.sun.jndi.ldap.LdapReferralContext.<init>(Unknown Source)
at java.naming/javax.naming.directory.InitialDirContext.search(Unknown Source)
at com.vmware.vdi.adamwrapper.ldap.a.search(SourceFile:464)
at java.naming/javax.naming.spi.NamingManager.processURLAddrs(Unknown Source)
at java.naming/javax.naming.spi.NamingManager.getObjectInstance(Unknown Source
Example 2:
Authentication failed, Unexpected fault: com.vmware.vdi.adamwrapper.exceptions.ADAMServerException: vdiglobal.vmware.int:389
Cause
When CPA is enabled, if it does not complete properly. It leads to login failures until the CPA status is set as disabled manually in ADAM database. This can happen , for example, in a scenario where CPA was being tested and removed partially.
Impact / Risks
Note that these steps are not valid for environments where CPA is expected to be enabled. These steps disable CPA. In a CPA environment where login is failing, such as after an upgrade, use the steps in article https://kb.vmware.com/s/article/2080253 to recover the CPA instance.
Resolution
Resolution/Workaround:1. Ensure that Global database instance is not existing for the connection server using Control Panel or Services.msc2. Back up your Adam Database & connect to dc=vdi,dc=vmware,dc=int:389 via Adsiedit. Please see this KB for a step by step : Connecting to the View ADAM Database (2012377)3. Traverse to the location CN=Common,OU=Global,OU=LMV,OU=Properties,DC=vdi,DC=vmware,DC=int4. Change the pae-LinkedModeEnabled value from 1 to 0.After performing the above changes, login to Horizon and it as to work as usual.Note, this is applicable to Horizon 8.3 with improved logic factored into later editions of Horizon.
