Error #1009 vSphere Web Client

Recently I have been having some issues with plugins while working in my lab.  I recently wrote this article “Error 1063 vSphere Web Client” which documents how to disable selected plugins.  This fixed worked for a little while, but recently I have started receving a similar error but with the Error #1009 vSphere Web Client.  I tried the fix in my previous article again, however when I tried to go into the Client Plug-Ins area of the vSphere Web Client, I received the #1009 error everytime.

Error #1009 vSphere Web Client

The first thing I tried was to (obviously) Google the error, but I couldn’t find any resolution.  A few people have experienced this error on the communities forum but no one had a fix for it.  I phoned a friend in GSS, and they told me about an issue with cached objects that are stored in a SerenityDB folder.  They aparantly have bad references and you need to clear out the cache.

After running the steps below, this error has now stopped appearing and I can continue with my daily activities in the vSphere Web Client.

Run these steps if you are using the VMware vCenter Server Appliance 5.5 or version 6.0 to clear the Error #1009 vSphere Web Client.
Login to the vCenter Server Appliance using SSH or the console:

# service vsphere-client stop
# rm -rf /etc/vmware-vsphere-client/SerenityDB/serenity/*
# service vsphere-client start

You will then see the following status:


Last login: Fri Jun 5 11:24:36 UTC 2015 on pts/0
Starting VMware vSphere Web Client...
Waiting for VMware vSphere Web Client......
running: PID:8765

This tells you that the vSphere Web Client is now running and started. You will need to wait a few minutes for the service to fully initiate. If you try to login too soon you will see the following message in your browser:

Error #1009 vSphere Web ClientThats it.  You should be fully working and no more annoying errors appearing.

, , , ,

