VMware vCenter Error Call “PropertyCollector.RetrieveContents” for object “propertyCollector” on vCenter Server failed

I wanted to modify my templates. After converting a template to a VM I tried to edit the settings. I received the following error: Call “PropertyCollector.RetrieveContents” for object “propertyCollector” on vCenter Server “VC” failed.

I once learned this trick from my fellow worker Bert that also helped me to overcome this annoyance. I removed the VM from the inventory and added it again from the data store. Fixed. But what was the problem? It seems to be a combination of the upgrade to vSphere 4.1 and maybe even to 4.0 Update 2 before that, and the mounting of an ISO that’s in a datastore that doesn’t exist anymore.

Being able to open the settings screen helps a lot in removing the link to the  non-existing ISO =)

All fine again, moving on to the next error message.

About Yuri de Jager
Technology Addict

33 Responses to VMware vCenter Error Call “PropertyCollector.RetrieveContents” for object “propertyCollector” on vCenter Server failed

  1. neyz says:

    Thanks for your help, that did the trick and saved us time opening a support ticket to vmware 🙂

    cheers !

  2. Thanks for this quick note. I was having issues and this was a great time saver!

  3. Marquis C says:

    Thanks. This was very helpful resolving the issue quickly.

  4. Steve says:

    We’ve also had it happen if the network label (dvSwitch) was no longer available. Removing from inventory, re-adding, then fixing the network label seems to fix it up.

  5. RickT says:

    Thanks. It worked for me.
    And I only upgraded vCenter to 4.1 (yet)

  6. Thankx, it did it for me as well. Just had the error this morning and google found your solutinon.

  7. Benito says:

    Thanks a lot, this info was very helpful.
    I tought that I was gonna lose my VM

  8. RateParentUp says:

    Thanks! This worked like a charm

  9. Martin says:

    Thanks for shareing! Great info!

  10. ANON says:

    This worked for me too. Thanks alot!

  11. thanks says:

    Thank you this is exactly what I was looking for!

  12. Josh A says:

    Thanks, This was very helpful for me as well.

  13. Robin says:

    Thank you. This solved my problem 🙂

  14. Abe says:

    Punched the ticket perfectly. Thanks man!

  15. Gabri says:

    This worked for me too. Thanks alot!!!

  16. Keith says:

    Found your solution from Google. Worked 100% thank you for posting.

  17. spillay8 says:

    Thanks for your help…….worked for me

  18. mittim12 says:

    Just wanted to say thanks for posting this. I ran into this issue and your blog saved me a ton of troubleshooting and a possible call to support.

  19. Thank you for posting this. It really helped me out.

  20. That was it! I was updating an old template that I haven’t touched in a while and I couldn’t figure out why the settings wouldn’t open. Thank you very much.

  21. paulgrevink says:

    Hi Yuri, thank you very much for this timesaver. Your solution worked like a charm.

  22. Pingback: 2010 in review | Yuri's Technology Blog

  23. dbutch1976 says:

    Fixed me too, thanks.

  24. Pingback: Vcenter erreur « PropertyCollector.RetrieveContents » « Virtuarsys

  25. Locky says:

    Большое спасибо за подсказку! Сам бы я в жизни не догадался! Удачи! =)

    Google translation: “Many thanks for the tip! Myself I would never have guessed! Good luck”

  26. JC says:

    you sir are a genius, thanks for sharing… saved me a lot of time by avoiding a support call

  27. Fred says:

    Thanks for sharing man !

  28. Stephan says:

    Worked like this – thanks!

  29. Pingback: Confluence: Technology

  30. Piotr says:

    Thx a lot for that valuable solution 🙂

  31. Martin says:

    The funny thing is, if you convert it back to a template and restart the vCenter service afterwards. It’s broken again.

  32. TomP says:

    Martin, try updating the vmtool also.

    Yuri, Thanks for the original note. it gave me the hit to fix it.

Leave a reply to Stephan Cancel reply