VMware Horizon Community
jakobsk
Contributor
Contributor

Error accessing domain on Horizon connection server

Hello, I don't usually ask these questions in forums as the solution is usually already posted, but this problem has been tormenting me for days now.

First a little background: I'm trying to set up a Horizon connection server with instant clones in my vCenter environment. I have followed the "Evaluation Guide for VMware Horizon 8", and the setup went smooth until I'm trying to set up a Desktop pool with instant clone template. When I'm adding the pool, it all goes well until I get to the "Guest Customization" part, where it throws me an error: "There was an error accessing domain.", and I can't proceed.

This got me suspicious and in the connection server web UI I went to "Users and Groups > Remote Access > Add" menu and I tried doing a query for my Active Directory. It returns the same error, and it doesn't show me the directory tree either. I checked the connection server debug logs, and it looks like it's not even able to connect to the AD: 

2023-09-22T05:48:08.956-07:00 DEBUG (2E84-2AA4) <ajp-nio-127.0.0.1-8009-exec-9> [RestApiAuthFilter] Received request for /view-vlsi/rest/v1/queryservice/query
2023-09-22T05:48:08.956-07:00 DEBUG (2E84-2AA4) <ajp-nio-127.0.0.1-8009-exec-9> [RestApiAuthFilter] Authentication successful,do further process
2023-09-22T05:48:08.961-07:00 DEBUG (2E84-2AA4) <ajp-nio-127.0.0.1-8009-exec-9> [VlsiInvocation] Call view API for /view-vlsi/rest/v1/queryservice/query
2023-09-22T05:48:08.961-07:00 DEBUG (2E84-2AA4) <ajp-nio-127.0.0.1-8009-exec-9> [WinAuthAdAdapter] Returning cached domainList...
2023-09-22T05:48:08.961-07:00 DEBUG (2E84-2AA4) <ajp-nio-127.0.0.1-8009-exec-9> [HorizonAdServiceClient] Success:getDomains():[]
2023-09-22T05:48:08.961-07:00 DEBUG (2E84-2AA4) <ajp-nio-127.0.0.1-8009-exec-9> [WinAuthAdAdapter] Returning cached domainList...
2023-09-22T05:48:08.962-07:00 DEBUG (2E84-2AA4) <ajp-nio-127.0.0.1-8009-exec-9> [HorizonAdServiceClient] Success:getDomains():[]
2023-09-22T05:48:08.962-07:00 DEBUG (2E84-2AA4) <ajp-nio-127.0.0.1-8009-exec-9> [NextGenDqmAdImpl] FILTER: (&(|(&(objectCategory=user)(objectClass=user))(&(objectCategory=group)(objectClass=group)))(cn=*))
2023-09-22T05:48:08.962-07:00 DEBUG (2E84-2AA4) <ajp-nio-127.0.0.1-8009-exec-9> [WinAuthAdAdapter] Returning cached domainList...
2023-09-22T05:48:08.962-07:00 DEBUG (2E84-2AA4) <ajp-nio-127.0.0.1-8009-exec-9> [HorizonAdServiceClient] Success:getDomains():[]
2023-09-22T05:48:08.962-07:00 DEBUG (2E84-2AA4) <ajp-nio-127.0.0.1-8009-exec-9> [NextGenDqmAdImpl] AD query: filter = (&(|(&(objectCategory=user)(objectClass=user))(&(objectCategory=group)(objectClass=group)))(cn=*))
2023-09-22T05:48:08.962-07:00 DEBUG (2E84-2AA4) <ajp-nio-127.0.0.1-8009-exec-9> [NextGenDqmAdImpl] AD query: baseDn = GC://dc=vdi,dc=local
2023-09-22T05:48:08.962-07:00 DEBUG (2E84-2AA4) <ajp-nio-127.0.0.1-8009-exec-9> [NextGenDqmAdImpl] AD query: user = (UserContext domain=vdi.local, user=administrator)
2023-09-22T05:48:08.962-07:00 DEBUG (2E84-2AA4) <ajp-nio-127.0.0.1-8009-exec-9> [NextGenDqmAdImpl] AD query: userSIDs = [<SIDS>]
2023-09-22T05:48:08.962-07:00 DEBUG (2E84-2AA4) <ajp-nio-127.0.0.1-8009-exec-9> [NextGenDqmAdImpl] AD query: maxPrincipalsToReturn = 1000
2023-09-22T05:48:08.962-07:00 DEBUG (2E84-2AA4) <ajp-nio-127.0.0.1-8009-exec-9> [NextGenDqmAdImpl] AD query: adAdapter = com.vmware.vdi.adamwrapper.ad.WinAuthAdAdapter
2023-09-22T05:48:09.039-07:00 INFO  (22C4-2F00) <MessageFrameWorkDispatch> [ws_winauth] Could not execute query. Could not bind to GC://dc=vdi,dc=local
   AD Query error occurred, HRESULT: 8007054b
   Error Code: 0
   Error Text: 
   Provider: LDAP Provider
