Don't submit links to blogspam or other low-quality content. Spammers will be banned this sub will not become a marketing cesspit for vendors. Off-topic posts may be locked or removed. Keep post submissions relevant to VMware. Support requests involving Mac OS on unsupported hardware (not a Mac) or software (VMware Workstation or VMware Player) will be removed, and will result in a ban. This includes discussion of 'unlocker' or other methods used to violate the Mac OS EULA by running Mac OS on non-Apple hardware. Expect posts facilitating or promoting piracy to be removed. Step 3.Have a technical question? Just make a self post!ĭiscussion of piracy methods will not be permitted. # rm -rf /storage/vsphere-client/SerenityDB/serenity/* # rm -rf /etc/vmware-vsphere-client/SerenityDB/serenity/* Service-control -start vspherewebclientsvc # service-control -stop vspherewebclientsvcĬ:\programdata\vmware\vCenterServer\data\vSphere Web Client\SerenityDB\serenity
# cd C:\Program Files\VMware\vCenter Server\bin Delete the contents of the folders below.Ĭ:\programdata\vmware\vSphere Web Client\SerenityDB\serenity Note: It’s always best practice to backup these folders before deleting them. In order to resolve this issue, you will need to clear the cache by performing the following steps.
These cached objects are stored in the SerenityDB folder under the users name, if by chance any of the cached objects are deleted, but the cache still exists, you get bad Object ID references which will crash the web client.
This issue is almost always caused by cached objects with bad references. Typically when this error message pops up you have to refresh your entire session. This issue occurs in vCenter Server 5.1, 5.5, and 6.0 when navigating through inventory. Maby: Sean Whitney in: Troubleshooting 8 CommentsĪn error that frequently comes up in the vSphere Web Client is Error 1009.
0 kommentar(er)
