Skip to main content

Recently I moved the first step to vSphere 7.0, so I started by upgrading the vCenter in my homelab. The upgrade went pretty well, everything went smoothly and in less than a hour I have my new fresh 7.0 vCenter.

I started looking around on the UI and I wanted to import the ESXI 7.0 ISO to start the host upgrade but I get suddenthly an error. Yes as you can see below on the Update Manager tab or better, the “LifeCycle manager” I got this error:
An unexpected error as occured!

And if you can see some lines inside the GUI doesn’t proprely look in a good shape.

Luckly in my case I didn’t spent so much time on it. It was just only a matter to find the right KB that explain how to reset the “Upgrade Manager” database.

So, to fix it you just need to connect to your vCenter via SSH, use the shell and launch these commands:

  • service-control --stop vmware-updatemgr


  • /usr/lib/vmware-updatemgr/bin/ reset-db


  • rm -rf /storage/updatemgr/patch-store/*


  • service-control - -start vmware-updatemgr


Then after that, you need to close the browser, redo the Login in your vCenter and you will see that simply the issue is gone, and now the Lifecycle Tab is proprely working.

More details about this procedure are explain on the following VMware KB “Resetting VMware Update Manager Database on a vCenter Server Appliance 6.5/6.7/7.0″


I hope this will be helpful!


  • Per von Zweigbergk ha detto:

    FYI: The service-control –stop and –start commands have been mangled by your blog software so they’re not possible to copy paste.

    (Make sure there’s two hyphens before stop and start as opposed to the dash that’s introduced in the blog software.)

    Other than that, thank you. This helped me fix my Lifecycle Manager after an update.

    • Giovanni Dominoni ha detto:


      thanks for the hint, I’ve correct that part of the article so now is possible to use copy-paste directly.
      I’m glad that this solution solved your issue!

  • Scott ha detto:

    Solved my issue. Thank you

Leave a Reply

Giovanni Dominoni's Tech Blog