"Could not execute Online health checks" in Skyline Health in vCenter 7.0 Update 3d and vCenter 6.7 pre Update 3r
search cancel

"Could not execute Online health checks" in Skyline Health in vCenter 7.0 Update 3d and vCenter 6.7 pre Update 3r

book

Article ID: 318568

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

This article describes a specific issue in vCenter Server 7.0 Update 3d and vCenter Server 6.7 pre-Update 3r
Should you experience a problem looking similar to what is described above, while using a version of vCenter Server not mentioned in this article, please contact the VMware Support by opening a support request using the VMware CustomerConnect portal.

Symptoms:
  • After updating vCenter Server to 7.0.3 Update 3d the Skyline Health tab in vSphere Client shows an error "Unable to query vSphere health information", similar to the example below:
image.png
 
  • When you select "RETEST", to refresh the information, it fails with the error message "Could not execute Online health checks": 
image.png
 
  • CEIP is enabled
  • in /var/log/vmware/analytics/analytics.log you find the following errors:
2022-04-08T10:41:02.492Z data-app-collector-vsphere.adc.7_0U3  ERROR phservice.provider.common.internal.SafeDataProvidersConnectionWrapper Error while getting the data providers list from: com.vmware.ph.phservice.provider.appliance.ApplianceDataProvidersConnection java.lang.IllegalStateException: Unable to locate VAPI URI.
        at com.vmware.ph.phservice.common.vapi.client.CisContextVapiClientBuilder.build(CisContextVapiClientBuilder.java:84)
        at com.vmware.ph.phservice.provider.appliance.internal.BaseApplianceDataProviderConnection.getVapiClient(BaseApplianceDataProviderConnection.java:54)
        at com.vmware.ph.phservice.provider.appliance.vmon.VmonDataProvidersConnection.getDataProviders(VmonDataProvidersConnection.java:35)
        at com.vmware.ph.phservice.provider.common.internal.CompositeDataProvidersConnection.getDataProviders(CompositeDataProvidersConnection.java:40)
        at com.vmware.ph.phservice.provider.appliance.ApplianceDataProvidersConnection.getDataProviders(ApplianceDataProvidersConnection.java:35)
        at com.vmware.ph.phservice.provider.common.internal.SafeDataProvidersConnectionWrapper.getDataProviders(SafeDataProvidersConnectionWrapper.java:51)
        at com.vmware.ph.phservice.provider.common.internal.CompositeDataProvidersConnection.getDataProviders(CompositeDataProvidersConnection.java:40)
        at com.vmware.ph.phservice.provider.vsphere.VSphereDataProvidersConnection.getDataProviders(VSphereDataProvidersConnection.java:86)
        at com.vmware.ph.phservice.collector.core.DefaultQueryServiceConnection.getQueryService(DefaultQueryServiceConnection.java:67)
        at com.vmware.cis.data.internal.adapters.dsvapi.SharedDsDefaultingQueryServiceConnectionFactory$SharedQueryServiceConnection.getQueryService(SharedDsDefaultingQueryServiceConnectionFactory.java:125)
        at com.vmware.ph.phservice.cloud.dataapp.internal.collector.SpecsCollector.collect(SpecsCollector.java:77)


 
 


Environment

VMware vCenter Server 7.0.3
VMware vCenter Server 6.7.x

Resolution

This issue is fixed in vCenter Server 7.0 Update 3e and vCenter Server 6.7 Update 3r

Workaround:
There is no workaround for this issue.

Powered by Wolken Software