VMware Cloud Community
eoindubh
Contributor
Contributor

Problem getting some plugins to work in vCenter 4.1.0 U2

I am seeing the following alerts in the plugins manager of vCenter 4,1.0 Update 2 and the vCenter client is version 4.1.0 build 345043.:

vCenter Service Status VMware, Inc. 4.1
Disabled
Displays the health status of vCenter services
The following error occurred while downloading the script plugin from https://172.25.175.38:18443/health-ui/scr-iptConfig.xml:
Unable to connect to the remote server

Licensing Reporting Manager VMware, Inc. 4.1
Disabled
Displays license history usage

The following error occurred while downloading the script plugin from https://172.25.175.38:18443/license-ui/scr-siptConfig.xml:
Unable to connect to the remote server

vCenter Hardware Status VMware, Inc. 4.1
Disabled
Displays the hardware status of  hosts (CIM monitoring)
The following error occurred while downloading the script plugin from https://172.25.175.38:18443/cim-ui/script-Config.xml:
Unable to connect to the remote server

Right-clicking brings up an Enable prompt that disappears when clicked with no result.

I have searched for the health-ui, license-ui and cim-ui directories on the server and do not fild them. Neither do I find the scripe-Config.xml file. Support had me upgrade the server to 4.1.0 U2 a few months ago and I have been seeing this issue for a few weeks now.

Has anyone seen this issue before? It looks like I may need to re-install again which takes an act of Congress in this company to do. Smiley Wink

Tags (1)
0 Kudos
6 Replies
a_p_
Leadership
Leadership

Please take a look at http://kb.vmware.com/kb/1013472 to see whether this helps.

André

0 Kudos
eoindubh
Contributor
Contributor

I tried it but there is no change. I think that the issue is that, in the error message, it shows an error like The following error occurred while downloading the script plugin from https://172.25.175.38:18443/health-ui/scr-iptConfig.xml but when I look at the server.xml file in that directory, the port is not 18443 but rather 8443 which should be correct. Any ideas where it could be picking up the extra 1? Also, the vCenter Converter plugin is now showing the following error:

vCenter Converter
VMware, Inc.
4.2.1
Disabled
Converts physical and virtual machines, and backup images to VMware virtual machines.
The plug-in failed to load on server(s) 172.25.175.38 due to the following error:
Retrieving the COM class factory for component with CLSID {445530D4-3D51- 44FB-99A3-264F01EC1AE0} failed due to the following error: 80040154.

0 Kudos
a_p_
Leadership
Leadership

Is this a new setup? Are you running VMware View, which might use this port?

Btw. is the hyphen in "scr-iptConfig.xml" a typo?

André

0 Kudos
eoindubh
Contributor
Contributor

It is sort of new. Support had me reinstall vCenter a couple of months ago because of corruption of a couple of clusters. These pluging have not worked since and no the Converter plugin keeps quiting. I think that I will have to reinstall the whole thing again but it sure was a pain the last time. Just to get permission to do it is difficult as there are engineers somewhere in the world accessing it 24/7/365 so a window has to be scheduled.

0 Kudos
azhskr
Enthusiast
Enthusiast

I experienced this same problem after upgrading to vSphere 5.0.  The password was set properly as stated in the KB article linked earlier.  I stopped the vCenter services, copied the SSL files from a backup made before I upgraded and re-registered the rui.pfx.  Restarted the services and the plugins were once again working normally.

0 Kudos