5 Responses to Error #1009 vSphere Web Client

  1. Edwin Matos June 9, 2015 at 9:26 pm #

    Pretty good information this worked for me but using the windows version of vSphere Client.

    Path on windows is located on C:\ProgramData\VMware\vSphere Web Client\SerenityDB\serenity

  2. Mike Laak July 18, 2015 at 9:55 pm #

    Thanks for the tip David.

    I found in the latest VCSA the files were located in /storage/vsphere-client/SerenityDB/serenity/

  3. Ramesh August 18, 2015 at 1:55 pm #

    David,

    I am still getting the error #1009 even after following your procedure mentioned here. I need your help.

    I created more vSwitches, but it is not listing in the available network adaptors. When I click show more network i get the Error #1009 with the following stack trace:

    Error Stack
    ———————
    TypeError: Error #1009
    at com.vmware.vsphere.client.commands.network::NetworkSelectorCommand/onPropertyRequest()
    at com.vmware.frinje::CommandRegistry/invokeRequestHandler()
    at com.vmware.frinje::CommandRegistry/execute()
    at com.vmware.frinje::CommandRegistry/onCommandRequest()
    at flash.events::EventDispatcher/dispatchEvent()
    at com.vmware.frinje::EventBus/dispatchEvent()
    at com.vmware.actionsfw.implementation::ActionWrapper/invokeInternal()
    at com.vmware.actionsfw.implementation::ActionWrapper/onCommandObjectLoaded()
    at com.vmware.extensionfw::CallbackUtil$/callback()
    at com.vmware.extensionfw::ExtensionManager/onObjectCreated()
    at com.vmware.extensionfw::CallbackUtil$/callback()
    at com.vmware.extensionfw::ExtensionObjectParser/onObjectDeserialized()
    at com.vmware.flexutil::MxmlDeserializer/onThreadTerminated()
    at flash.events::EventDispatcher/dispatchEvent()
    at com.vmware.flexutil::PseudoThread/terminate()
    at com.vmware.flexutil::PseudoThread/onTimer()
    at com.vmware.flexutil::PseudoThread/start()
    at com.vmware.flexutil::MxmlDeserializer/xmlToObjectAsync()
    at com.vmware.extensionfw::ExtensionObjectParser/parse()
    at com.vmware.extensionfw::ExtensionManager/createObjectInternal()
    at com.vmware.extensionfw::ExtensionManager/onResourceModulesLoaded()
    at com.vmware.extensionfw::MiscUtil$/loadResourceModules()
    at com.vmware.extensionfw::ExtensionManager/createObject()
    at com.vmware.actionsfw.implementation::ActionWrapper/invokeInternal()
    at com.vmware.actionsfw.implementation::ActionWrapper/onConfirmationReturned()
    at com.vmware.actionsfw.implementation::AFUtil$/showConfirmation()
    at com.vmware.actionsfw.implementation::AFUtil$/defaultConfirmation()
    at com.vmware.actionsfw.implementation::ActionWrapper/invoke()
    at com.vmware.vsphere.client.events.network::NetworkSelectorProxy/onActionReturn()
    at EventFunctor/notifyTarget()
    at EventFunctor/onEvent()
    at flash.events::EventDispatcher/dispatchEvent()
    at com.vmware.frinje::EventBus/dispatchEvent()
    at com.vmware.frinje::EventBus/onEvent()
    at flash.events::EventDispatcher/dispatchEvent()
    at com.vmware.actionsfw.commands::ActionsRequestCommand/dispatchRequestedActions()
    at com.vmware.actionsfw.implementation::ActionFramework/onAvailabilityCalculated()
    at StandardContextCalculation/reportEvaluated()
    at StandardContextCalculation/calculateAvailability()
    at com.vmware.actionsfw.implementation::ActionFramework/processPendingActionsRequest()
    at com.vmware.actionsfw.implementation::ActionFramework/onRelevanceCalculated()
    at StandardContextCalculation/reportPopulated()
    at StandardContextCalculation/relevanceCallback()
    at com.vmware.actionsfw.implementation::ActionWrapper/reportRelevanceResult()
    at com.vmware.actionsfw.implementation::ActionWrapper/onRelevanceKnown()
    at com.vmware.actionsfw.implementation::ActionWrapper/checkRelevance()
    at com.vmware.actionsfw.implementation::ActionWrapper/evaluateRelevance()
    at StandardContextCalculation/populateRelevantActions()
    at StandardContextCalculation/onDynamicActionsLoaded()
    at com.vmware.actionsfw.implementation::DynamicActionsLoader/actionsExtensionCallback()
    at com.vmware.actionsfw.implementation::DynamicActionsLoader/getDynamicActionsForActionSets()
    at StandardContextCalculation/processActionSets()
    at StandardContextCalculation/actionsExtensionCallback()
    at com.vmware.extensionfw::CallbackUtil$/callback()
    at com.vmware.extensionfw::ExtensionManager/onExtensionObjectsCreated()
    at com.vmware.extensionfw::CallbackUtil$/callback()
    at ObjectsCreator/onObjectCreated()
    at com.vmware.extensionfw::CallbackUtil$/callback()
    at com.vmware.extensionfw::ExtensionObjectParser/onObjectDeserialized()
    at com.vmware.flexutil::MxmlDeserializer/onThreadTerminated()
    at flash.events::EventDispatcher/dispatchEvent()
    at com.vmware.flexutil::PseudoThread/terminate()
    at com.vmware.flexutil::PseudoThread/onTimer()
    at com.vmware.flexutil::PseudoThread/start()

  4. Matt October 20, 2015 at 10:54 am #

    David, you’re a life saver! I’ve been putting up with the error for a while now and it’s been driving me mad. I renamed serenity folder to serenity.old just in case, and it’s been stable now through a bunch of NSX dialogs for the past hour.

  5. RD January 2, 2018 at 1:27 am #

    Hi David,

    Can i stop the service while there are VMs running?

    Thanks
    RD

Leave a Reply

Copyright David Hill Group Limited

Powered by WordPress. Designed by Woo Themes

%d bloggers like this: