VirtualCenter fails to start with SOAP error in log

It was a regular reboot but now Virtual Center will not start and looking in the logs we see this error:

2009-02-18 17:05:05.359 'App' 4260 warning VpxUtil Failed to parse XML in deserializing soap to object at 1: not well-formed (invalid token)
2009-02-18 17:05:05.359 'App' 4260 warning VpxdInvtHost::LoadHostHealthFromDb Failed todeserialize system health data from Db:

followed by a mass of XML which presumably is the bad SOAP packet, looking like this: <obj xmlns="urn:vim25" xsi:type="HealthSystemRuntime"><systemHealthInfo><numericSensorInfo><name>System Level for System Board 1</name><healthState><label>Green</label><summary>Green</summary><key>Green</key></healthState><currentReading>24800</currentReading><unitModifier>-2</unitModifier><baseUnits>Watts</baseUnits><sensorType>power</sensorType></numericSensorInfo><numericSensorInfo><name>Voltage 2 for Power Supply 2</name><healthState><label>Green</label><summary>Green</summary><key>Green</key></healthState><currentReading>23400</currentReading><unitModifier>-2</unitModifier><baseUnits>Volts</baseUnits><sensorType>voltage</sensorType></numericSensorInfo><numericSensorInfo><name>Voltage 1 for Power Supply 1</name><healthState><label>Green</label><summary>Green</summary><key>Green</key></healthState>

and on and on, there is heaps of it.....

further up the log stack are these lines:

2009-02-18 17:05:03.984 'Libs' 4260 warning VpxdOsLayer Couldn't read registry entry vmdbPort
2009-02-18 17:05:03.984 'Libs' 4260 warning VpxdOsLayer Couldn't read registry entry managedIP

are they relevant? The database is running and can be connected to by ODBC and trying a manual start of the virtualCenter server is no different to that of a boot-up.
mbcommsTechAsked:
Who is Participating?
 
mbcommsTechConnect With a Mentor Author Commented:
This was a first off installation, not an update. We reinstalled, on another database server, and have our fingers crossed.
0
 
nappy_dThere are a 1000 ways to skin the technology cat.Commented:
Have you recently updated your ESX boxes with update 2?  If so, you should also update your VC also.
0
 
mbcommsTechAuthor Commented:
Its a new install, update 2 was in everything as installed. This is the first reboot after that installation.

Dell servers with ESXi in them, vCenter running on a Win2003 box with a full SQL server on the same machine.
0
 
nappy_dThere are a 1000 ways to skin the technology cat.Commented:
Can you try rerunning the update 2 install?  on your VC?

Take a look here http://communities.vmware.com/thread/120876
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.