Hi All,
Just patching some hosts and getting a 'Failed to retreive data' message. I get this just after I click on 'Remediate' for the host and then I see the Updates section greyed out with this message across all the updates. Any idea why?
Cheers,
Neel
Have you tried to force manually the download of patches (from the VC tasks)?
Are you using a proxy setting?
Andre
How do I do it manually?
No I am not going through a proxy.
Click on "scheduled tasks" icon (under the menu bar).
Select the task for update download.
Right click and choose Run.
Andre
Did you do scan for updates before remediate on the host? Also if you have updated or moved Update Manager database make sure that is working.
Mike
Oh yes sorry, that works fine. I am able to download the patches it seems, and Scan the host for updates.
I am rebooting the VC server just to see if that does anything.
I just had this same issue and ran across your post when looking through the forums. After not finding anything solutions, I worked through the issue on my own. Listed below is what I did to resolve the problem.
- Checked virtual center log's for update MGR which didn't have anything that helped. C:\Documents and Settings\All Users\Application Data\VMware\VMware Update Manager\Logs
- Redownloaded patches -worked fine
- Rescanned host - worked fine
- Restarted update MGR service - didn't resolve issue
- Opened VMware client on a different system and added the update MGR pluging - did not have the issue
- I then removed the update MGR plugin on my virtual center system where I was experiencing the issue (uncheck box)
- I then closed Vi client, reopened and added back the Update MGR plugin. The issue was resolved.
If you found this or any other answer helpful please consider the use of helpful or correct buttons to award points.
4 sept. 2012
Re: Update Manager - 'Failed to retrieve data'
"Failed to retrieve data" is an issue with the Database. (in our case)
When VMWare support check the ODBC configuration, they find there are two similar DSN configuration on ODBC32 and ODBC64 because we upgraded vcenter & update manager 4.1 (32b) to vCenter & update manager 5.0 (64b) and we didn't delete ODBC32. So, there was an conflict. We deleted all ODBC DSN and create an unique DSN (for update manager).
Restart service and enjoy 😉
If the problem persist reinstall plugin.
Hope that can help someone 😉
It's been a while but for your information the solution above never really works well just a while (2 days) ! I had to recreate a new database for my Update Manager Server 1 week after !
I think the database was corrupt and didn't want display repository ! VMWare Support Developer tried some tricks on database but nothing more !
Conclusion - Try to backup VUM configuration (Baseline) and recreate Database !
++
Worked for me!