Viewing virtual machine summary using the vSphere Web Client fails with the Error #1009

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:
In a VMware vSphere 6.0 Update 2 environment, you experience these symptoms:

• Viewing virtual machine summary using the vSphere Web Client fails.
• You see the error:
  
  TypeError: Error #1009
  at com.vmware.ui.error::ErrorNotificationManager/onPlatformReportedError()
  at flash.events::EventDispatcher/dispatchEvent()
  at com.vmware.frinje::EventBus/notifyContainedErrorIfApplicable()
  at com.vmware.frinje::EventBus/postprocess()
  at com.vmware.frinje::EventBus/dispatchEvent()
  at com.vmware.frinje::EventBus/onEvent()
  at flash.events::EventDispatcher/dispatchEvent()
  at com.vmware.data.query.commands::DataRequestCommand/onSingleEntityDataReturn()
  at DataAccessItem/notify()
  at DataAccessItem/handleResult()
  at DataAccessItem/processResult()
  at com.vmware.data.query::DataAccessManager/onDataRetrieved()
  at com.vmware.flexutil.proxies::BaseProxy/notify()
  at com.vmware.flexutil.proxies::BaseProxy/result()
  at com.vmware.flexutil.proxies::BaseProxy/onInvocationComplete()
  at OperationInvoker/resultResponseForRequest()
  at OperationInvoker/result()
  at mx.rpc::AsyncToken/http://www.adobe.com/2006/flex/mx/internal::applyResult()
  at mx.rpc.events::ResultEvent/http://www.adobe.com/2006/flex/mx/internal::callTokenResponders()
  at mx.rpc::AbstractOperation/http://www.adobe.com/2006/flex/mx/internal::dispatchRpcEvent()
  at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::resultHandler()
  at mx.rpc::Responder/result()
  at mx.rpc::AsyncRequest/acknowledge()
  at NetConnectionMessageResponder/resultHandler()
  at mx.messaging::MessageResponder/result()"'
  
  Note: For additional symptoms, see the Additional Information section.

Cause

This issue occurs due to the error related to a NULL pointer exception that was not handled properly in the User Interface (UI).

Resolution

This issue is resolved in VMware vSphere 6.0 Update 3, available at VMware Downloads.

Additional Information

In the vsphere_client_virgo.log, you see these errors similar to:

[2017-01-11T13:08:29.538-07:00] [INFO ] data-service-pool-962 70000206 100013 200002 com.vmware.vise.vim.security.util.VCAuthorizationUtil Server 2daca9c4-f55d-42b2-b49d-99cf12a54d07 version detected: 6.0.0
[2017-01-11T13:08:29.538-07:00] [INFO ] data-service-pool-962 70000206 100013 200002 com.vmware.vise.vim.security.util.VCAuthorizationUtil Assuming AuthZ permission for server with GUID '2daca9c4-f55d-42b2-b49d-99cf
[2017-01-11T13:08:29.790-07:00] [ERROR] pbm-service-thread-pool-1043 70000206 100013 200002 com.vmware.vise.vim.commons.vmomi.response.ResultInterceptorImpl Operation PbmComplianceManager#fetchRollupComplianceResult failed. opId=f646
[2017-01-11T13:08:29.817-07:00] [ERROR] data-service-pool-964 70000206 100013 200002 com.vmware.vsphere.client.spbm.util.PbmUtil Failed to retrieve VmRollupComplianceSummay: java.util.concurrent.Execution
faultCause = null,
faultMessage = null
}
at com.vmware.vim.vmomi.core.impl.BlockingFuture.get(BlockingFuture.java:70)
at com.vmware.vsphere.client.spbm.util.PbmUtil.getVmRollupComplianceSummay(PbmUtil.java:702)
at com.vmware.vsphere.client.spbm.impl.PbmPropertyProvider.getVmRollupComplianceSummay(PbmPropertyProvider.java:907)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)

Notes:

• The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
• Log location :
  
  • Appliance: /var/log/vmware/vsphere-client/logs/
  • Windows: %ALLUSERSPROFILE%\VMWare\vCenterServer\logs\vsphere-client\logs

Impact/Risks: