reto
Contributor
Contributor

Error in Update Manager since vCSA Upgrade to 6.5 Update 1

Hi there,

We have recently upgraded our vCenter appliance from 6.5 to 6.5 Update 1.

Since then, the Update Manager Tab in the webclient is not working anymore, we always receive the following error message:

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

Many thanks in advance for your help.

Best regards

Reto

7 Replies
conyards
Expert
Expert

This could be a straight forward as the firewall rule to the VCSA,

The port used by vSphere Update Manager client plug-in to connect to the vSphere Update Manager SOAP server is TCP 8084. VMware vSphere Update Manager.​ 

So you can check this by attempting to telnet to port 8084 on the VCSA, if you can't connect then you'll need to open the port bidirectionally.

Simon

https://virtual-simon.co.uk/
reto
Contributor
Contributor

Hi Simon

Many thanks for your answer, I really appreciate it.

Telnet to port 8084 is working fine.

The Update Manager was working great before the upgrade.

Do you have any other idea?

Cheers

Reto

0 Kudos
reto
Contributor
Contributor

Hi there

Has anyone an idea how I can reset the update manager?

Many thanks Smiley Happy

Best regards

Reto

0 Kudos
JustinDevelops
Contributor
Contributor

While I have not fixed the issue yet as I am trying to figure out what firewall they are talking about this link seems to have the fix we are all needing.

https://www.vmscribble.com/vcenter/6-5-vum-elm-interface-com-vmware-vim-binding-integrity-vcintegrit...

0 Kudos
JustinDevelops
Contributor
Contributor

Actually wanted to add that, the previous post I sent did nothing. Now I followed this post and I am back in business now. Hopefully it helps.

https://blog.ukotic.net/2017/10/03/vmware-update-manager-vum-fails-to-load-within-vsphere-web-client...

Miph120
Contributor
Contributor

A bit late, but I just wanted to say that JustinDevelops link to that article fixed it for me. Thanks!

0 Kudos
kevin8611
Contributor
Contributor

I once had the exactly same problem, actually, you can just ssh into vcsa, and restart update manger service, which works for me.

the command are:

service-control --stop vmware-updatemgr

service-control --start vmware-updatemgr

0 Kudos