• EMC Elect 2015 EMC Elect 2015 

    EMC Elect represents an unprecedented opportunity for members to receive exclusive access, privileges, and status in appreciation for their contributions to the EMC community.

    Read more

  • Demo Image Everything you need and nothing you don’t. EMC MOBILE is the essential tool for those of us who live EMC. Now your documentation library is available and in-sync online or off direct from the EMC Cloud


  • FreeWhether you're looking to broaden your awareness of emerging technologies, learn new skills for news roles, EMC Education offers free e-Learning Fundamentals courses to help you redefine your skills. 

    Read more
  • FreeVMware Fusion 7 Professional delivers improved IT controls, unsurpassed platform support, more powerful virtual machines, and enhanced usability. VMware Fusion 7 is optimized for the latest Macs and ready for OS X Yosemite and Windows 8.1 to deliver the ultimate Windows on Mac experience.

    Read more
  • Demo ImageWhy Advertise on Mikes.eu

    Mikes.eu traffic varies depending on the post. We have a VERY focused audience in the Virtualization, Storage and Cloud Marketing space. We have been ranked in the top 5 of Favorite Independent Blogger and one of the most visited website.


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

Written by on . Posted in How to

When I tried to edit the settings thru "edit settings" on my Microsoft server 2008 R2 templates in vSphere Client version 4.1.0 build 258902 I get the following error:

Call "PropertyCollector.RetrieveContents" for object "propertyCollector" on vCenter Server "name vCenter server" failed.

I removed the VM template from the inventory and added it again from the data store. After this trick it was working again. Problem solved!

But what was the problem? According to Bjorn Bats (http://www.bjornbats.nl) who was incredibly fast with his response it seems that this happens after an upgrade in vSphere. With this conclusion he could be right, because I just updated my vSphere farm from ESX 4.0 Update 2 to ESX 4.1.

It's wise to check if you still can convert en deploy a new virtual server. Just to be sure!