Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Storage Providers fail to display in Web Client with error message: "The storage service is not initialized. Try again later." (60325)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 16054Language:
English

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

When checking Storage Providers in the Web Client you see empty list and an error similar to: The storage service is not initialized. Try again later.

In /var/log/vmware/vmware-sps/sps.log on vCenter Server you see errors similar to:

2018-10-13T06:06:50.942Z [pool-20-thread-1] DEBUG opId=sps-PSVDCleanup-257037-916 com.vmware.vim.sms.policy.PolicyManagerImpl - Waiting for 1000 millisecs till all the providers are loaded...
2018-10-13T06:06:51.942Z [pool-20-thread-1] DEBUG opId=sps-PSVDCleanup-257037-916 com.vmware.vim.sms.policy.PolicyManagerImpl - Waiting for 1000 millisecs till all the providers are loaded...
2018-10-13T06:06:52.942Z [pool-20-thread-1] DEBUG opId=sps-PSVDCleanup-257037-916 com.vmware.vim.sms.policy.PolicyManagerImpl - Waiting for 1000 millisecs till all the providers are loaded...
2018-10-13T06:06:53.942Z [pool-20-thread-1] DEBUG opId=sps-PSVDCleanup-257037-916 com.vmware.vim.sms.policy.PolicyManagerImpl - Waiting for 1000 millisecs till all the providers are loaded...
2018-10-13T06:06:54.943Z [pool-20-thread-1] DEBUG opId=sps-PSVDCleanup-257037-916 com.vmware.vim.sms.policy.PolicyManagerImpl - Waiting for 1000 millisecs till all the providers are loaded...
2018-10-13T06:06:55.684Z [pool-24-thread-10] DEBUG opId=lro-2-42443ae5-bcc com.vmware.vim.storage.common.security.CommonActivationValidator - Found saml token in auth data for user: vpxd-4f764c70-1509-11e5-
8ba7-005056000ead
2018-10-13T06:06:55.684Z [pool-24-thread-10] DEBUG opId=lro-2-42443ae5-bcc com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session using saml token...
2018-10-13T06:06:55.684Z [pool-22-thread-4] DEBUG opId=lro-2-42443ae5-bcc com.vmware.vim.storage.common.util.SimpleTimeCounter - TIMER STARTED: queryProvider
2018-10-13T06:06:55.684Z [pool-22-thread-4] DEBUG opId=lro-2-42443ae5-bcc com.vmware.vim.sms.StorageManagerImpl - ProviderLoader initialization is ongoing.
2018-10-13T06:06:55.684Z [pool-22-thread-4] ERROR opId=lro-2-42443ae5-bcc com.vmware.vim.sms.StorageManagerImpl - [queryProvider] Failed with exception.
(sms.fault.ServiceNotInitialized) {

In /var/log/iofiltervpd.log on ESXi host you see entries similar to:

2018-11-02T00:13:10Z iofiltervpd[69019]: IOFVPSSL_VerifySSLCertificate:150:Client certificate can't be verified
2018-11-02T00:13:20Z iofiltervpd[69019]: IOFVPSSL_VerifySSLCertificate:150:Client certificate can't be verified
2018-11-02T00:13:30Z iofiltervpd[69019]: IOFVPSSL_VerifySSLCertificate:150:Client certificate can't be verified

When checking status of SPS service, it is still in Yellow state even after several hours after SPS service restart:

root@vc01 [ /tmp ]# wget localhost:22000/sms/HealthStatus ; cat HealthStatus ; rm HealthStatus
--2018-11-16 12:46:26-- http://localhost:22000/sms/HealthStatus
Resolving localhost... 127.0.0.1
Connecting to localhost|127.0.0.1|:22000... connected.
HTTP request sent, awaiting response... 200
Length: unspecified [application/xml]
Saving to: ‘HealthStatus’

HealthStatus [ <=> ] 450 --.-KB/s in 0s

2018-11-16 12:46:26 (49.1 MB/s) - ‘HealthStatus’ saved [450]

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><healthStatus schemaVersion="1.0" xmlns="http://www.vmware.com/cis/cm/common/jaxb/healthstatus"><status>YELLOW</status><message messageKey="com.vmware.vim.sms.InitializationInProgress" defaultMessage="{0} initializing..."><param xsi:type="xs:string" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">VASA providers</param></message></healthStatus>

When running netstat command you see stuck connection to specific IOFilter in CLOSE_WAIT state for several hours:

root@vc01 [ /var/log/vmware/vmware-sps ]# netstat -pan output | grep -i sps

tcp 0 0 127.0.0.1:22000 0.0.0.0:* LISTEN 30309/vmware-sps.la
tcp 0 0 127.0.0.1:22100 0.0.0.0:* LISTEN 30309/vmware-sps.la
tcp 0 0 127.0.0.1:8190 0.0.0.0:* LISTEN 30309/vmware-sps.la
tcp 0 0 127.0.0.1:8191 0.0.0.0:* LISTEN 30309/vmware-sps.la
tcp 0 0 127.0.0.1:8190 127.0.0.1:47768 ESTABLISHED 30309/vmware-sps.la
tcp 0 0 127.0.0.1:56588 127.0.0.1:10080 ESTABLISHED 30309/vmware-sps.la
tcp 0 0 127.0.0.1:51832 127.0.0.1:443 ESTABLISHED 30309/vmware-sps.la
tcp 1867 64240 192.168.0.217:57181 192.168.10.20:9080 CLOSE_WAIT 30309/vmware-sps.la <<<<<<<<<<<< Example of stuck Provider (CLOSE_WAIT connection for several hours)
tcp 0 0 127.0.0.1:52184 127.0.0.1:443 ESTABLISHED 30309/vmware-sps.la
tcp 0 0 127.0.0.1:52266 127.0.0.1:443 ESTABLISHED 30309/vmware-sps.la
tcp 0 0 127.0.0.1:56776 127.0.0.1:10080 ESTABLISHED 30309/vmware-sps.la
tcp 0 293 192.168.0.217:37614 192.168.20.32:9080 ESTABLISHED 30309/vmware-sps.la
unix 3 [ ] STREAM CONNECTED 26144279 30309/vmware-sps.la
unix 3 [ ] STREAM CONNECTED 26141247 30309/vmware-sps.la
unix 2 [ ] STREAM CONNECTED 26147124 30309/vmware-sps.la
unix 2 [ ] STREAM CONNECTED 26147419 30309/vmware-sps.la
unix 3 [ ] STREAM CONNECTED 26148013 30309/vmware-sps.la

Resolution

This issue is resolved in VMware vSphere 6.5 U3 and 6.7 U3, available at VMware Downloads

If you experience the preceding symptoms, contact VMware Technical Support by filing a support request, and note this KB article ID (60325) in the problem description. For more information, see How to Submit a Support Request.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vCenter Server

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vCenter Server 6.x

Take Our Survey

Support Assistant