I have the same problem, any answer someone about this wierd problem i have done both work around but without any result.
Will you please try to replace hostname i.e primarywith ip address. Restart VC service.
Or try below -
Unable to enable vCenter Service Status plug-in, Unable to enable vCenter Hardware
As a result of unable toenable plug-in user will not be able to check vCenter Server status and ESX
host Hardware Status.
1. edit C:\WINDOWS\system32\drivers\etc\hosts to add an entry <VP IP> <VC hostname>
2. Updated new hostname in extension.xml file for all extensions in VirtualCenter Server folder.
Updatednew hostname scriptConfig.xml from -- C:\ProgramFiles\VMware\Infrastructure\tomcat\webapps\cim-ui, C:\Program
Files\VMware\Infrastructure\tomcat\webapps\Health-ui (default installationpath)
4. Updatednew hostname in web.xml from -- C:\ProgramFiles\VMware\Infrastructure\tomcat\webapps\statsreport\WEB-INF\ (default
5. In VirtualCenter Advanced Settings update hostname for –
Make sure that VirtualCenter.InstanceName is not update with new hostname.
Make sure host name is getting resolved.
URL in VirtualCenter .VimWebServicesUrl, VirtualCenter.VimApiUrl new hostname should be resolved or use IP address.
Make sure VirtualCenter Web Access service is up and running.
Let us know if this work.
1 person found this helpful
Your workaround have worked fine, i also reduce the maximum memory to 512 in the tomcat settings and everything is working fine now.
Thank you very much for your help!
Great to hear that issue is resloved. You can mark this issue as answered.
If you find this information useful, please award points for "correct"!
Thanks Ramesh, I will try this later. Looking at the depth of your reply, I;m confident we have the right steps now. Thanks again!
Moved to the vCenter Server 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]
Unfortunately, I performed all the steps which you specified in your workaround but still had no success?
I restart the VMware VirtualCenter Management Webservices and still when I try to enable the plugins, no success. Not sure what else I can try?
Your help is much appreciated,
I am having this problem since upgrading to Update 1 vsphere. When I conenct directly to the hosts all the information appears, it is just missing when using VC. I havent changed the server name but I have run through all the above posts changing the name to the FQDN - still no joy.
The strange thing is I see this is listed as a fix in update 1, doesnt seem to be the case for me, it actually brakes it!!
I can ping the name, but did notice it was coming back with an IPv6 response. I have also tried disabling IPv6, I now get an IPV4 response, but still no plugins
Upgrade to Update 1 from 3.5 I am getting the same error. Also had to change port to 8444 but dont know if that has any effect.
any update on this? I think I may have to log a call tomorrow on this one
Nothing yet I have a ticket open with them for a week or more and they are testing some things in the lab. Using 8443 would probably fix it but we need to use 8444
doesnt work for me on port 8443 even with a fresh load of virtual center and no other app on their. Won't even open up using the vi client on the actuall server. Name resolution is all ok, tried disabling the firewall etc - very confused
works all ok if I talk to the esx hosts directly - sods law I just updated all my hosts to esxi with the cim agents to use the hardware monitoring, and now I still have to log onto each host manually see whats going on