Search the VMware Knowledge Base (KB)
View by Article ID

vSphere Profile-Drivern Storage Service fails (2150565)

  • 0 Ratings

Symptoms

  • The vSphere Profile-Driven Storage service stops responding immediately after it starts.
  • The C:\Program Files\VMware\Infrastructure\Profile-Driven Storage\conf\sps.properties file is zero bit.
  • In the C:\ProgramData\VMware\vCenterServer\logs\vmware-sps\sps.log file, you see entries similar to:
<YYYY-MM-DD>T<TIME>.199+01:00 [WrapperSimpleAppMain] ERROR opId= com.vmware.sps.util.SpsConfiguration - Error reading the configuration file: java.lang.NumberFormatException: null
<YYYY-MM-DD>T<TIME>.201+01:00 [WrapperSimpleAppMain] WARN  opId= org.springframework.context.support.ClassPathXmlApplicationContext - Exception encountered during context initialization - cancelling refresh attempt
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'adapterServer' defined in class path resource [../conf/sps-spring-config.xml]: Cannot resolve reference to bean 'storageProfileManager' while setting bean property 'managedObjects' with key [0]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'storageProfileManager' defined in class path resource [../conf/sps-spring-config.xml]: Invocation of init method failed; nested exception is java.lang.ExceptionInInitializerError
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:359)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:108)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveManagedList(BeanDefinitionValueResolver.java:382)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:157)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1471)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1216)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:538)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:476)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:302)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:229)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:298)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:292)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:762)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:757)

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

Cause

This issue may occur due to a configuration issue with UPN style and Domain level name format which affects the searchability of global catalogs to look for NT user account.

Resolution

To resolve this issue, revert the sps.properties from the backup file created with unique parameters during installation.

To recover the values of sps.serverGuid and vpxd.vcGuid:
  1. Copy the sps.properties file from another vCenter Server.
    • Replace the sps.serverGuid and vpxd.vcGuid values in the properties file that are unique to the vCenter
  2. Locate the sps.serverGuid from the inv-svc-perf.log
    • c:\ProgramData\VMware\vCenter\Logs\invsvc\
    • There is a line entry in the log file: ...Total objects loaded for provider (SPS serverGuid UUID number) of product SPS are 0

  3. Find the vpxd.vcGuid value in the sps.log file
    • ....DEBUG opid= com.vmware.pbm.app.PbmLocalService - [getServerGUIDFromSourceVC] sourceServerGUID : (vpxd.vcGuid UUID number)

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 0 Ratings
Actions
KB: