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?

[admin6]

As well, that was not a typo (on my post):

The Plugin Manager error msg. indicates: port 8443-3 in the error msg.

The .xml files use 8443. Still not working.

[Dworkins]

Hello,

I have the same problem, any answer someone about this wierd problem i have done both work around but without any result.

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1010725&sliceId=1&docTypeID=DT_KB_1_1&dialogID=29156774&stateId=1 0 29162026

Best regards

Gabriel

[Ramesh Jagannatha Shetty]

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

Status plug-in.

As a result of unable toenable plug-in user will not be able to check vCenter Server status and ESX

host Hardware Status.

*Workaround

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.

3.

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

installation path)

5. In VirtualCenter Advanced Settings update hostname for –

• VirtualCenter .VimWebServicesUrl

• VirtualCenter .VimApiUrl

*NOTE:

• 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.

Thanks,

Ramesh

[Dworkins]

Hi Ramseh,

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!

Gabriel

[Ramesh Jagannatha Shetty]

Hi Gabriel,

Great to hear that issue is resloved. You can mark this issue as answered.

Regards,

Ramesh

If you find this information useful, please award points for "correct"!

[admin6]

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!

[Texiwill]

Hello,

Moved to the vCenter Server Forum.

Best regards,

Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009, Virtualization Practice Analyst[/url]
Now Available: 'VMware vSphere(TM) and Virtual Infrastructure Security: Securing the Virtual Environment'[/url]
Also available 'VMWare ESX Server in the Enterprise'[/url]
[url=http://www.astroarch.com/wiki/index.php/Blog_Roll]SearchVMware Pro[/url]|Blue Gears[/url]|Top Virtualization Security Links[/url]|Virtualization Security Round Table Podcast[/url]

[zikria]

Hi Remesa,

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,

Zikria

[beovax]

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 :smileysad:

[zmclean]

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.

Z-Bone

[beovax]

any update on this? I think I may have to log a call tomorrow on this one

[zmclean]

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

[beovax]

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 :smileyhappy:

[zmclean]

Could be an update 1 issue. Works on our DR Standalone EXS server we have in a remote location. It was upgraded as well.

[beovax]

problem did occur after installing update 1. Funny thing they have listed this as one of the fixes, well at least this problem if you change the server name. Maybe we need to rename our servers :smileyhappy:

having said that I hve just read through the release notes again and cant see it mentioned, maybe I made it up in my head

[zmclean]

Here is the new KB they want me to try

[akash1980]

KB URL please? Seems you missed to provide KB link.

I have opened case with VMware more than 2 weeks ago, but they haven't provided fix for this. They said resolution is going to take some time and they are involving their Engineering team.

Thanks,

[zmclean]

http://kb.vmware.com/kb/1010641 Didnt work

Z-Bone

[akash1980]

http://technodrone.blogspot.com/2009/12/case-of-my-ssl-cert-rtfm.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3Atechnodrone%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

[akash1980]

Hi Ramesh,

> is working fine, but it's never going to https://<hostname>:8443. ( Page can't be displayed)

Any ideas on how to goahead?

I tried all your steps, no joy :smileysad:

Thanks,

[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=1010641