Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Restart order of the View environment to clear ADLDS (ADAM) synchronization in View 4.5, 4.6, 5.0, and 5.1 (2068381)

Symptoms

  • 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.

Cause

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 5.1 or earlier connection servers replicating over a WAN.
Note: Horizon View 5.2 and later, see Pool settings are not saved, new pools cannot be created, and vCenter Server tasks are not processed in a Horizon View environment (2082413).

Resolution

To resolve this issue, you must restart all the Connection servers in your environment, including any disabled Connection servers.

Note: It is not necessary to restart Security servers and Agent virtual machines.

Reboot order

If Composer is installed on the vCenter Server:
  1. Shut down all the Connection servers in your environment. They must be powered down and not just rebooted. This includes disabled Connection servers.
  2. When all the Connection servers are powered down, reboot the vCenter Server. After reboot, ensure that the vCenter services and composer services are back online.
  3. After the vCenter Server is back online, start the Connection servers one at a time. Power on the first server, then wait until the login screen appears before powering on the next server. The order in which you power on the Connection servers does not matter.
  4. Log in to View Administrator 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).

If Composer is installed on a standalone server:
  1. Shut down all the Connection servers in your environment. They must be powered down and not just rebooted. This includes disabled Connection servers.
  2. When all the Connection servers are powered down, shut down the Composer server.
  3. When all Connection servers and Composer server are shutdown, reboot the vCenter Server. After reboot, ensure that the vCenter services have started.
  4. 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.
  5. Start the Connection servers one at a time. Power on the first server, then wait until the login screen appears before powering on the next server. The order in which you power on the Connection servers does not matter.
  6. Log in to View Administrator 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 View Administrator page. The administrator page may not appear to function until all Connection servers are started. This is an expected behavior.

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.

Additional Information

To be alerted when this article is updated, click Subscribe to Document in the Actions box.

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 2 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 2 Ratings
Actions
KB: