To fix the database and work around this issue, remove the host from Lab Manager and vCenter and then add it back.
Perform these steps for each ESX host, one at a time:
- In Lab Manager Global Organization, click Resources, then click the Hosts tab.
- If host spanning is enabled on the host, go to the host properties and disable it.
- From the Resources/Hosts page, disable the host.
- Either un-deploy all virtual machines on the host or put the host into maintenance mode so that all of the virtual machines vMotion to another host.
- When all of the virtual machines are off of the host, un-prepare the host in Lab Manager.
- Edit the cluster settings in VMware Infrastructure (VI) Client, and in the VMware DRS change the automation level to Manual.
- Disconnect the host from the cluster.
- When the host is disconnected from the cluster, remove the host from the cluster.
- Re-add the host to the cluster and take it out of maintenance mode.
- In Lab Manager, prepare the host on the Resources/Hosts page.
- After completing this process for all ESX hosts in the cluster, set the DRS settings back to automated (if it was previously set to automated).
Note: You cannot migrate a virtual machine from an ESX 4.0 host to an ESX 3.5 host. For information about configuring Lab Manager in a mixed ESX 3.5 and 4.0 environment, see the Lab Manager Installation and Upgrade Guide and Lab Manager User's Guide.