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

Profile Driven Storage service fails to start after upgrading to vCenter Server 5.5 (2081420)

  • 2 Ratings


  • After upgrading vCenter Server to version 5.5, Storage views does not display.
  • In the sps.log file located at C:\programdata\VMware\Infrastructure\Profile-Driven Storage\Logs\, you see entires similar to:

    <YYYY-MM-DD><TIME> [Thread-6] ERROR opId= - Failed populating service cache
    org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Login failed for user 'domain\VC_machine_account$'.)
            at org.apache.commons.dbcp.BasicDataSource.createPoolableConnectionFactory(
            at org.apache.commons.dbcp.BasicDataSource.createDataSource(
            at org.apache.commons.dbcp.BasicDataSource.getConnection(
            at com.ibatis.sqlmap.engine.transaction.jdbc.JdbcTransaction.init(
            at com.ibatis.sqlmap.engine.transaction.jdbc.JdbcTransaction.getConnection(
            at com.ibatis.sqlmap.engine.mapping.statement.GeneralStatement.executeQueryForList(
            at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelegate.queryForList(
            at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelegate.queryForList(
            at com.ibatis.sqlmap.engine.impl.SqlMapSessionImpl.queryForList(
            at com.ibatis.sqlmap.engine.impl.SqlMapSessionImpl.queryForList(
            at com.ibatis.sqlmap.engine.impl.SqlMapClientImpl.queryForList(
            at com.vmware.vim.sms.ServiceImpl.syncServiceCache(
            at com.vmware.vim.sms.ServiceImpl.init(
            at com.vmware.vim.sms.ServiceImpl.access$100(
            at com.vmware.vim.sms.ServiceImpl$
    Caused by: Login failed for user 'domain\VC_machine_account$'.

  • The wrapper.log file  contains message similar to

    INFO | jvm 1 |
    <YYYY-MM-DD><TIME> |  ERROR opId= - Failed populating service cache
    INFO | jvm 1 |
    <YYYY-MM-DD><TIME> | org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Login failed for user 'domain\VC_machine_account$'.)


This issue can occur when vCenter Server is using a remote database hosted on a Microsoft SQL Server with Windows Authentication, while the Profile Driven Storage service is configured to start with the local system account.

Note: If you are using Microsoft SQL Server 2012, BUILTIN\administrators and Local System (NT AUTHORITY\SYSTEM) are not automatically provisioned in the sysadmin fixed server role. This can prevent the Profile Driven Storage service from accessing the vCenter Server database. For more information, see the Security Enhancements (Database Enginer) section in the Microsoft SQL Server 2012 documentation.


This is a known issue affecting vCenter Server.

Currently, there is no resolution.

To work around this issue, change the VMware vSphere Profile-Driven Storage Service account to a domain account that has permissions to access the vCenter Server database in SQL:
  1. Click Start > Run, type services.msc, and click OK. The Services window opens.
  2. Right-click the VMware vSphere Profile-Driven Storage service and click Properties.
  3. Change Local system account to a domain user with SQL permissions.
  4. Click OK.
  5. Restart the VMware vSphere Profile-Driven Storage service.

See Also

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.


  • 2 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.
  • 2 Ratings