Scanning ESXi hosts using VMware vSphere Update Manager 5.x and 6.0 fails at 5% with an unknown error

search cancel

book

calendar_today

VMware vCenter Server

Symptoms:

A VMware vSphere Update Manager host scan fails at 5%
You see the error:

VMware vSphere Update Manager had an unknown error. Check the events and log files for details.
In the C:\ProgramData\VMware\VMware Update Manager\Logs\vmware-vum-server-logcpp.log file, you see entries similar to:

<YYYY-MM-DD>T<time> 'HostUpdateDepotManager' 3440 ERROR] [patchDepotManager, 213] Failed to get filesize for: D:\hostupdate\vmw\metadata_xxxxxxxxxx.zip, please check if the file exists and accessible. Error: boost::filesystem::file_size: The system cannot find the file specified
[<YYYY-MM-DD>T<time>:813 'SingleHostScanTask.SingleHostScanTask{360}' 3440 ERROR][vciTaskBase, 564] Task execution has failed: boost::filesystem::file_size: The system cannot find the file specified

</time></time>
Note: In the preceding log entry, metadata_xxxxxxxxxx.zip is unique. The X's are specific to the environment.

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
This issue occurs after reinstalling or upgrading vCenter Server and Update Manager

VMware vCenter Update Manager 5.0.x
VMware vCenter Update Manager 5.1.x
VMware vCenter Update Manager 5.5.x
VMware vCenter Update Manager 6.0.x

This issue occurs if the path to the metadata_xxxxxxxxxx.zip file is not found.

To resolve this issue, move the metadata_xxxxxxxxxx.zip file to D:\hostupdate\vmw\.

Locate the metadata_xxxxxxxxxx.zip file reported in the vmware-vum-server-logcpp.log file.

Notes:
- By default, the file is located at C:\ProgramData\VMware\VMware Update Manager\Data\hostupdate\vmw\metadata_xxxxxxxxxx.zip. This path differs depending on your installation.
- If VMware vSphere Update Manager is reinstalled on a different machine, the file is located on the previous machine.
Copy the metadata_xxxxxxxxxx.zip file to D:\hostupdate\vmw\.

Note: Ensure that the location to which the metadata_xxxxxxxxx.zip file is copied matches the file path identified in the vmware-vum-server-logcpp.log file error.
Navigate to C:\hostupdate\offline\ and copy the metadata_xxxxxxxxxx.zip file to this location.

Note: If a folder named offline does not exist, create it.
Verify that the issue is resolved by performing a host scan with Update Manager.

Note: Ensure that the firewall rules on the host are enabled for Update Manager.

thumb_up Yes

thumb_down No