[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: