Error loading plugin 4.2 for vCenter 5

[Shaymt]

Hi

I installed the new vSphere 5 on fresh windows 2008 R2 server

Also I successfully configured the Orchestrator 4.2

I tried start some basic built in workflow and when i try to open the vCenter tree i received plugin error

I configured additional vCenter 4.1 and this one fork fine

attach print screen of the error and of the configuration

do i have plugin missing ?

Thanks in advance

[Shaymt]

Hi again

I found the plugin for vcenter 5 in VMware Web site under driver and tools

I installed the plugin and i found the Virtual Center menu in the configuration web site changed to Virtual Center (5.0.0)

but when i click on it to change the vCenter configuration i receive the following error message:

Error occured
on http://localhost:8282/o11nplugin-vsphere50-config/Default.action?selectedMenu=VC
(12031 Unknown)

Any idea ??

[tschoergez]

Hi!

Usually installing the vCenter 5.0-Plugin should update the old one.

Can you try to restart the server-service and the configuration service, and try to install the plugin again?

Do you have some screenshots from the plugins-section in the configurator?

Regards,

Joerg

[FSvcoe]

I've run into the same issue, but with version 4.1 and for VUM..no luck on removing/reinstalling it thus far.

[CMitchell3]

I am getting the same results, has anyone found a solution for this?

[igorstoyanov]

Hi,

Not sure what might be the issue but the first step is to increase the memory used by the configurator. The procedure is described in the release notes of vCenter5.0 plug-in.

The second step is to delete the old plugin - ${Orchestrator-installation-path}/app-server/server/vmo/plugins/o11nplugin-vsphere41.dar.

The version 5.0 of the plugin is named differently app-server/server/vmo/plugins/o11nplugin-vsphere50.dar.

The problem might be caused by the VC plugin being to big and loaded twice because of the different names.

So delete the o11nplugin-vsphere41.dar and try to restart the Configurator and the vCO server

[FSvcoe]

Just wondering-you would remove the previous plugin and then reregister the new one. How would it load them twice?

[igorstoyanov]

Not sure I understood the question but removing the old plug-in and restarting the server should load only the new plug-in.

Thanks.

[FSvcoe]

Your post stated the plugin could somehow be loaded twice, consuming a large amount of memory, just wondering how that might occur. Thanks.