While working on getting my hosts properly patched, I found I couldn’t even do a scan on them.


Alright so next I took a look at the esxupdate log on the host.


Both of these correspond to a VMware kb found Here

The cause as listed in the KB “This error occurs when two VIBs use the same vSphere Update Manager (VUM) identifier or bulletin ID (type, name, vendor, version) with different attributes or payload.”

The things I found interesting about this issue is it does not affect ESXi 5.5 or 4.1, atleast according to VMware. However the error above occurred on a ESXi 5.5 host.

The solution to which is the re-initialization of the VMware Update Manager Database, or to Manually install the VIBs.

I personally am a Update Manager kind of guy, so that is how I am going to approach this.

The full instructions for re-initializing the VUM Database are Herehttp://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2043170

First things first…

  1. Make sure you have a backup of the VUM database.
  2. Stop the VMware Update Manager Service
  3. Second you should get into the server where VUM is hosted and open an admin command prompt and run the following command:
    1. C:\Program Files (x86)\VMware\Infrastructure\Update Manager\vciInstallUtils.exe -O dbcreate -C . -L .  (Both .  should be used)
    2. Also your path to that file might be different depending on where VUM was install in your environment. Also as noted in the KB “Note: This command completely erases the Update Manager database. All custom baselines and imported patches are lost.”
  4. Restart the VMware Update Manager Service
  5. Go into vCenter-Update Manager-Configurations-Download Settings- and Download Now


And again per the KB “Re-import any offline bundles, async drivers, third party extensions, and ESXi upgrade bundles.”

Once Completed. I was able to scan my hosts again…


Categories: vCenterVMware


Leave a Reply

%d bloggers like this: