Update Manager cannot accept requests (vCenter Update 4)

Details

If a new port is specified for HTTP or HTTPS Web Services when upgrading VirtualCenter to version 2.5 Update 4, the new port is not set for configuration of Update Manager server. 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 new port by editing the vci-integrity.xml file in the Update Manager installation directory at C:\Program Files\VMware\Infrastructure\Update Manager\ .

Note: The ports need to be changed the 'vpxdLocation' section

Product Versions

vCenter 2.5 Update 4

Additional information

This document is based on KB Article 1004412 that referrs to Virtual Center 2.5 Update 1