Thanks for the update!!! = )
Anything yet? = )
I've just stumbled upon the same bug, and have opened a case this morning.
I can poweron the VM in question using an "Administrator" role applied at the Hosts & Clusters level, but not using a limited role which normally can perform this action.
We applied Patch2 to VC2.01 a couple of weeks ago.
Tried restarting the VirtualCenter Service on the VC server, to no avail.
I can also connect with VI Client 2.01 (build 40644) DIRECTLY to the ESX node hosting the VM at this time and power it on.
Not sure what the deal is yet, but that's why the support is there, eh?
Will post results of this inquiry when completed. (or they give up and finally build this on Linux. -- Where's my Linux Remote Console ?
For ours we are still working with support. It looks like the problem only happens on hosts in a cluster ( regardless of if DRS or HA are turned on or off ). The next step for us is to move one host to a new cluster and see if the problem surfaces there.
Looks like the issue, for us, was an absence of permissions on the cluster itself. We typically assign users permissions on virtual machines, or folders of virtual machines, and hosts. When I added read only to the cluster and set it to not propagate my users were able to start their virtual machines without getting the error.
Hope this helps someone else. Only 2-3 months working with support only to stumble upon this myself
Just a straggling post to this thread... I also saw this same error message numerous times during my efforts to modify the default permissions. I was attempting to create a local group on the VC server called VIadmins, and place the appropriate domain user group into that local user group. I then granted the VIadmins group administrator rights on the datacenters within VC. The problem came about when i removed the local Windows Administrators group from the VC administrators of the Virtual Infrastructure.
FYI - Just had this problem today when trying to right click and remove an invalid VM. The resolution was to disable the virtual infastructure client plugins. After I removed the VM from inventory I was able to re-enable the plugins.
Moved to VMware vCenter forum
Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009, url=http://www.virtualizationpractice.comVirtualization Practice Analyst[/url]
Now Available: url=http://www.astroarch.com/wiki/index.php/VMware_Virtual_Infrastructure_Security'VMware vSphere(TM) and Virtual Infrastructure Security: Securing the Virtual Environment'[/url]
Also available url=http://www.astroarch.com/wiki/index.php/VMWare_ESX_Server_in_the_Enterprise'VMWare ESX Server in the Enterprise'[/url]
[url=http://www.astroarch.com/wiki/index.php/Blog_Roll]SearchVMware Pro[/url]|url=http://www.astroarch.com/blogBlue Gears[/url]|url=http://www.astroarch.com/wiki/index.php/Top_Virtualization_Security_LinksTop Virtualization Security Links[/url]|url=http://www.astroarch.com/wiki/index.php/Virtualization_Security_Round_Table_PodcastVirtualization Security Round Table Podcast[/url]