Error #1009 when opening Client Plug-Ins on vSphere Web Client.

[LowRes]

I am using vCenter Web Client with vCenter 5.5. I recently installed the Dell OpenManage Essentials Plugin for VMware Integration. The plugin itself seems to be working correctly (it appears on the Home screen, and I can access the configuration options). However when I navigate to Administration->Solutions->Client Plug-Ins I am given this error:

An internal error has occurred - Error #1009.

Reloading the client is recommended, so as to clear any problems left by this error.

Click Yes to reload the vSphere Web Client?

When clicking "Show error stack..." I am given this:

Error Stack

---------------------

TypeError: Error #1009

  at com.vmware.vsphere.client.views.admin::PluginManagementViewMediator/processPlugins()

  at com.vmware.vsphere.client.views.admin::PluginManagementViewMediator/updateUi()

  at com.vmware.vsphere.client.views.admin::PluginManagementViewMediator/onDisabledPluginPackagesRetrieved()

  at com.vmware.extensionfw::CallbackUtil$/callback()

  at com.vmware.extensionfw::ExtensionServiceProxy/notify()

  at com.vmware.flexutil.proxies::BaseProxy/fault()

  at com.vmware.flexutil.proxies::BaseProxy/onInvocationComplete()

  at OperationInvoker/faultResponseForRequest()

  at OperationInvoker/fault()

  at mx.rpc::AsyncToken/http://www.adobe.com/2006/flex/mx/internal::applyFault()

  at mx.rpc.events::FaultEvent/http://www.adobe.com/2006/flex/mx/internal::callTokenResponders()

  at mx.rpc::AbstractOperation/http://www.adobe.com/2006/flex/mx/internal::dispatchRpcEvent()

  at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::faultHandler()

  at mx.rpc::Responder/fault()

  at mx.rpc::AsyncRequest/fault()

  at NetConnectionMessageResponder/statusHandler()

  at mx.messaging::MessageResponder/status()

I have restarted vCenter but it did not resolve the issue. I have not attempted to unregister the plugin from vCenter yet.

[ZackGregory]

If you log in to the Thick Client(vSphere Client) and go to the plugins button at the top, and then Manage Plug-ins... do you get the same error? When you get this error, are you able to continue working in the web client or does it kick you out of the Web Client?

Also, what plugins are you using if you do not get that error in the thick client.

[DBNSOG]

I am experiencing the exact same issue after resetting the embedded db on the vcenter appliance. Anyone find a solution to this issue yet? I have tried disabling every plugin from the windows client and relaunching the web client but the same error still occurs. There were several orphaned extensions from before the db reset but they do no show up in the MOB page to remove or update. Even after reconfiguring every plugin that previously existed i'm still getting this error on the web client.

[vThinkBeyondVM]

Can you please let me know exact steps that you performed? I will try to reproduce the same.

As per me, UI workflow is leading Null pointer exception on specific steps that you performed. Error #1009 is generic error message, only difference would be in error stack.

[DBNSOG]

I had a couple months of the vcenter appliance either failing to load the web ui, failing sso auth or just being so slow it was unusable. All of these issues were resolved temporarily by rebooting or restarting services. Then the inventory service started failing. I reset the DB, and rebuilt my vcenter config from scratch. After this everything started working much better, all my plugins are working, but if I try to browse to the plugins page of the webclient I get this

TypeError: Error #1009

at com.vmware.vsphere.client.views.admin::PluginManagementViewMediator/processPlugins()

at com.vmware.vsphere.client.views.admin::PluginManagementViewMediator/updateUi()

at com.vmware.vsphere.client.views.admin::PluginManagementViewMediator/onDisabledPluginPackagesRetrieved()

at com.vmware.extensionfw::CallbackUtil$/callback()

at com.vmware.extensionfw::ExtensionServiceProxy/notify()

at com.vmware.flexutil.proxies::BaseProxy/fault()

at com.vmware.flexutil.proxies::BaseProxy/onInvocationComplete()

at OperationInvoker/faultResponseForRequest()

at OperationInvoker/fault()

at mx.rpc::AsyncToken/https://urldefense.proofpoint.com/v1/url?u=http://www.adobe.com/2006/flex/mx/internal::applyFault%28%29&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=FGyPC8ZSvBkKihkoeKgCmjuZI2qYJ8xvSchS1aM1v%2Fc%3D%0A&m=7c2BCNkLS0shdL%2BV9AQgw0kWItjy%2FDfgeAzV2cXruSk%3D%0A&s=cf89d2c5a2430a2fbc09196cf0ffd91395f5fda6ed99f0a43fd2f8e651d75a74

at mx.rpc.events::FaultEvent/https://urldefense.proofpoint.com/v1/url?u=http://www.adobe.com/2006/flex/mx/internal::callTokenResponders%28%29&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=FGyPC8ZSvBkKihkoeKgCmjuZI2qYJ8xvSchS1aM1v%2Fc%3D%0A&m=7c2BCNkLS0shdL%2BV9AQgw0kWItjy%2FDfgeAzV2cXruSk%3D%0A&s=c46b9ff003fbcb32f716ed9edbcf17339fbff0f249328c2e1fd04387c7076aee

at mx.rpc::AbstractOperation/https://urldefense.proofpoint.com/v1/url?u=http://www.adobe.com/2006/flex/mx/internal::dispatchRpcEvent%28%29&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=FGyPC8ZSvBkKihkoeKgCmjuZI2qYJ8xvSchS1aM1v%2Fc%3D%0A&m=7c2BCNkLS0shdL%2BV9AQgw0kWItjy%2FDfgeAzV2cXruSk%3D%0A&s=a717e28e5cc19579fa66a392be6e321c89036726dc0e4ff78ce053e42141bc79

at mx.rpc::AbstractInvoker/https://urldefense.proofpoint.com/v1/url?u=http://www.adobe.com/2006/flex/mx/internal::faultHandler%28%29&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=FGyPC8ZSvBkKihkoeKgCmjuZI2qYJ8xvSchS1aM1v%2Fc%3D%0A&m=7c2BCNkLS0shdL%2BV9AQgw0kWItjy%2FDfgeAzV2cXruSk%3D%0A&s=a6aa32b7555c0357b14d5c52bebdd18a77724b84239af9d917df0891b2bf45da

at mx.rpc::Responder/fault()

at mx.rpc::AsyncRequest/fault()

at NetConnectionMessageResponder/statusHandler()

at mx.messaging::MessageResponder/status()

[vThinkBeyondVM]

Hi LowRes,

Can you please provide exact step for this issue? I also suggest if possible, can you please file support request with VMware?

[Bleeder]

Check if you have leftover plugin folders in C:\ProgramData\VMware\vSphere Web Client\vc-packages\vsphere-client-serenity\

It seems that some vendors are not clearing this out when uninstalling/unregistering their web client plugins    For example:

https://sort.symantec.com/public/documents/vom/6.1/windowsandunix/productguides/html/Rel_Notes/ch04s...

There may also be plugin state information (perhaps whether a plugin was previously disabled thru the web client) cached in the file "C:\ProgramData\VMware\vSphere Web Client\SerenityDB\serenity\ALL\client.package.states".   You can try renaming/deleting it.

PS - Sorry, this is all in relation to vCenter running on Windows.

[Ted_O_]

This worked for me!  Thanks!!!

[TProm]

I thank, it helped me!

[Chadwickles]

I have this exact same issue, error stack messages and all.  Only, I'm using the vCenter Server Appliance with an embedded db, not Windows, so I can't navigate to that path and delete any leftover plugin files.  I'm on version 5.5.0.20100, Build 2170515.  I'm suspecting this is a result of disabling either a.) a Pure Storage Web Client plugin or b.) an older EMC Networker client plugin.  They have both been disabled for a while, but I've just now noticed I cannot access the Client Plugin page.

Anyone know a fix for this?  I've tried rebooting the entire server appliance to no avail.  When I go to /mob, I don't even see the older EMC Networker client plugin listed.  I do however see the newer version along with the Pure Storage plugin listed.

Thanks!

[Chadwickles]

Actually, I figured it out.  It was our old Networker client-plugin causing the problem, as I suspected.  It never removed its old package and line from the client.package.states file, which was causing it to bomb when accessing that page.

First, either ssh in to your vCenter Server Appliance using PuTTY, Terminal on Mac, WinSCP, whatever.

Then, navigate to /etc/vmware-vsphere-client/SerenityDB/serenity/ALL and mv / rename the client.package.states file to something like client.package.states.old.  Hard reload the vCSA client in the browser - you should then be able to access the Client Plugins page and see all of your plugins listed there as normal, but any you had disabled are now back in the enabled state.  So, disable them again and reload the client again.  This worked for me. 

For future reference, the vc-packages path when using vCSA and embedded database is: /var/lib/vmware/vsphere-client/vc-packages/vsphere-client-serenity

Disclaimer! Obviously, be careful editing any file on your vCSA, you never know what may happen.

[Nodnarb]

Worked for me as well when trying to clean up old versions of HP OneView for vCenter. Thanks!

[davidhill]

I have found that these two articles really helped.

http://www.davidhill.co/2015/06/error-1009-vsphere-web-client/

Error 1063 vSphere Web Client - DavidHill.co

[johandijkstra]

We are experiencing the same problem with vCenter 6.0 explicitly for vSAN.

Tried some things mentioned here, but without succes.