After installing or upgrading to vCenter Server 6.0 on Windows, you may notice the following issues:

  • vAPI Endpoint Service Health Alarm keeps triggering in vCenter Server for Windows
  • “You do not have permissions to view this object or this object does not exist” messages when using vSphere Web Client

Review the %ProgramData%\VMware\vCenterServer\runtime\VMwareSTSService\logs\lookupserver.log for entries like:

  • Unable to load library ‘vmafdclient’: The specified module could not be found
  • Could not initialize class com.vmware.af.interop.VmAfClientAdapter$VmAfClientLibrary

Review the %ProgramData%\VMware\vCenterServer\logs\vapi\endpoint\endpoint.log for entries like:

  • ComponentManagerClientWrapper | Service lookup failed
  • java.util.concurrent.ExecutionException

Cause

This issue occurs when the Local System user overrides the Local Machine’s Path registry key and prevents the VMware Secure Token Service (STS) from starting properly.

Resolution

  • Start regedit.exe on the vCenter server
  • Navigate to HKEY_USERS\S-1-5-18\Environment
  • Right click the Path value and select Modify
  • Append c:\Program Files\MIT\Kerberos\bin to the value (for example C:\Windows\System32;c:\Program Files\MIT\Kerberos\bin)
  • Click OK
  • Restart the vCenter server