Symptoms
VirtualCenter Server service fails to start after moving the vCenter Server database to another host and updating vCenter Server to reflect the database change.The vpxd.log contains entries similar to: Vdb::Connection::TestConnection SQLExecute failed: 42000:229
Resolution
This issue may occur if the account used to connect to the database does not have the the db_owner role within the vCenter Server database.
To resolve this issue, you must give the db_owner rights to the account that is being used to connect the database:
Connect to the SQL server.Launch Microsoft SQL Server Management Studio app and click Connect.Expand Databases > VC Database > Security > Roles > Database Roles. Right click on db_owner.Click Add under Role Members.Enter the user account being used to connect to the database that has db_owner rights.Click OK.Restart the vCenter Server service. For more information, see Stopping, starting, or restarting vCenter services (1003895). Note: When restarting the VMware VirtualCenter Server service, you may see that the service is already in the starting mode. If you experience this issue, open Task Manager, stop the vpxd process, and then start the VMware VirtualCenter Server service.
Related Information
How to stop, start, or restart vCenter Server services
