Error: "You do not have permissions to view this object or this object does not exist" in vSphere Web Client
search cancel

Error: "You do not have permissions to view this object or this object does not exist" in vSphere Web Client

book

Article ID: 335971

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

The issue of vSphere Web Client failing to login is a known issue affecting VMware vCenter Server 6.0.

 


Symptoms:
After installing or upgrading to vCenter Server 6.0 on Windows, you experience these symptoms:
  • Logging in to the vSphere Web Client fails.
  •  
  • While replacing the Machine SSL certificate, we see error in the certificate-manager.log,

    YYYY-MM-DDTHH:MM:SS.XZ INFO certificate-manager MACHINE_SSL_CERT certificate replaced successfully. SerialNumber and Thumbprint changed.
    YYYY-MM-DDTHH:MM:SS.XZ ERROR certificate-manager Error while replacing Machine SSL Cert, please see C:\ProgramData\VMware\vCenterServer\logs\vmca\certificate-manager.log for more information.
    YYYY-MM-DDTHH:MM:SS.XZ ERROR certificate-manager 'lstool list' failed:

     
  • You see the error:

    You do not have permissions to view this object or this object does not exist
     
  • In the %ProgramData%\VMware\vCenterServer\runtime\VMwareSTSService\logs\lookupServer.log file on the Platform Services Controller, you see entries similar to:
[YYYY-MM-DDTHH:MM:SS:MS-04:00 pool-2-thread-1 ERROR com.vmware.vim.lookup.vlsi.util.VmodlEnhancer] Unable to load library 'vmafdclient': The specified module could not be found.
java.lang.UnsatisfiedLinkError: Unable to load library 'vmafdclient': The specified module could not be found.

...
 
[YYYY-MM-DDTHH:MM:SS:MS-04:00 pool-7-thread-1 ERROR com.vmware.vim.vmomi.server.impl.SoapBindingImpl] Method 'list' completed with undeclared fault of type 'LookupFaultServiceFault'
(lookup.fault.ServiceFault) {
faultCause = null,
faultMessage = null,
errorMessage = Unable to load library 'vmafdclient': The specified module could not be found.

...

[YYYY-MM-DDTHH:MM:SS:MS-04:00 pool-2-thread-1 INFO com.vmware.vim.lookup.vlsi.VlsiSecurityChecker] Operation create is permitted for user {Name: machine-6b018b31-b0fb-11e3-a918-0050569817d1, Domain: vsphere.local}

...

[YYYY-MM-DDTHH:MM:SS:MS-04:00 pool-2-thread-1 ERROR com.vmware.vim.lookup.vlsi.util.VmodlEnhancer] Could not initialize class com.vmware.af.interop.VmAfClientAdapter$VmAfClientLibrary
java.lang.NoClassDefFoundError: Could not initialize class
com.vmware.af.interop.VmAfClientAdapter$VmAfClientLibrary
  • In the %ProgramData%\VMware\vCenterServer\logs\vapi\endpoint\endpoint.log file on the vCenter Server, you see entries similar to:
YYYY-MM-DDTHH:MM:SS:MS-04:00 | ERROR | state-manager1 | ComponentManagerClientWrapper | Service lookup failed.
java.util.concurrent.ExecutionException: (cis.cm.fault.ComponentManagerFault) {
  • In the %ProgramData%\VMware\vCenterServer\logs\cm\cm.log file on the Platform Services Controller, you see entries similar to:
YYYY-MM-DDTHH:MM:SS:MS-04:00 [pool-14-thread-1 WARN com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore (46db3ac0-a783-422a-a8cf-ec9b7d19ba85)] Call to lookup service failed; uri:https://<Platform_Services_Controller_FQDN>/lookupservice/sdk [(vmodl.fault.SystemError) {
faultCause = null,
faultMessage = null,
reason = Invalid fault
}]
YYYY-MM-DDTHH:MM:SS:MS-04:00 [pool-14-thread-1 ERROR com.vmware.cis.services.cm.service.ServiceManagerImplTemplate (46db3ac0-a783-422a-a8cf-ec9b7d19ba85)] search v1: Failed to search
(vmodl.fault.SystemError) {
faultCause = null,
faultMessage = null,
reason = Invalid fault

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.


Environment

VMware vCenter Server 6.0.x

Cause

This issue occurs when the local system user overrides the Path registry key of the local machine and prevents the VMware Secure Token Service (STS) from starting properly.

Resolution

This is a known issue affecting VMware vCenter Server 6.0.
 
Currently, there is no resolution.
 
To workaround this issue, use any one of these options:
  • Rename the Path Registry Key

    Note: Use this method if you do not need this Path registry key for the local system and can use the system wide path from local machine, you can remove this path.
     
  • Include Addition Values to the Path Registry Key

    Note: Use this method if you require the local system Path registry to remain unique for you windows system.
 
Renaming the Path Registry Key (Simple)
 
If you do not need this Path registry key for the local system and you can use the system wide path from Local Machine.

Note: This procedure modifies the Windows registry. Before making any registry modifications, ensure that you have a current and valid backup of the registry and the virtual machine. For more information on backing up and restoring the registry, see the Microsoft Knowledge Base article 136393.
  1. Connect to the external Platform Services Controller or the vCenter Server with Embedded Platform Services Controller remotely as a local administrator.
  2. Click Start > Run, type regedit, and click OK. The registry editor window opens.
  3. Navigate to the Environment registry key for Local System:

    HKEY_USERS\S-1-5-18\Environment
     
  4. Right-click on Path and select Rename.
  5. Set the name of the registry key to Old_Path.
  6. Restart vCenter Server.
 
Including Addition Values to the Path Registry Key (Advanced)
 
If you require the Local System Path registry to remain unique for your Windows system.

Note: This procedure modifies the Windows registry. Before making any registry modifications, ensure that you have a current and valid backup of the registry and the virtual machine. For more information on backing up and restoring the registry, see the Microsoft Knowledge Base article 136393.
  1. Connect to the external Platform Services Controller or the vCenter Server with Embedded Platform Services Controller remotely as a local administrator.
  2. Click Start > Run, type regedit, and click OK. The registry editor window opens.
  3. Navigate to the path registry key for local machine:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
     
  4. Right-click Path and click Modify.
  5. Locate and copy the MIT\kerberos path contained with the key.

    By default, MIT\kerberos path should be:

    c:\Program Files\MIT\Kerberos\bin
     
  6. Navigate to the Environment registry key for Local System:

    HKEY_USERS\S-1-5-18\Environment
     
  7. Right-click Path and click Modify.
  8. Append the the MIT\kerberos path from Step 5 to the registry key's Value data field.

    Use this as a model:

    C:\Program Files\System Center Operations Manager 2007;c:\Program Files\MIT\Kerberos\bin
     
  9. Click OK.
  10. Restart the vCenter Server.
 
Note: The preceding links were correct of June 15, 2016. If you find a link in broken provide a feedback and a VMware employee will update the link.


Additional Information