Unable to connect to the vCenter Update Manager when it is configured to use non-default ports for http and https

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

If you are using vCenter Server 2.5 Update 2 or later, and vCenter Server and vCenter Update Manager are installed on different servers, you may experience these symptoms:

• You cannot connect to the vCenter Update Manager.
• You cannot enable the vCenter Update Manager Plug-in.
• When trying to install the Plug-in, you see the error:
  
  Unable to Connect to the Remote Server
  
  
• When trying to enable the Plug-in, you see the error:
  
  The Request failed because of a connection failure
  
  
• vCenter Update manager cannot connect to vCenter Server.
• In the vCenter Update Manager webServer logs, you see errors similar to:
  

  [2009-02-20 13:27:03.663 'Ufa' 5232 info] Plugin initialized
  [2009-02-20 13:27:03.663 'ProxySvc' 5232 info] Proxy service created: http port (80), https port (443)
  [2009-02-20 13:27:03.678 'ProxySvc' 5232 error] Failed to create http proxy: Resource is already in use: Listen socket: :80
  [2009-02-20 13:27:03.678 'ProxySvc' 5232 info] Proxy service stopped
  [2009-02-20 13:27:03.678 'ProxySvc' 5232 info] Proxy service destroyed
  [2009-02-20 13:27:03.678 'Ufa' 5232 info] Plugin started
  
  Note: The default path to these logs is C:\Documents and Settings\All Users\Application Data\VMware\VMware Update Manager\Logs\vum-webServer-*.log. Check the most recent version of the log.

Environment

VMware VirtualCenter 2.5.x
VMware vCenter Update Manager 1.0.x

Resolution

To resolve this issue and confirm which http and https ports are configured for vCenter Update Manager, check the registry on the vCenter Update Manager server.

To check the registry on the vCenter Update Manager server

1. Click Start > Run, type regedit, and click OK.
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Vmware, Inc.\VMware Update Manager.
   
   Notes:

• In 64-bit versions of Microsoft Windows, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Vmware, Inc.\VMware Update Manager
  
• HttpPort identifies the port configured for http and has a default value of 80.
• HttpsPort identifies the port configured for https and has a default value of 443.

To resolve this issue, update the vci-integrity.xml file on the vCenter Update Manager server.

To update the vci-integrity.xml file:

1. Make a backup copy of vci-integrity.xml. The default path is C:\Program Files\VMware\Infrastructure\Update Manager\vci-integrity.xml.
2. Open the vci-integrity.xml file for editing
3. Add the <ports></ports>, <http></http> and <https></https> tags between <proxySvc> and </proxySvc>. For example:
   

   <proxySvc>
   .
   .
   <ports>
   <http>9080</http>
   <https>9043</https>
   </ports>
   .
   .
   </proxySvc>
   
   Note: Set the port numbers for <http> and <https> to the values configured in the registry. In this example, port 9080 is used for <http> and port 9043 is used for <https>.

4. Save the file and exit.

5. Restart the VMware Update Manager Service for the change to take effect.

Additional Information

如果将 vCenter Update Manager 配置为对 http 和 https 使用非默认端口，则无法连接到 vCenter Update Manager
vCenter Update Manager が http および https にデフォルト以外のポートを使用するように構成されている場合に、vCenter Update Manager に接続できない