VMware vSphere Web Client reports an internal error 1009
search cancel

VMware vSphere Web Client reports an internal error 1009

book

Article ID: 345642

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:

  • Performing any operation in the vSphere Web Client fails with an internal error 1009.
  • In the vSphere_client_virgo.log file, you see entries similar to:

    [INFO ]http-bio-9443-exec-470000848 100013 200004 c.v.v.vim.data.adapters.search.impl.PropertyCollectorDataAdapter Object not found: ManagedObjectReference:type = VirtualMachine,value = vm-3309,serverGuid = 17D382FB-####-####-####-########961
    FilterSpec: [0]
    objectSet: [0]: VirtualMachine:vm-3309:17D382FB-####-####-####-########961
    propSet: [0]: [overallStatus, runtime.connectionState]
    [1]
    objectSet: [0]: VirtualMachine:vm-1058:17D382FB-####-####-####-########961
    propSet: [0]: [overallStatus, runtime.connectionState]
    [2]
    objectSet: [0]: VirtualMachine:vm-138:17D382FB-####-####-####-########961
    propSet: [0]: [overallStatus, runtime.connectionState]
    [3]
    objectSet: [0]: VirtualMachine:vm-1494:17D382FB-####-####-####-########961
    propSet: [0]: [overallStatus, runtime.connectionState]
    [4]
    objectSet: [0]: VirtualMachine:vm-425:17D382FB-####-####-####-########961
    propSet: [0]: [overallStatus, runtime.connectionState]

  • In the vpxd.log file, you see entries similar to:

    [06944 info 'commonvpxLro' opID=5a4a5af3] [VpxLRO] -- BEGIN task-internal-168981 -- -- vmodl.query.PropertyCollector.retrieveContents -- 1cf0d4a2-####-####-####-########a92(52d477e0-####-####-####-########80d)
    [06944 info 'commonvpxLro' opID=5a4a5af3] [VpxLRO] -- FINISH task-internal-168981 -- -- vmodl.query.PropertyCollector.retrieveContents --
    [06944 info 'Default' opID=5a4a5af3] [VpxLRO] -- ERROR task-internal-168981 -- -- vmodl.query.PropertyCollector.retrieveContents: vmodl.fault.ManagedObjectNotFound:
    --> Result:
    --> (vmodl.fault.ManagedObjectNotFound) {
    --> dynamicType = <unset>,
    --> faultCause = (vmodl.MethodFault) null,
    --> obj = 'vim.VirtualMachine:vm-3309',
    --> msg = "",
    --> }
    --> Args:
    -->

    Note
    : Similar entries are observed for all other virtual machine objects denoted in the vsphere_client_virgo.log file.



Environment

VMware vCenter Server 6.0.x
VMware vCenter Server 5.1.x
VMware vCenter Server 5.5.x

Cause

This issue occurs due to cached object IDs on vSphere Web Client for the logged in user.

For example, when a user logs in, accesses a virtual machine, the user data is cached in the corresponding user profile. The cached user details continue to exist even after you delete the user object.

Resolution

To resolve this issue, remove the files in the serenity database.

Important: Before attempting any of the steps below, make sure you have a recovery point prior to deleting or modifying any files. If the VMware vSphere Web Client is installed on a virtual machine or you are using the VMware vCenter Server Appliance, you may take a snapshot before proceeding.

To remove the files in the VMware vSphere Web Client serenity database:
  1. To remove the files in the serenity database, type these commands:

    For Windows vCenter Server 5.x:

    Use File Explorer to delete the contents of C:\programdata\vmware\vSphere Web Client\SerenityDB\serenity

    For Windows vCenter Server 6.0.x:

    Use File Explorer to delete the contents of C:\programdata\vmware\vCenterServer\data\vSphere Web Client\SerenityDB\serenity

    For the VMware vCenter Server Appliance 5.x:

    Type this command when logged in as root through a console shell or SSH session:

    rm -rf /etc/vmware-vsphere-client/SerenityDB/serenity/*

    For the VMware vCenter Server Appliance 6.0.x:

    Run this command when logged in as root through a console shell or SSH session:

    rm -rf /storage/vsphere-client/SerenityDB/serenity/*

Additional Information