?
Solved

VirtualCenter fails to start with SOAP error in log

Posted on 2009-02-19
4
Medium Priority
?
1,456 Views
Last Modified: 2012-06-27
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.
0
Comment
Question by:mbcommsTech
  • 2
  • 2
4 Comments
 
LVL 32

Expert Comment

by:nappy_d
ID: 23687553
Have you recently updated your ESX boxes with update 2?  If so, you should also update your VC also.
0
 

Author Comment

by:mbcommsTech
ID: 23687730
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
 
LVL 32

Expert Comment

by:nappy_d
ID: 23688232
Can you try rerunning the update 2 install?  on your VC?

Take a look here http://communities.vmware.com/thread/120876
0
 

Accepted Solution

by:
mbcommsTech earned 0 total points
ID: 24733489
This was a first off installation, not an update. We reinstalled, on another database server, and have our fingers crossed.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article, I will show you HOW TO: Create your first Windows Virtual Machine on a VMware vSphere Hypervisor 6.5 (ESXi 6.5) Host Server, the Windows OS we will install is Windows Server 2016.
In this article, I show you step by step with screenshots to assist you - HOW TO: Deploy and Install the VMware vCenter Server Appliance 6.5 (VCSA 6.5), with some helpful tips along the way.
Teach the user how to edit .vmx files to add advanced configuration options Open vSphere Web Client: Edit Settings for a VM: Choose VM Options -> Advanced: Add Configuration Parameters:
This Micro Tutorial walks you through using a remote console to access a server and install ESXi 5.1. This example is showing remote access and installation using a Dell server. The hypervisor is the very first component of your virtual infrastructu…
Suggested Courses

750 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question