VMware Cloud Community
MorDrakka
Contributor
Contributor

Update mgr plugin unable to enable

Hi,

The following is my current setup:

Server A VC server 'running'

Server B License Server and Update Manager server, all running.

In my VI client I can download de update manager plugin. but I am not able to 'enable' it When trying to do so I get the error:

"The Request failed because of a connection failure'.

I restart both VC service and Updata manager services multiple times(discovered this issue some time ago)

I am using no firewall between the two nodes.

The used user accounts for update manager service has complete access to VC server.

Security logging logs no fails.

I tried installing the UM plugin on multiple clients (New ones too).

I checked the UM file "vci-integrity.xml", no oddities there.

I have the feeling I am missing something basic here. Anyone got some clues ?

Reply
0 Kudos
3 Replies
elgordojimenez
Contributor
Contributor

I am having the same exact error. I will browse the web a bit more but will more likely give vmware a call and let you know mate. Or if you found the solution for this let me know.

        • If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful ****

**** If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful ****
Reply
0 Kudos
MorDrakka
Contributor
Contributor

VMware solved the issue for us. Our problem was the VUM service on the second server was not running on standard ports. i suplied different ones in the installer. What we did not know it has to be the same ports as the Virtual Center.

We needed to edit vci-integrity.xml with the following:

<enableReverseProxy>false</enableReverseProxy> change into <enableReverseProxy>true</enableReverseProxy>

Go to </proxySvc>

Change into:

<ports>

<http>2080</http>

<https>2443</https>

</ports>

</proxySvc>

Where 2080 and 2443 are the ports you use for VUM. However only changing the vci-integrity.xml file and restarting the service did not work. I had toreïnstall VUM and reïnit VUM DB, then change vci-integrity.xml then restart servic, then it worked.

Hope this helps for you.

Ad van Bokhoven

Reply
0 Kudos
elgordojimenez
Contributor
Contributor

Hello,

I had the same exact error this morning, this happened after we RE-IP the VC Server, had to do the following:

1) On the Virtual Center DB checked the following tables:

VPX_EXT_CLIENT.URL

VPX_EXT_SERVER.URL

The IP on these tables was set to the old IP, so I changed that for the new IP

2) rebooted the server

3) Once it came back up I ran the Update Manager .MSI file ONLY and completely uninstalled the application

4) rebooted the server

5) ran the VC Install and it automatically detected the only missing

addon was vc update manager, went through the install and selected the

existing DSN entry but selected the option to start with a new blank

database for update manager only. i backed up before just in case.

6) started VIC and logged on, I waited until it completed the schedule task and update signature task (takes a while)

7) checked the plugins and was able to tick update manager and it started successfully.

hope this helps, cheers.

        • If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful ****

**** If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful ****
Reply
0 Kudos