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

"An error occurred while starting service 'sps' VMware vSphere Profile-Driven Storage Service failed to start" During vCenter 7.0 Upgrade (78900)

Last Updated: 6/26/2020Categories: Known IssueTotal Views: 34737Language:
English

5 like this article

Subscribe to get an email
newsletter with new updates

5 people found this helpful Please provide article feedback:

Symptoms

Upgrading to vCenter Server 7.0 Fails with Error:

An error occurred while starting service 'sps'
VMware vSphere Profile-Driven Storage Service failed to start

In /var/log/firstboot/firstbootStatus.json file, you see entries similar to:

"failedSteps": "sms_spbm_firstboot",

In /var/log/firstboot/sms_spbm_firstboot.py_XXXXX_stderr.log, you see entries similar to:

2020-04-21T16:13:32.135Z ERROR starting sps rc: 1, stdout: , stderr: Start service request failed. Error: Operation timed out

2020-04-21T16:13:32.135Z Failed to start the service : {
"detail": [
{
"id": "install.ciscommon.service.failstart",
"translatable": "An error occurred while starting service '%(0)s'",
"args": [
"sps"
],
"localized": "An error occurred while starting service 'sps'"
}
],
"componentKey": null,
"problemId": null,
"resolution": null
}

In /var/log/vmware/vmware-sps/sps.log, you see entries similar to:

2020-04-21T16:01:49.707Z [Thread-10] ERROR opId=sps-Main-484890-690 com.vmware.vim.storage.common.kv.KvDefaultValueMarshaller - Unable to unmarshal stream to object.
org.apache.commons.lang.SerializationException: java.io.InvalidClassException: com.vmware.vim.binding.impl.vmodl.LocalizableMessageImpl; local class incompatible: stream classdesc serialVersionUID = 5180556415689811114, local class serialVersionUID = 1
at org.apache.commons.lang.SerializationUtils.deserialize(SerializationUtils.java:168)
.....
at com.vmware.vim.sms.StorageManagerImpl$ProviderLoader.run(StorageManagerImpl.java:253)
Caused by: java.io.InvalidClassException: com.vmware.vim.binding.impl.vmodl.LocalizableMessageImpl; local class incompatible: stream classdesc serialVersionUID = 5180556415689811114, local class serialVersionUID = 1
at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:699)
....
at org.apache.commons.lang.SerializationUtils.deserialize(SerializationUtils.java:163)
... 11 more
2020-04-21T16:01:49.720Z [main] ERROR opId=sps-Main-484890-690 com.vmware.vim.vmomi.core.soap.impl.unmarshaller.StackContextFactory - Missing namespace definition detected for namespace prefix xsd
2020-04-21T16:01:49.725Z [main] ERROR opId=sps-Main-484890-690 com.vmware.vim.vmomi.core.soap.impl.unmarshaller.StackContextFactory - Missing namespace definition detected for namespace prefix xsd
2020-04-21T16:01:49.725Z [main] ERROR opId=sps-Main-484890-690 com.vmware.vim.vmomi.core.soap.impl.unmarshaller.StackContextFactory - Missing namespace definition detected for namespace prefix xsd
2020-04-21T16:01:49.723Z [Thread-10] ERROR opId=sps-Main-484890-690 com.vmware.vim.storage.common.kv.LocalKvReaderWriter - Failed to get values for the key prefix '' from the provider '[Name:providerInfoKvProvider Optimistic locking:]'.
com.vmware.vim.storage.common.kv.exceptions.KvValueUnmarshalException: org.apache.commons.lang.SerializationException: java.io.InvalidClassException: com.vmware.vim.binding.impl.vmodl.LocalizableMessageImpl; local class incompatible: stream classdesc serialVersionUID = 5180556415689811114, local class serialVersionUID = 1
at com.vmware.vim.storage.common.kv.KvDefaultValueMarshaller.unmarshal(KvDefaultValueMarshaller.java:104)
....
at com.vmware.vim.sms.StorageManagerImpl$ProviderLoader.run(StorageManagerImpl.java:253)
Caused by: org.apache.commons.lang.SerializationException: java.io.InvalidClassException: com.vmware.vim.binding.impl.vmodl.LocalizableMessageImpl; local class incompatible: stream classdesc serialVersionUID = 5180556415689811114, local class serialVersionUID = 1
at org.apache.commons.lang.SerializationUtils.deserialize(SerializationUtils.java:168)
at com.vmware.vim.storage.common.kv.KvDefaultValueMarshaller.unmarshal(KvDefaultValueMarshaller.java:101)
... 10 more
Caused by: java.io.InvalidClassException: com.vmware.vim.binding.impl.vmodl.LocalizableMessageImpl; local class incompatible: stream classdesc serialVersionUID = 5180556415689811114, local class serialVersionUID = 1
at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:699)
...
at org.apache.commons.lang.SerializationUtils.deserialize(SerializationUtils.java:163)
... 11 more
2020-04-21T16:01:49.728Z [Thread-10] ERROR opId=sps-Main-484890-690 com.vmware.vim.sms.StorageManagerImpl - Exception while loading providers!
com.vmware.vim.storage.common.kv.exceptions.KvOperationException: Failed to get values for the key prefix '' from the provider '[Name:providerInfoKvProvider Optimistic locking:]'.
at com.vmware.vim.storage.common.kv.LocalKvReaderWriter.getByPrefix(LocalKvReaderWriter.java:223)
....
at com.vmware.vim.sms.StorageManagerImpl$ProviderLoader.run(StorageManagerImpl.java:253)
Caused by: com.vmware.vim.storage.common.kv.exceptions.KvValueUnmarshalException: org.apache.commons.lang.SerializationException: java.io.InvalidClassException: com.vmware.vim.binding.impl.vmodl.LocalizableMessageImpl; local class incompatible: stream classdesc serialVersionUID = 5180556415689811114, local class serialVersionUID = 1
at com.vmware.vim.storage.common.kv.KvDefaultValueMarshaller.unmarshal(KvDefaultValueMarshaller.java:104)
at com.vmware.vim.storage.common.kv.KvDefaultValueMarshaller.toValueObject(KvDefaultValueMarshaller.java:158)
at com.vmware.vim.storage.common.kv.LocalKvReaderWriter.getByPrefix(LocalKvReaderWriter.java:201)
... 8 more
Caused by: org.apache.commons.lang.SerializationException: java.io.InvalidClassException: com.vmware.vim.binding.impl.vmodl.LocalizableMessageImpl; local class incompatible: stream classdesc serialVersionUID = 5180556415689811114, local class serialVersionUID = 1
at org.apache.commons.lang.SerializationUtils.deserialize(SerializationUtils.java:168)
at com.vmware.vim.storage.common.kv.KvDefaultValueMarshaller.unmarshal(KvDefaultValueMarshaller.java:101)
... 10 more
Caused by: java.io.InvalidClassException: com.vmware.vim.binding.impl.vmodl.LocalizableMessageImpl; local class incompatible: stream classdesc serialVersionUID = 5180556415689811114, local class serialVersionUID = 1
at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:699)
....
at org.apache.commons.lang.SerializationUtils.deserialize(SerializationUtils.java:163)
... 11 more

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

Cause

This issue occurs when there are storage providers in statusFault = (sms.fault.ProviderSyncFailed) state.

Resolution

This issue is resolved in vCenter Server 7.0.0b, available at VMware Downloads

Workaround

To workaround this issue, resolve the storage provider statusfault in source vCenter:

Finding storage provider in statusFault = (sms.fault.ProviderSyncFailed)

Un-register and re-sync storage provider:

Finding storage provider in statusFault = (sms.fault.ProviderSyncFailed)

Connect to the source vCenter sms Managed Object Browser to list Storage Providers using below URL with a vCenter Administrator user credentials:

https://<vCenter FQDN/IP>/sms/mob?moid=storageManager&method=QueryProvider

Click on the "Invoke Method" link and note down the list of providers

For Example:

On a new browser tab use the below URL with a vCenter Administrator user credentials to show details of the Provider:

https://<vCenter FQDN/IP>/sms/mob?moid=<VASAPROVIDER-ID>&method=QueryProviderInfo

For Example:

https://vcenter.test.org/sms/mob?moid=vasaProvider-1&method=QueryProviderInfo

Click on the "Invoke Method" link.

From the output search (Ctrl+F) for statusFault, if the value is NOT null, note down the uid of the provider

For example: uid = 0e178603-1877-4c7b-8719-a69a76f591c8

Repeat step 3 to 5 for each provider which are not having a statusFault = null

Un-register and re-sync storage provider:

Caution: IO Filter providers will register back on "Synchronize Storage Provider" from vSphere client, Other storage providers require manual registration after unregister.

On a new browser tab connect to below URL with a vCenter Administrator user credentials:

https://<vCenter FQDN/IP>/sms/mob/?moid=storageManager&method=UnregisterProvider_Task

For Example:

https://vcenter.test.org/sms/mob/?moid=storageManager&method=UnregisterProvider_Task

In the value field fill the uid of the provider that need to be unregistered

Click on "Invoke Method" link, the result may look like below:

Go to vCenter's vSphere Client -> select vCenter Server object -> Configure -> Storage Providers

Use the Synchronize Storage Providers  option to register the IO Filter providers back

Use the Add option to register other storage providers back

Validate the statusFault value again following  Finding storage provider in statusFault = (sms.fault.ProviderSyncFailed)

Upgrade to vCenter Server 7.0

If this issue persists, contact VMware Support and note this Article ID (78900) 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)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 7.0.x

Take Our Survey

Support Assistant