Skip to main content

Update Manager 6.5 issue ""interface com.vmware.vim.binding.integrity.VcIntegrity is not visible from class loader""



This post is related to the issue what we faced today when we replaced the SSL certificates in our setup. 

When I launched the web-client and access the update manager tab,  I get the message  "interface com.vmware.vim.binding.integrity.VcIntegrity is not visible from class loader"






I started off by restarting the VMWare vSphere Update Manager Service for the affected vCSA:

1. Log into vCenter using the administrator@vsphere.local account.
2. Home - System Configuration - Services - Restart



This did not resolve my issue... And we tried restarting all the services by SSH/Console into the affected server and run the following commands:

service-control --stop --all
service-control --start --all
Still no luck. 

Make sure the certs are applied and it gets reflected in the config file. ( verify if the thumbprint matches) 

root@homelab71 [ /usr/lib/vmware-updatemgr/bin ]# pwd
/usr/lib/vmware-updatemgr/bin

root@homelab71 [ /usr/lib/vmware-updatemgr/bin ]# ./updatemgr-util config -g | less


    <vci_vcIntegrity>
      <EsxTaskMax>10</EsxTaskMax>
      <LocalTaskMax>10</LocalTaskMax>
      <downloadAfterInstallation>true</downloadAfterInstallation>
      <encryptGuestInfo>true</encryptGuestInfo>
      <guestRebootTimeout>900</guestRebootTimeout>
      <guestShutdownTimeoutMinutes>10</guestShutdownTimeoutMinutes>
      <path>../lib/libvci-vcIntegrity.so</path>
      <toolsUpgradeTimeoutSec>1800</toolsUpgradeTimeoutSec>
      <toolsWaitTimeoutSec>600</toolsWaitTimeoutSec>
      <vimNameSpace>vim.version.version10</vimNameSpace>
      <vpxdLocation>http://deheremvc30.emea.adsint.biz:80/</vpxdLocation>
             <vpxdThumbprint>DD:DD:1D:C7:EF:D7:C7:E7:37:E7:55:57:55:55:55:55:57:57:55:55</vpxdThumbprint>
    </vci_vcIntegrity>


 Connect to the vCenter Server using SSH and run the following commands:

Re-try to replace the SSL certificates.

/usr/lib/vmware-updatemgr/bin/updatemgr-util refresh-certs
/usr/lib/vmware-updatemgr/bin/updatemgr-util register-vc
service-control --start vmware-updatemgr


Logout and login to the WebClient again. 

Verify that VMware Update Manager is accessible in the vSphere Web Client.

Popular posts from this blog

HOW TO EDIT THE BCD REGISTRY FILE

The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s