mbcommsTech
asked on
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::LoadHostHeal thFromDb 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="HealthSystemRunt ime"><syst emHealthIn fo><numeri cSensorInf o><name>Sy stem Level for System Board 1</name><healthState><labe l>Green</l abel><summ ary>Green< /summary>< key>Green< /key></hea lthState>< currentRea ding>24800 </currentR eading><un itModifier >-2</unitM odifier><b aseUnits>W atts</base Units><sen sorType>po wer</senso rType></nu mericSenso rInfo><num ericSensor Info><name >Voltage 2 for Power Supply 2</name><healthState><labe l>Green</l abel><summ ary>Green< /summary>< key>Green< /key></hea lthState>< currentRea ding>23400 </currentR eading><un itModifier >-2</unitM odifier><b aseUnits>V olts</base Units><sen sorType>vo ltage</sen sorType></ numericSen sorInfo><n umericSens orInfo><na me>Voltage 1 for Power Supply 1</name><healthState><labe l>Green</l abel><summ ary>Green< /summary>< key>Green< /key></hea lthState>
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.
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::LoadHostHeal
followed by a mass of XML which presumably is the bad SOAP packet, looking like this: <obj xmlns="urn:vim25" xsi:type="HealthSystemRunt
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.
Have you recently updated your ESX boxes with update 2? If so, you should also update your VC also.
ASKER
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.
Dell servers with ESXi in them, vCenter running on a Win2003 box with a full SQL server on the same machine.
Can you try rerunning the update 2 install? on your VC?
Take a look here http://communities.vmware.com/thread/120876
Take a look here http://communities.vmware.com/thread/120876
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.