VMware vCenter Server Heartbeat - After Making a Change or Restarting Single Sign On Server System, vCenter Server 5.1.x Fails to Start



This Knowledge Base article provides information about vCenter Server 5.1.x Single Sign On Server system preventing vCenter Server from starting.

More Information


After restarting the Single Sign On (SSO) server system, vCenter Server 5.1.x fails to start and you are unable to log in to the vSphere Web Client.


Restarting the machine where SSO is installed may result in changes to the system. For example, when updates are applied to the operating system, the machine name changes, or the machine is added or removed from an Active Directory domain. These changes prevent the SSO server from starting and, as a result, vCenter Server does not start. In addition, if you clone or change the parameters of a virtual machine where SSO is installed (such as the amount of RAM), the number of CPUs, the MAC address, and SSO fails to start.


To resolve this issue:

  1. Click Start , right-click Command Prompt , and select Run as administrator to open a command prompt as an administrator.
  2. On the Primary/active server, locate and navigate to the SSO server installation directory. By default, this directory is located at C:\Program Files\VMware\Infrastructure\SSOServer\Utils .
  3. Run the following command:

    Note: This command replaces the masterPassword with the SSO Password  ( admin@system-domain )

    rsautil manage-secrets -a recover -m <masterPassword>
  4. Restart the VMware SSO service.
  5. Restart the VMware VirtualCenter Server service.

Applies To

VMware vCenter Server Heartbeat 6.5 and later

Additional Information



0 out of 0 found this helpful



Please sign in to leave a comment.