Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Update Manager fails to scan an ESX Server for updates when using non-default Web Services HTTP port (1003943)

Symptoms

Scan of ESX Server 3.5 host using Update Manager fails with the error Patch Metadata Not Found . 
 
The following entries are reported in Update Manager logs:
  • [hostUpdateBase, 279] Depot for update: Unknown corrupted. remove the package from DB.
  • [hostUpdateBase, 165] Patch Metadata Not Found: [PatchID: Unknown][Missing file: 033A07F8]
  • [vciTaskBase, 442] Task execution has failed: SingleHostScan : Patch Metadata Not Found: [PatchID: Unknown][Missing file: 033A07F8]

Resolution

This error occurs if the web service HTTP port in VirtualCenter is not set to the default port (the default port is 80).
 
Perform one of the following workarounds based on your situation.

Workaround 1

VMware Update Manager automatically opens firewall ports 9000-9100 on ESX Server 3.5 during scan or remediation. If port 80 cannot be used as the web service HTTP port, use a port in the range of 9000-9100:
  1. Log in to the Virtual Infrastructure Client and click Administration.
  2. Click VirtualCenter Server Management Server Configuration.
  3. Click Web Service.
  4. Change the HTTP port to a new value, within the 9000-9100 range.
  5. Click OK and restart VirtualCenter Server service.
  6. Restart the Update Manager service.
  7. Log in to Virtual Infrastructure Client after both VirtualCenter and Update Manager services have been restarted,
  8. Disable the Update Manager Plug-in in the Virtual Infrastructure Client and re-enable it.

Workaround 2

If port range 9000-9100 cannot be used as web service HTTP port in VirtualCenter:
  1. Enable the custom VirtualCenter web service HTTP ports in the ESX Server's firewall by entering the following command in the service console:

    esxcfg-firewall --openport ####,tcp,out,dynamicupdates

    Note: #### is the custom port being used by VirtualCenter.
    You can check the custom port by logging into VirtualCenter and clicking Administration Menu > VirtualCenter Management Server Configuration > Web Service.

  2. Restart the Update Manager service.
  3. Log off and log in to VirtualCenter using the Virtual Infrastructure Client.
  4. Disable and re-enable the Update Manager plug-in.

Additional Information

This issue can also be caused by an inability to scan a host because of a Port 80 conflict with VirtualCenter when both are installed on the same server. Ensure to select Access patch depot through Web port (not through reverse proxy) in Update Manager setup.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 8 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 8 Ratings
Actions
KB: