Issue:
While attempt to reboot the VirtualCenter server or restart the VirtualCenter Service you may receive an error message similar to the following.
VMWare VirtualCenter Server failed with a service-specific error code 2
Cause:
One possible cause is that there is an entry in the SQL database which has malformed XML data which causes VirtualCenter to crash during start up. The problem is not seen until the VirtualCenter Service is stopped and restarted, or the server is rebooted.
This issue may be caused by:
· Upgrading your ESX 3.5 hosts to Update 2 without first updating to VirtualCenter 2.5 Update 3.
· UTF-8 characters in the VirtualCenter database as a result of naming virtual machines and datastores
· Or the User ID and password for the DSN to connect to the SQL Database has been changed.
Solution:
Use Add/Remove Programs to repair the corrupted installation or database, or to update the DSN user information.
1) Click the Change Button on the VMware VirtualCenter Server item in Add/Remove programs
2) Welcome Screen
a. Click Next
3) Program Maintenance Screen
a. Select Repair
b. Click Next
4) VirtualCenter Database
a. Select use an existing database server
b. Click Next
5) Database Information
a. Verify the ODBC Connection information is correct
b. Type the same username and password as used in the ODBC DNS Setup.
c. Click Next
6) Reinitialize the Database?
a. Click NO
7) SQL Agent Verification
a. Click OK
8) Click Next on all the remaining screens
a. Note: The next screens should present your existing configuration information as the default selection. Unless absolutely positive that a change is needed you should accept the current settings provided.
9) Click Install on the final Screen.
10) Wait while the repair is performed.
11) Click Finish
12) Check that the VirtualCenter Service is started
13) Log into VirtualCenter
More Information:
VirtualCenter server fails with the error: A general system error occurred: at line number 7, not well-formed (invalid token)
A repair will not correct SQL Agent Jobs. To correct those you should use the following KB Article from VMWare. After VirtualCenter 2.5 upgrade: Performance data is currently not available for this entity