2023-09-22T05:48:09.042-07:00 INFO  (2E84-2AA4) <ajp-nio-127.0.0.1-8009-exec-9> [DomainAuthManager] Using credentials for domain VDI (vdi.local)
2023-09-22T05:48:09.042-07:00 ERROR (2E84-2AA4) <ajp-nio-127.0.0.1-8009-exec-9> [DomainAuthManager] Unable to retry operation. Secondary credential is missing for domain: VDI (vdi.local)
2023-09-22T05:48:09.042-07:00 ERROR (2E84-2AA4) <ajp-nio-127.0.0.1-8009-exec-9> [WinAuthAdAdapter] AD Query: error executing LDAP AD Query. Failed to list users: Could not execute query. Could not bind to GC://dc=vdi,dc=local
   AD Query error occurred, HRESULT: 8007054b
   Error Code: 0
   Error Text: 
   Provider: LDAP Provider
2023-09-22T05:48:09.042-07:00 ERROR (2E84-2AA4) <ajp-nio-127.0.0.1-8009-exec-9> [FaultUtilBase] UnexpectedFault: There was an error accessing domain 
2023-09-22T05:48:09.042-07:00 DEBUG (2E84-2AA4) <ajp-nio-127.0.0.1-8009-exec-9> [VlsiInvocation] Finish to call view API for /view-vlsi/rest/v1/queryservice/query elapsed time:81 msecs
2023-09-22T05:48:09.043-07:00 ERROR (2E84-2AA4) <ajp-nio-127.0.0.1-8009-exec-9> [RestApiServlet] Unexpected fault:(vdi.fault.UnexpectedFault) {
   errorMessage = There was an error accessing domain ,
   causeString = null,
   causeStackTrace = null,
   errorCode = UNABLE_TO_ACCESS_DOMAIN,
   errorAttributes = null
} for uri /view-vlsi/rest/v1/queryservice/query
2023-09-22T05:48:09.044-07:00 DEBUG (2E84-2AA4) <ajp-nio-127.0.0.1-8009-exec-9> [RestApiServlet] Exception for uri /view-vlsi/rest/v1/queryservice/query com.vmware.vdi.logger.Logger.debug(Logger.java:44)
com.vmware.vdi.vlsi.rest.exceptions.ViewServiceFaultException: (vdi.fault.UnexpectedFault) {
   errorMessage = There was an error accessing domain ,
   causeString = null,
   causeStackTrace = null,
   errorCode = UNABLE_TO_ACCESS_DOMAIN,
   errorAttributes = null
}

 

The weird thing is that using the vdmadmin -N -domains -list -active  command on the connection server correctly lists the AD it was set up on, and adding Instant Clone Engine Domain Accounts also works, which means that the connection server has some kind of good connection to the AD... 

I have tried reinstalling the connection server (which is on a different machine than the AD DC), but it's still the same issue. Any help is much appreciated!

Reply
0 Kudos
2 Replies
vBritinUSA
Hot Shot
Hot Shot

Hi @jakobsk  What's your MS Domain Functional Levels? Check the kb

Supported Operating Systems, Microsoft Active Directory Domain Functional Levels, and Events Databas...

 

Please mark helpful or correct if my answer resolved your issue.
Reply
0 Kudos
jakobsk
Contributor
Contributor

Functional level is Server 2016 and the Domain Controller is hosted on a Server 2022

jakobsk_0-1695711511846.png

 

 

Reply
0 Kudos