Hope that helps.

Tara

"C:\Documents and Settings\All Users\Application Data\VMware\VMware Update Manager\Logs\vmware-vci-log4cpp.log"

The server that I have the Virtual Center Server software on is dual-nic'd. One address is routable, but the other is on a private, non-routed VLAN used for storage for certain ESX hosts.

By looking in it I found that my update scans were failing because the Update Manager was insisting on pointing to the non-routable address used by the second NIC in the server. The host I was trying to scan can't reach that address (it's at a different physical location).

By disabling the 2nd NIC I was able to verify that update scans would then work.

I had also this strange problem but i have solved it for my company.

Go to the vci-integrity.xml file and look for the following :

<!-- HostUpdate Management Configuration -->

<HostConfig>

In the Next Line Try something like that:

<PatchDepotURL>http://VCServerHostName:80/vci/hostupdates/hostupdate</PatchDepotURL>

restart the VMWare update manager service and then try to scan again.

Hope it works for you

I disable that nic, and restarted the vmware update service. Now all my servers are scaning and i am remediating them now.