Search the VMware Knowledge Base (KB)
View by Article ID

Inventory objects fail to display in vSphere Web Client 6.0 (2144934)

  • 47 Ratings

Symptoms

  • vSphere Web Client displays only few or no inventory objects under Host and Clusters after upgrading to vCenter Server 6.0
  • Browsing the inventory under Related Objects at multiple levels fail with the error:

    no object found
     

Note: For additional symptoms and log entries, see the Additional Information section. 

Purpose

When the Inventory objects fail to display in vSphere Web Client 6.0, restart vCenter Inventory Services to work around this issue.

Cause

This issue occurs due to caching within the Inventory Service.

Resolution

This issue is resolved in vCenter Server and vCenter Server Appliance 6.0 Update 2a, available at VMware Downloads. For more information, see VMware vCenter Server 6.0 Update 2a Release Notes.

To work around this issue, restart vCenter Inventory Services.

Additional Information

You experience these additional symptoms:
  • You are able to find the objects when you search using the Search function in the vSphere Web Client.
  • This issue does not occur in the vSphere Client.
  • In the authz-event.log file, you see entries similar to:

    2016-04-06T14:38:39.375+09:00 [tomcat-exec-81  INFO  AuthorizationService.AuditLog  opId=6765911c-7aeb-42c4-b066-c37d9505739c] Action performed by principal(name=VSPHERE.LOCAL\Administrator,isGroup=false):Added access control [ Principal=Name=Domain\user,isGroup=false,roles=[-1],propogating=true ] to document urn:vmomi:Folder:group:0e828d90-4eb9-4b08-925c-7395c79c3382
    2016-04-06T14:39:07.493+09:00 [tomcat-exec-182  INFO  AuthorizationService.AuditLog  opId=41ea82b7-34f8-4a92-9d50-7114eea55e05 IS] Action performed by principal(name=VSPHERE.LOCAL\Administrator,isGroup=false):Added access control [ Principal=Name=Domain\user,isGroup=false,roles=[-1],propogating=true ] to document urn:vmomi:Folder:group:0e828d90-4eb9-4b08-925c-7395c79c3382
    2016-04-06T14:39:25.637+09:00 [tomcat-exec-182  INFO  AuthorizationService.AuditLog  opId=41ea82b7-34f8-4a92-9d50-7114eea55e05 IS] Action performed by principal(name=VSPHERE.LOCAL\Administrator,isGroup=false):Added access control [ Principal=Name=Domain\user,isGroup=false,roles=[-1],propogating=true ] to document urn:vmomi:Folder:group:0e828d90-4eb9-4b08-925c-7395c79c3382 Add permission for folderA, folderB and folderC
    2016-04-06T14:41:44.634+09:00 [tomcat-exec-59  INFO  AuthorizationService.AuditLog  opId=41ea82b7-34f8-4a92-9d50-7114eea55e05 IS] Action performed by principal(name=VSPHERE.LOCAL\Administrator,isGroup=false):Remove access control for principals [ Name=Domain\user,isGroup=false ] on document urn:vmomi:Folder:group:0e828d90-4eb9-4b08-925c-7395c79c3382 Remove permission for folder

  • In the inv-svc.log file, you see entries similar to:

    2016-04-06T14:41:44.634+09:00 [tomcat-exec-59  INFO  com.vmware.cis.authorization.impl.AuthorizationManagerImpl  opId=41ea82b7-34f8-4a92-9d50-7114eea55e05 IS] Invalidating permission cache for principal:VSPHERE.LOCAL\Administrator
    2016-04-06T14:41:44.634+09:00 [tomcat-exec-59  INFO  com.vmware.cis.authorization.impl.AuthorizationManagerImpl  opId=41ea82b7-34f8-4a92-9d50-7114eea55e05 IS] Invalidating permission cache for principal:VSPHERE.LOCAL\vsphere-webclient-a1716610-fb7f-11e5-bc66-000c29823aed
    2016-04-06T14:41:44.634+09:00 [tomcat-exec-59  INFO  AuthorizationService.AuditLog  opId=41ea82b7-34f8-4a92-9d50-7114eea55e05 IS] Action performed by principal(name=VSPHERE.LOCAL\Administrator,isGroup=false):Remove access control for principals [ Name= Domain \ user ,isGroup=false ] on document urn:vmomi:Folder: group :0e828d90-4eb9-4b08-925c-7395c79c3382 Remove permission for folderC
    2016-04-06T14:41:53.127+09:00 [tomcat-exec-22  INFO  com.vmware.vim.vcauthenticate.servlets.AuthenticationServlet  opId=41ea82b7-34f8-4a92-9d50-7114eea55e05 IS] Received new logout request from 127.0.0.1
    2016-04-06T14:41:53.129+09:00 [VLSI-session-reaper  INFO  com.vmware.cis.authorization.impl.AuthorizationManagerImpl  opId=] Session count for user [after remove]: VSPHERE.LOCAL\Administrator is 1
    2016-04-06T14:41:53.565+09:00 [tomcat-exec-59  WARN  com.vmware.vim.vmomi.server.session.impl.SessionImpl  opId=41ea82b7-34f8-4a92-9d50-7114eea55e05 IS] closeSession called for 233C3CC5 with use count 2
    2016-04-06T14:41:53.569+09:00 [tomcat-exec-59  WARN  com.vmware.vim.vmomi.server.session.impl.SessionImpl  opId=41ea82b7-34f8-4a92-9d50-7114eea55e05 IS] closeSession called for BDF7246D with use count 2
    2016-04-06T14:41:53.569+09:00 [VLSI-session-reaper  INFO  com.vmware.cis.authorization.impl.AuthorizationManagerImpl  opId=] Removed user data for: VSPHERE.LOCAL\vsphere-webclient-a1716610-fb7f-11e5-bc66-000c29823aed
    2016-04-06T14:41:53.569+09:00 [VLSI-session-reaper  INFO  com.vmware.cis.authorization.impl.AuthorizationManagerImpl  opId=] Session count for user [after remove]: VSPHERE.LOCAL\vsphere-webclient-a1716610-fb7f-11e5-bc66-000c29823aed is 0
    2016-04-06T14:41:53.569+09:00 [VLSI-session-reaper  INFO  com.vmware.cis.authorization.impl.AuthorizationManagerImpl  opId=] Removed user data for: VSPHERE.LOCAL\Administrator
    2016-04-06T14:41:53.569+09:00 [VLSI-session-reaper  INFO  com.vmware.cis.authorization.impl.AuthorizationManagerImpl  opId=] Session count for user [after remove]: VSPHERE.LOCAL\Administrator is 0
    2016-04-06T14:42:11.525+09:00 [pool-17-thread-4  INFO  com.vmware.cis.authorization.impl.UserSessionManagerImpl  opId=] Auth data null in session. Returning false
    2016-04-06T14:42:11.537+09:00 [pool-16-thread-5  INFO  com.vmware.identity.token.impl.SamlTokenImpl  opId=96706bfd-5b60-4579-a0d9-8d5ce08d9ef6] SAML token for SubjectNameId [value=
    user@domain , format=http://schemas.xmlsoap.org/claims/UPN] successfully parsed from Element
    2016-04-06T14:42:11.541+09:00 [pool-16-thread-5  INFO  com.vmware.cis.authorization.impl.AuthorizationManagerImpl  opId=96706bfd-5b60-4579-a0d9-8d5ce08d9ef6] Session count for user [after add]:  Domain \ user  is 1
    2016-04-06T14:42:22.287+09:00 [tomcat-exec-59  INFO  com.vmware.identity.token.impl.SamlTokenImpl  opId=41ea82b7-34f8-4a92-9d50-7114eea55e05 IS] SAML token for SubjectNameId [value=
    user@domain , format=http://schemas.xmlsoap.org/claims/UPN] successfully parsed from XML
    2016-04-06T14:42:22.301+09:00 [tomcat-exec-59  INFO  com.vmware.identity.token.impl.SamlTokenImpl  opId=41ea82b7-34f8-4a92-9d50-7114eea55e05 IS] SAML token for SubjectNameId [value=
    user@domain , format=http://schemas.xmlsoap.org/claims/UPN] successfully parsed from XML
    2016-04-06T14:42:22.303+09:00 [tomcat-exec-59  INFO  com.vmware.cis.authorization.impl.AuthorizationManagerImpl  opId=41ea82b7-34f8-4a92-9d50-7114eea55e05 IS] Session count for user [after add]:  Domain \ user  is 2
    2016-04-06T14:42:22.307+09:00 [tomcat-exec-166  WARN  com.vmware.cis.authorization.impl.AclPrivilegeValidator  opId=41ea82b7-34f8-4a92-9d50-7114eea55e05 IS] User  Domain \ user  does not have privileges [System.View] on object urn%3Avmomi%3AFolder%3Agroup-d1%3A0e828d90-4eb9-4b08-925c-7395c79c3382 User  Domain \ user  does not have privileges for group 

    Note : This log excerpt is an example. Date, time, and environmental variables may vary depending on your environment.

Tags

no object found, inventory object failure, Inventory Service, vSphere Web Client objects

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 47 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 47 Ratings
Actions
KB: