Fresh Install - vCenter Service Status and Hardware Status plugins in vSphere 4.0 client Plug-In Manager not working

[admin6]

Fresh install of vSphere Server 4.0 with vSphere client. Separate SQL 2005 DB.

2 plugins are not working,disabled with almost identical error msgs stated directly in the Plug-In Manager.

1.) vCenter Service Status -

The following error occurred while downloading the script from https://primary:8443-3/health-ui/scriptConfig.xml:Unable to connect to the remote Server

2.) vCenter Hardware Status -

The following error occurred while downloading the script from https://primary:8443-3/cim-ui/scriptConfig.xml:Unable to connect to the remote Server

There is no remote VirtualCenter - the box resolves to itself locally (it's name is primary) fine.

The browser resolves to the vSphere Welcome page if I go to http://primary.

https://primary resolves to the same page, albeit with a cert error.

If I install the cert (VMware default cert) into the Personal and Trusted Publishers Store, I still see the Cert error. Hmm.

If I look in C:\ProgramFiles\VMware\Infrastructure\VirtualCenter Server\extensions, there is a health-ui and cim-ui folder, respectively, each with an extension.xml

Changing the https to http, or the name to IP (within the .xml files), or bouncing the Virtual Center Server (restarting) does not help remedy the issue.

Any ideas?

[akash1980]

http://technodrone.blogspot.com/2009/12/case-of-my-ssl-cert-rtfm.html?utm_source=feedburner&utm_medi...technodrone%28Technodrone%29&utm_content=Google+Reader

Guys, try this. It may work. I have all similar symptons, but we are fine with giving password twice. Not sure what is more we need to check. Working with VMWare.

[zmclean]

That worked I redid the PFX file and that fixed my problem. Now the plugins start but the hardware and service status give errors. Thats another topic

Z-Bone

[jacamano]

This KB works fine for me:http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1011648

I change the maximum

memory pool of Tomcat form 1024 to 512 and Vcenter Hardware status and service status starts fine.

[bigDavefromTren]

Followed up on all of these suggestions; thanks but nothing seemed to work....however make sure your VMware Web Services is started. Can't connect to port 8443 unless this is started. DUH.

bigD

[CPooley]

Hey guys,

Is it safe to say that you are having these problems even with the VMware VirtualCenter Webservices service process running? I noticed mine was not running and turned it on and the errors went away.

best regards,

Chuck

[SecondCity]

Yep, +1 to Chuck's response. Checking services.msc shows that the VMWare Webservice wasn't even started, even though it was set to automatic. Hello, properly-enabled plugins! This also resolved the issue where I couldn't see Performance overviews (only Advanced metrics).

John

[CarlosGonzalez]

Try to check your DNS configuration of the machine that you are using to connect to the vCenter Server.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101064...