vCenter server Skyline health error "Unable to query vSphere health information. Check vSphere client logs for more information."
search cancel

vCenter server Skyline health error "Unable to query vSphere health information. Check vSphere client logs for more information."

book

Article ID: 373923

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

vCenter skyline health is not working, showing below error in vSphere client:

When we look at the /var/log/vmware/sps.log file, we may see the below entries:

YYYY-MM-DDTXX:XX:XX.278Z [pool-20-thread-1] DEBUG opId=sps-PSVDCleanup-999147-409 com.vmware.vim.sms.policy.PolicyManagerImpl - Waiting for 1000 millisecs till all the providers are loaded...
YYYY-MM-DDTXX:XX:XX.450Z [pool-24-thread-2] DEBUG opId=dam-auto-generated: StorageProvidersViewMediator:dr-2365:SmsPropertyProvider:200073:105321-598590-ngc:70017925 com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session using session cookie...
YYYY-MM-DDTXX:XX:XX.480Z [pool-22-thread-2] DEBUG opId=dam-auto-generated: StorageProvidersViewMediator:dr-2365:SmsPropertyProvider:200073:105321-598590-ngc:70017925 com.vmware.vim.sms.StorageManagerImpl - [queryArray] Received API Call: queryArray
YYYY-MM-DDTXX:XX:XX.481Z [pool-22-thread-2] DEBUG opId=dam-auto-generated: StorageProvidersViewMediator:dr-2365:SmsPropertyProvider:200073:105321-598590-ngc:70017925 com.vmware.vim.sms.StorageManagerImpl - ProviderLoader initialization is ongoing.
YYYY-MM-DDTXX:XX:XX.481Z [pool-22-thread-2] ERROR opId=dam-auto-generated: StorageProvidersViewMediator:dr-2365:SmsPropertyProvider:200073:105321-598590-ngc:70017925 com.vmware.vim.sms.StorageManagerImpl - [queryArray] Operation queryArray failed
(sms.fault.ServiceNotInitialized) {
   faultCause = null,
   faultMessage = null

Also, you will see an event for setContext for iofiltervpd provider, but it will not complete.

YYYY-MM-DDTXX:XX:XX:00.006Z [Thread-9] DEBUG opId=sps-Main-999074-744 com.vmware.vim.storage.common.util.SimpleTimeCounter - TIMER
STARTED: VasaClientImpl : setContext for provider: https://hostname.com:9080/version.xml

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

Environment

vCenter server version: 7.0.3.01900, Build 23788036

Cause

vCenter Storage Monitoring Service (com.vmware.vim.sms) was not running. 

Resolution

Rebuild the missing service using lsdoctor -r option using this KB: 320837

 

Additional Information

Lookup Service Doctor (lsdoctor) is a tool used to address issues with data stored in the PSC database, as well as data local to a vCenter (regardless of whether the PSC is external or embedded).  The tool can be used to detect and correct problems that could cause failures in topology changes (converge, repoint, etc.), upgrades, or failures incurred as a result of maintenance (e.g. incorrectly applying new SSL certificates).  This article will outline its functions and use.

-r, --rebuild

This option is used when rebuilding one or all service registrations for a given node.  This action performs the most significant changes, and extra care should be taken to ensure a safe rollback is possible (see Impact/Risks section).