Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

Update Manager fails with the error: Metadata for patch missing (1004914)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 14994Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

After downloading ESX patches using Update Manager, scanning the ESX host fails

Update Manager fails

You see errors similar to:

Metadata for patch missing
Download host update packages: System error 3: The system cannot find the path specified.; Context: Failed to create temporary file. Error: 3

Cannot update ESX hosts

In the esxupdate.log file of Update Manager, you see the error :

connection refused 111

In the vmware-vci-log4cpp.log file located at C:\Documents and Settings\All Users\Application Data\VMware\Update Manager or C:\Users\All Users\VMware\VMware Update Manager\Logs, you see connection errors similar to:

[08Apr17-0937] DEBUG: summary: /usr/sbin/esxupdate --HA --flushcache -d http://esxhost/vci/hostupdates/hostupdate/esx/esx-3.5.0 scan
[08Apr17-0937] DEBUG: root: Enabling hostagent interface
[08Apr17-0937] DEBUG: db: dbfile = [/etc/vmware/patchdb/patch.db], 3 keys
[08Apr17-0937] DEBUG: Depot: Download Rules: {'blacklist': ['*.rpm', '*/headers'], 'exclusives': []}
[08Apr17-0937] ERROR: root: [Errno 4] IOError: <urlopen error (111, 'Connection refused')>

Resolution

To resolve the issue:

Ensure that the Update Manager hostname can be pinged from the VirtualCenter and the ESX host.

Ensure that the Windows temp directory is present in the system where Update Manager is running. If not, create one.

Ensure that the Update Manager is allowed through the ESX firewall. For example, if the port for Update Manager is 8080, the command is:

esxcfg-firewall -o 8080,tcp,out,updatemanager

For more information, see VMware Update Manager Network Port Requirements (1004543) .

Related Information

If you make changes to Update Manager ports, ensure to restart the VMware Update Manager service or reboot the server for the changes to take effect. For more information on restarting services, see Stopping, starting, or restarting vCenter services (1003895).

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
确定正在 ESXi 主机上主动使用的存储或网络驱动程序 (1034674)

KB
•
vCenter Server 4.x/5.x での SNMP トラップの構成 (1006438)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
vCenter Server 4.x 以降へのアップグレード後に VMware vCenter Management Web サービスを開始できない (1011648)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware VirtualCenter

VMware vCenter Update Manager

VMware ESX Server

Related Versions:

VMware VirtualCenter 2.5.x

VMware vCenter Update Manager 4.0.x

VMware vCenter Update Manager 1.0.x

VMware ESX Server 3.5.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant