- You have two or more connection servers, including disabled connection servers.
- Recompose operations may not occur or may be very slow.
- vCenter Server indicates that the service is not working properly even though vCenter services are up on the vCenter Server and connecting with either the vSphere Web Client or the vSphere Client works without issues.
- Connection server statuses display different information depending which server you are connected to.
- Connection servers display inconsistent data about virtual machine status.
- The Connection server Administrator dashboard shows a red error status for vCenter and/or Composer certificates. When viewing the certificates, they cannot be accepted.
The symptoms are seen when either ADLDS (ADAM database) synchronization fails or when corrupt information is inserted into the the VcCache.
This issue can occur for various reasons. Some known reasons are:
- The View Composer loses connection to its database (when on a remote server).
- The vCenter Server database is running on MS SQL Express and has reached its 10 GB limit.
- vCenter Server was upgraded and the connection servers have not been restarted.
Note: This can cause issues but does not always cause an error.
- Network interruption for prolonged periods of time between the View connection servers and vCenter Server.
- The boot order of servers is done incorrectly after a power outage.
- You have Horizon View Connection Servers replicating over a WAN.
Note: Horizon View 5.2 and later, see Unable to save pool settings or create new pools in VMware View (2082413).
Impact / Risks
- While the Connection Servers are down, users will not be able to create new connections to their desktops.
- If you have tunneling enabled, all active user sessions tunneled through the connection servers will be disconnected.
- Sessions made through Security Servers will not be impacted as long as the Security Servers remain powered on.
To resolve this issue, you must restart all the Connection servers in your environment, including any disabled Connection servers.
- Shut down all the Connection Servers in your environment. They must be powered down and not just rebooted. This includes disabled Connection servers.
- When all the Connection Servers are powered down, shut down the Composer Server.
- When all Connection Servers and Composer Server are shutdown, reboot the vCenter Server. After reboot, ensure that the vCenter services have started.
- After vCenter Server is started and all services are running, start the Composer server. Wait until the login screen appears on the Composer server before proceeding to the next step.
- Start the Connection servers. You can send all of the Connection Servers in the pod the Power On command at the same time.
- Log in to Horizon Console page and confirm that the issue is resolved. If the issue persists, file a support request with VMware Technical Support and note this Knowledge Base article ID (2068381) in the problem description. For more information on filing a Support Request, see Filing a Support Request in My VMware (2006985).
Note: All Connection Servers must be started before you can use the Horizon Console or Horizon Administrator page. The administrator page may not be available until all Connection Servers are started. This is an expected behavior.