Tag Archives: Update Manager

VMware Update Manager (VUM) Fails To Load Within vSphere Web Client

I recently upgraded my lab VCSA from version 6.5 (Build Number 5705665) to version 6.5 U1 (Build Number 6671409).  After the upgrade I noticed that VMware Update Manager was no longer working correctly.  Navigating around the various VUM pages I received the same consistent error message.

interface com.vmware.vim.binding.integrity.VcIntegrity is not visible from class loader

VUM management page

VUM Tab within an ESXi host

Checking the vCenter services within Administration > System Configuration they all appeared Up and Running.  Though all services were running I never the less restarted the VMware Update Manager service which unfortunately didn’t help.  I also tried restarting a few other services without much success.  So rather than just continuing to randomly restart services I decided to take a tougher approach and restart all services from the CLI.

After the stopping and starting of all vCenter services, which took a few minutes, VUM was back up and running again within the vSphere Web Client.  While this was a fairly drastic step to take, so would have been rebooting the vCenter server, which I’m glad I managed to avoid.

I’ve previous written about restarting vCenter services.  The process is quite simple.   First connect up to the CLI of the VCSA box.  Then run the below two commands.  Both the stopping and starting of services will take a few minutes each.  Once the services are restart the Web Client will take a further few minutes to fully start up and be accessible.  If all is successful Update Manager should be accessible once again.

Command> service-control --stop --all

Command> service-control --start --all

Restarting all the vCenter services like this is obviously a disruptive action.  Connectivity to vCenter will be dropped while the services restart.  Usually restarting all services on vCenter via the CLI is my last ditch attempt to resolve an issue before I attempt a reboot of the appliance.  While restarting the VCSA might have been the easiest thing to do to resolve this issue it’s not always necessary.

vSphere Update Manager 5.x to 5.5 Upgrade

A few days back I upgrade a vCenter Server Appliance from 5.0 to 5.5.  With that prerequisite out the way I can now upgrade vSphere Update Manager (VUM) from 5.0 to 5.5.  This will bring me one step closer to being able to use VUM to upgrade my ESXi hosts to 5.5.

The process is very simple and just a matter of a few clicks.  VUM still requires that it runs on a Windows Server, VMware having yet provided an appliance alternative --yet.  So you will have to download the entire vSphere vCenter 5.5 Windows installation from VMware.

The process for a fresh install of VUM is similar to an upgrade.  As I’m upgrading I’ll be running through the process I used. The first step is executing the installer.


Select vSphere Update Manager and Click Install


Click OK


If you have a previous version of VUM installed you will be prompted to upgrade.


Click Next to start to installation wizard.


Accept the license agreement.


A few things have changed in the latest version of VUM.  Take note of what will be removed.  Make sure the checkbox to download updates after installation is selected.


Enter in your vCenter details.  Port 80 is the default unless you have changed this during vCenter installation.  Enter in a user account and password that has admin rights into vCenter.  If you’re running a vCenter Server Appliance like me you can use the root account.


If you haven’t already upgraded your vCenter to 5.5 you will receive the following warning and will need to upgrade vCenter before you can continue any further.


If you’re upgrading you won’t be able to change any database DSN or driver details.  Click Next.


Select ‘Yes, I want to upgrade my Update Manager Database’.  Select the checkbox ‘I have taken a backup of the existing Update Manager database’.


If your windows server’s IP address is resolvable its name will be listed in the drop down list.  Select the server and leave the default ports unless you wish to change them.  If you need to go through a proxy to access the internet select the checkbox below else click Next


Click Install to start the installation.


Update manager will need to be shutdown to upgrade it.  Select ‘Automatically close and attempt to restart applications’.


Once the installation is complete open up the vCenter 5.5 C# client.  Select plugins on the menu bar.  Scroll down to Available Plug-ins and click Download and Install on VMware vSphere Update Manager.


So that’s it.  Maybe a little more than a few click though 😉

You can now access Update Manager as you normally would in the vCenter Client.