VirtualCenter fails to connect to Update Manager if a new HTTP or HTTPS Web Services port is specified during VirtualCenter installation
Details
If a new port is specified for HTTP or HTTPS Web Services when upgrading VirtualCenter from version 2.5 to version 2.5 Update 1, the new port is not used by VirtualCenter. The default port of the previous installation of VirtualCenter is used instead of the new port and VirtualCenter will not be able to connect to Update Manager. The following error will appear on the Update Manager tab of VMware Infrastructure Client:
The VMware Update Manager cannot accept requests now because VirtualCenter server cannot be reached, or the database cannot be reached, or it is in the process of stopping.
Solution
This issue only impacts upgrades of VirtualCenter server and Update Manager server, new installations are not affected by this issue.
To avoid this issue, do not specify a new HTTP or HTTPS Web Services port during an upgrade, use the port specified in the previous installation.
To work around this issue configure Update Manager to use the old port by editing the vci-integrity file in the Update Manager installation directory at C:\Program Files\VMware\Infrastructure\Update Manager\ .
Note: The ports need to be changed to the original under the 'Proxysvc' section
