To resolve this issue, verify that the Health OU is missing from the ADAM database.
To verify that the Health OU is missing:
- Log into the vCenter Server as an Administrator.
- Click Start > Administrative Tools > ADSI Edit.
- Click Action, then clickConnect to.
- Under Connection Point, click Select or Type a Distinguished Name or Naming Context and type:
dc=virtualcenter, dc=vmware, dc=int
- Under Computer, select Select or type a domain or server and type:
localhost:389
- Click OK.
- Expand the Default Naming Context section.
- Expand
dc=virtualcenter, dc=vmware, dc=int
and verify if OU=Health
is missing from the ADAM database.
If the
OU=Health
is missing from the database, you must reinstall vCenter Server.
To reinstall vCenter Server:
- Stop the vCenter Server Service. For more information, see Stopping, starting, or restarting vCenter services (1003895).
- Back up the vCenter Server database. For more information, see Backing up the vCenter Server database running on Microsoft SQL or SQL Express server (2012138).
- Uninstall vCenter Server. For more information, see Best practices for uninstalling vCenter Server (1030559).
- Reinstall vCenter Server and select the existing 64-bit DSN and select the Do not overwrite, leave my existing database in place option.
- Start the vCenter Server Service. For more information, see Stopping, starting, or restarting vCenter services (1003895).
Notes:
- Hosts and virtual machines can remain powered on during this process, so there should be minimal to no impact to production.
- The existing database can remain attached to the existing SQL Server instance.
- The existing database preserves all inventory hierarchies, custom roles, and permissions propagation data.