vCenter Update manager is unavailable after upgrading to vCenter Server Appliance 6.5
search cancel

vCenter Update manager is unavailable after upgrading to vCenter Server Appliance 6.5

book

Article ID: 322201

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
  • vCenter Update Manager 6.5 is unavailable
  • You see error similar to:
ERROR interface com.vmware.vim.binding.integrity.VcIntegrity is not visible from class loader
  • In the vSphere-Client.virgo.log file, you see entries similar to:
    [ERROR] data-service-pool-795 70004032 100907 200826 com.vmware.vum.aspects.LoggingAspect Exception caught in class 'com.vmware.vum.dataservice.impl.CompliancePropertyProviderAdapterImpl', line 533 java.lang.IllegalArgumentException: interface is not visible from class loader
    at java.lang.reflect.Proxy$ProxyClassFactory.apply(Proxy.java:581)
    at java.lang.reflect.Proxy$ProxyClassFactory.apply(Proxy.java:557)
    at java.lang.reflect.WeakCache$Factory.get(WeakCache.java:230)
    at java.lang.reflect.WeakCache.get(WeakCache.java:127)
    at java.lang.reflect.Proxy.getProxyClass0(Proxy.java:419)
    at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:719)
    at com.vmware.vim.vmomi.client.common.impl.ManagedObjectFactoryImpl.createManagedObject(ManagedObjectFactoryImpl.java:87)
    at com.vmware.vim.vmomi.client.http.impl.HttpClient.createStub(HttpClient.java:89)
    at com.vmware.vum.client.adapters.updatemanager.impl.UpdateManagerServiceImpl.login(UpdateManagerServiceImpl.java:174)
    at com.vmware.vum.client.adapters.updatemanager.impl.UpdateManagerServiceInstantiator.instantiate(UpdateManagerServiceInstantiator.java:58)
    at com.vmware.vum.client.adapters.updatemanager.impl.UpdateManagerServiceProviderImpl.createVumService(UpdateManagerServiceProviderImpl.java:273)
    at com.vmware.vum.client.adapters.updatemanager.impl.UpdateManagerServiceProviderImpl.getService(UpdateManagerServiceProviderImpl.java:137)
    at sun.reflect.GeneratedMethodAccessor823.invoke(Unknown Source)


Environment

VMware vCenter Server Appliance 6.5.x

Resolution

To resolve this issue:
1. Ensure that required time-zone is configured for VCSA through VAMI page.
2. Reset the serenity database on the vCenter using the steps below:
Note: Take a snapshot of the vCenter before reset.
(a) Login to the appliance using SSH.
(b) Run this command to stop the vSphere Web Client service
    # service-control --stop vsphere-client
(c) Run this command when logged in as root through a console shell or SSH session:
    # rm -rf /storage/vsphere-client/SerenityDB/serenity/*
 (d) Run this command to start the web client service
    # service-control --start vsphere-client