vSphere Web Client Displays Error #1009 in vCenter Server 5.1, 5.5 and 6.0

 

Error 1009 in vSphere Web Client

 

An error that frequently comes up in the vSphere Web Client is Error 1009. This issue occurs in vCenter Server 5.1, 5.5, and 6.0 when navigating through inventory. Typically when this error message pops up you have to refresh your entire session. This issue is almost always caused by cached objects with bad references. 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.
 
In order to resolve this issue, you will need to clear the cache by performing the following steps.
 
Note: It’s always best practice to backup these folders before deleting them.
 

Windows based vCenter Server 5.x

Step 1. Stop the vSphere Web Client Service
 
Step 2. Delete the contents of the folders below.
 
C:\programdata\vmware\vSphere Web Client\SerenityDB\serenity
 
Step 3. Start the vSphere Web Client Service
 

Windows based vCenter Server 6.x

Step 1. Stop the vSphere Web Client Service

# cd C:\Program Files\VMware\vCenter Server\bin
# service-control --stop vspherewebclientsvc

Step 2. Delete the contents of the folders below.
 
C:\programdata\vmware\vCenterServer\data\vSphere Web Client\SerenityDB\serenity
 
Step 3. Start the vSphere Web Client Service

service-control --start vspherewebclientsvc 

 

vCenter Server Appliance 5.x

Step 1. Stop the vSphere Web Client Service

# service vsphere-client stop

Step 2. Remove the Contents

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

Step 3. Start the vSphere Web Client Service

# service vsphere-client start

 

vCenter Server Appliance 6.x

Step 1. Stop the vSphere Web Client Service

# service vsphere-client stop

Step 2. Remove the Contents

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

Step 3. Start the vSphere Web Client Service

# service vsphere-client start

 

Posted by:

Sean Whitney

8 Comments

  1. Newsletter: March 28, 2015 | Notes from MWhite -  April 4, 2015 - 9:12 am 74

    […] error in my labs, but I have seen it elsewhere and I was not sure how to fix it!  But the info is here so if you see Error 1009 when working in the Web Client you can solve the issue without a call to […]

    Reply
  2. Newsletter: April 4, 2015 | Notes from MWhite -  April 4, 2015 - 3:19 pm 76

    […] last week – sorry about that.  And I had this problem this week too.  Here is the correct link for this issue.  Important to note that the solution works in 5.x and 6.x […]

    Reply
  3. Newsletter: April 12, 2015 | Notes from MWhite -  April 12, 2015 - 2:21 pm 84

    […] 1009 errors I had many months with no 1009 issues. Then I had a few. So I used the process from the article that had me fix the 1009 issue. After that it was a disaster. I could last maybe 3 minutes in the […]

    Reply
  4. Berned M -  May 18, 2015 - 3:57 pm 103

    Had an issue with a VCSA 5.5 web client plug in failing for an RCCMD plug in that was working fine in the c# client, followed the steps above then it worked in the web client with no issues.

    Reply
  5. Robert Tate -  August 5, 2015 - 11:19 am 222

    Thanks for this. I have this error constantly and I am trying to find a long term resolution.

    FYI: There is an article on the VMware knowledge base on this issue: http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2101256&sliceId=1&docTypeID=DT_KB_1_1&dialogID=717660892&stateId=0 0 717688260

    However, for vCenter 5.5, there is no official fix other than reinstall the web server, which is not really a good option.

    Reply
    • Sean Whitney -  August 15, 2015 - 8:22 am 230

      Hi Robert,

      You’re welcome, thanks for the information as well. There may be other fixes, the #1009 error can be a series of things, but this resolution seems to encompass the majority of the problems.

      Thanks,
      Sean

      Reply
  6. Robert Tate -  September 24, 2015 - 3:47 pm 261

    I just ran into another web error (#1057) in which the folder delete works.

    FYI: As long as the user you need to “fix” is not logged into the web client, you can delete their folder without restarting the Web Server.

    Reply
    • Sean Whitney -  September 28, 2015 - 7:18 pm 267

      Hi Robert,

      Correct, thanks for the information!

      Sean

      Reply

Leave A Comment

Your email address will not be published. Required fields are marked (required):

Back to Top