Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
An error on the Horizon Admin console stating "Internal Error Occurred" when clicking on Settings -- Servers -- Connection Servers or the "Connect Server Restrictions" tabs of the administrative user interface. Horizon Connection Server debug logs show logging similar to the following: Collecting VMware Horizon View log bundles (1017939) for details. YYYY-MM-DDTHH:MM:SS.ms+HH:MM TRACE (XXXX-XXXX) <ajp-nio-127.0.0.1-8009-exec-1> [LDAPObjectStore] com.vmware.vdi.dal.ldap.LDAPObjectStore$b.loadNextPage 1 ms YYYY-MM-DDTHH:MM:SS.ms+HH:MM ERROR (XXXX-XXXX) <ajp-nio-127.0.0.1-8009-exec-1> [FaultUtilBase] InvalidArgument(parameter: connectionServers): A null value is invalid. YYYY-MM-DDTHH:MM:SS.ms+HH:MM DEBUG (XXXX-XXXX) <ajp-nio-127.0.0.1-8009-exec-1> [VlsiInvocation] Finish to call view API for /view-vlsi/rest/v1/connectionserver/list elapsed time:6 msecs YYYY-MM-DDTHH:MM:SS.ms+HH:MM ERROR (XXXX-XXXX) <ajp-nio-127.0.0.1-8009-exec-1> [RestApiServlet] Unexpected fault:(vdi.fault.InvalidArgument) { errorMessage = A null value is invalid., parameterName = connectionServers } for uri /view-vlsi/rest/v1/ConnectionServer/list YYYY-MM-DDTHH:MM:SS.ms+HH:MM DEBUG (XXXX-XXXX) <ajp-nio-127.0.0.1-8009-exec-1> [RestApiServlet] Exception for uri /view-vlsi/rest/v1/ConnectionServer/list com.vmware.vdi.logger.Logger.debug(Logger.java:44) com.vmware.vdi.vlsi.rest.exceptions.ViewServiceFaultException: (vdi.fault.InvalidArgument) { errorMessage = A null value is invalid., parameterName = connectionServers }
This article discusses the "Internal Error Occurred" banner message that appears when one of the connection servers' GSS API configuration is missing.
When pae-SendBrokerServicePrincipal is 1 GSS API Authenticator configuration must be present at pae-GSSAPIConfigDN on all connection servers. This Issue occurs when the attribute "pae-SendBrokerServicePrincipal" value at CN=<ConnectionServer>,OU=Server,OU=Properties,DC=vdi,DC=vmware,DC=int is set to 1 and the attribute value for "pae-GSSAPIConfigDN" in the same path is empty.
The Horizon Admin console dashboard will display connection servers as an error and will be unable to populate the servers list when you click on Settings — Servers — Connection Servers.
This issue has been resolved in Horizon Version 8.8/Horizon 8 2212 (ESB Release) and later
Procedure to re-populate the pae-GSSAPIConfigDN value to correct this issue on Horizon 8.6: Ensure Horizon ADLDS replication is healthy [ Reference: Forcing replication between ADAM databases ]Backup the ADLDS Database [ Reference: Performing an end-to-end backup and restore for VMware Horizon View ].Connect to ADLDS Database [ Reference: Connecting to the View ADAM Database ]Note the value of pae-GSSAPIConfigDN on all connection servers at CN=<ConnectionServer>,OU=Server,OU=Properties,DC=vdi,DC=vmware,DC=int.You can safely ignore servers with the pae-GSSAPIConfigDN value that matches the Authenticator CN objects(OU=Authenticator,OU=Properties,DC=vdi,DC=vmware,DC=int). Identify the server which has the pae-GSSAPIConfigDN empty or matching authenticators, then clear the pae-GSSAPIConfigDN value and set the value of pae-SendBrokerServicePrincipal to 0Ensure that any orphaned GSS API authenticator entries (class=pae-GSSAPIAuthenticator) are removed from the database located at OU=Authenticator, OU=Properties, DC=vdi, DC=vmware, and DC=int.Then login to Horizon Connection Server Administrator Console, Navigate to Settings – Servers – Connection Servers, click on EDIT on connection server for which you have changed the pae-SendBrokerServicePrincipal value to 0. Then apply the Authenticator settings again matching the other connection servers. This will update the SendBrokerServicePrincipal to 1 and pae-GSSAPIConfigDN will re-populate with the correct values.