Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

46601

May 15th, 2014 09:00

inventory fails on all host Reason The markup in the document following the root element must be well formed

Running ver 2.1 of openmanage for vcenter and applied firmware updates to the 7 servers in a VMware stack . Now inventory fails on all servers Failed to get OMSA inventory. I run the fix non-compliant servers wizard and the log shows completed, the server reboots, logs show starting inventory, inventory failed and failed to get iDRAC ip address when starting up. If I try to run on demand I get eh markup must be well formed message.

What did I do and how do I fix it ?

2 Posts

June 23rd, 2014 01:00

Hi


the Dell Support told me last Tuesdays that there is a new VMware patch (ESXi 5.1) KB 2077641 and one patch for the OMI appliance 2.1.23 to 2.1.0.27.

I installed the patches on Friday and now it seem all is running fine.

2 Posts

June 23rd, 2014 08:00

When you open the OMI administrtion website in your browser click on appliance management. There you can find a task like "update virtual machine".

I hope the translations are right I use the OMI with german text.

4 Posts

May 16th, 2014 01:00

Hi,

Thank you for your post.

Can you please give us few more details like

1.What generation of servers are added to your VCenter?Is it 11g or 12g?

2.Which component did you try to update?Is it Lifecycle Controller or IDRAC update?

3.Which version of ESXi is running on your servers?

4.When you said compliance fix,was it OMSA compliance?

thanks,

Midhun

5 Posts

May 16th, 2014 05:00

1.They are all PowerEdge R810's, not sure what generation that is.

2. Originally did updates on all components, Lifecycle, DRAC , BiIOS

3. 5.1 build 1743533

4 yes, Management center shows OMSA Status Update required

Logs show clean up until it starts the inventory after the reboot, then I get inventory failed, failed to get ip address of DRAC card. If I run inventory on demand logs show failed to get OMSA inventory and then the mark must be well formed message. Last nights scheduled inventory shows the same failed to get inventory and markup message

1 Message

May 21st, 2014 10:00

Hi,

we have the same problem. Today I updated our three ESXi Server from 5.1.0 1612806 to 5.1.0 1743533 after updateing the first Server the error appears. The Inventory on the other two Server are running fine.

"Inventory failed for host esxi Reason: The markup in the document following the root element must be well-formed."

Server PE R710

BIOS 6.4.0

iDRAC6 Firmware 1.97(Build02)

Lifecycle-Controller Firmware   1.6.5.12

OpenManage Integration for VMware vCenter

2.1.0.23

(Management center shows OMSA Status Update required)

VMWare

5.1.0 1743533

5 Posts

May 21st, 2014 10:00

currently 1:45 into a call with Dell they are telling me it is abug, OM wont run with that build. Suggested I roll back VMware. Will keep it posted

 

16 Posts

May 28th, 2014 08:00

I have the same problem with OMSA 7.3 or 7.4 and ESXi 5.1 build 1743533

Works fine on build 1612806.

rollback on VMWare is not acceptable - the update fixes a number of serious crashes and security vulnerabilities.  We need a fix for OMSA.

June 9th, 2014 11:00

Was there ever a solution to this problem? A rollback is unacceptable at this point.

5 Posts

June 9th, 2014 12:00

Nothing, Dell says it may be fixed in next version, no ETA. Normal Dell answer. Will look around before refreshing servers next time

June 9th, 2014 13:00

Just saw this on another post about the same thing:

Update from our VMware case; It is fixed if you upgrade to 5.5 U2. If you'd rather stay on 5.1, this issue will be fixed on 5.1P05, and 5.1 U3. There is no release date set for P05 yet, but from internal discussion I wouldn't expect it sooner than late July to August.

16 Posts

June 23rd, 2014 07:00

I can confirm that the latest set of patches from vmware along with the appliance upgrade have resolved this issue :)

5 Posts

June 23rd, 2014 08:00

Where did you download the Dell patch from? I can't find it

16 Posts

June 23rd, 2014 08:00

You have to go to the vCenter plugin Admin portal webpage and log in.  It is not in vCenter.

Go to Appliance management, and there is "Update Virtual Appliance" at the top of the page in the middle.

No Events found!

Top