Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

After upgrading to vCenter Server 5.0 Update 1, the Performance tab reports the message: Report application initialization is not completed successfully (2015964)

Symptoms

After upgrading to vCenter Server 5.0 Update 1, you experience these symptoms:

  • The Performance tab reports the message:

    Perf charts service experienced an internal error
    Message: Report application initialization is not completed successfully. Retry in 60 seconds."

  • When you click the Storage Views tab, the Maps view does not function properly

  • In the C:\ProgramData\VMware\VMware VirtualCenter\Logs\stats.log file, you see entries similar to:

    2012-03-20 10:30:12,303 pool-1-thread-1  INFO  com.vmware.vim.common.vim.VcDataSourceInitializer] Start VC DataSource configuration.
    [2012-03-20 10:30:12,335 Thread-2  ERROR com.vmware.vim.common.lifecycle.InitializerExecutor] Initialization error; attempt 3 will begin in 60 seconds...
    java.util.concurrent.ExecutionException: java.lang.IllegalStateException: org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory ([Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user ' DOMAIN\MACHINE$'.)
        at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
        at java.util.concurrent.FutureTask.get(FutureTask.java:83)
        at com.vmware.vim.common.lifecycle.InitializerExecutor$MonitorCallback.run(Unknown Source)
        at java.lang.Thread.run(Thread.java:662)
    Caused by: java.lang.IllegalStateException: org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory ([Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user ' DOMAIN\MACHINE$'.)
        at com.vmware.vim.common.lifecycle.InitializerExecutor$MonitorCallback$1.run(Unknown Source)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        ... 1 more
    Caused by: org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory ([Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user ' DOMAIN\MACHINE$'.)
        at org.apache.commons.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1549)
        at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1388)
        at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
        at com.vmware.vim.common.vim.VcDataSourceInitializer.init(Unknown Source)
        at com.vmware.vim.stats.webui.startup.StatsReportInitializer.createInitializers(Unknown Source)
        at com.vmware.vim.stats.webui.startup.StatsReportInitializer.init(Unknown Source)
        ... 9 more
    Caused by: java.sql.SQLException: [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user DOMAIN\MACHINE$'.
        at sun.jdbc.odbc.JdbcOdbc.createSQLException(JdbcOdbc.java:6957)
        at sun.jdbc.odbc.JdbcOdbc.standardError(JdbcOdbc.java:7114)
        at sun.jdbc.odbc.JdbcOdbc.SQLDriverConnect(JdbcOdbc.java:3073)
        at sun.jdbc.odbc.JdbcOdbcConnection.initialize(JdbcOdbcConnection.java:323)
        at sun.jdbc.odbc.JdbcOdbcDriver.connect(JdbcOdbcDriver.java:174)
        at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
        at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
        at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:1556)
        at org.apache.commons.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1545)
        ... 14 more"
  • Before the upgrade, the VMware VirtualCenter Management Webservices service was running under a Windows Active Directory account

  • The vCenter Server database is set to use Windows authentication

Purpose

This article describes a specific issue. If you experience all of the above symptoms, consult the sections below. If you experience some but not all of these symptoms, your issue is not related to this article. Search the Knowledge Base for your symptoms or Open a Support Request.

Cause

If the VMware VirtualCenter Management Webservices is running under a Windows Active Directory account instead of Local System and you are upgrading to vCenter Server 5.0 Update 1, the VMware VirtualCenter Management Webservices is set to Local System during the upgrade process.

This causes the VMware VirtualCenter Server and VMware VirtualCenter Management Webservices services to no longer run under the same domain account. The VMware VirtualCenter Server service continues to run under the domain account, and the VirtualCenter Management Webservices service runs as Local System.

The VirtualCenter Management Webservices (Tomcat) service starts successfully, but may not operate properly.

Resolution

To work around this issue:
  1. Close all vSphere Client sessions connected to vCenter Server.
  2. Click Start > Run, type services.msc, and click OK. The Services window opens.
  3. Right-click the VMware VirtualCenter Management Webservices service and click Properties.
  4. Click the Log On tab.
  5. Change the account to use This account: and use the same domain account which the VMware VirtualCenter Server service is using.
  6. Click OK.
  7. Right-click the VMware VirtualCenter Management Webservices service and click Restart.
  8. After the service starts, connect to the vCenter Server.

Note: You may have to follow this process for these services:
  • vCenter Inventory Service
  • VMware vSphere Profile-Driven Storage Service

Additional Information

To be alerted when this article is updated, click Subscribe to Document in the Actions box.

See Also

This Article Replaces

2018765, 2017346

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

  • 9 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)
  • 9 Ratings
Actions
KB: