Knowledge Base

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

Performance overview and storage views are not displayed after upgrading to vCenter Server 5.1 (2042546)

Symptoms

  • After upgrading to vCenter Server 5.1, the performance overview charts and the storage views no longer display
  • Performance overview charts and the storage views fail to display data
  • In the %ProgramData%\VMware\VMware VirtualCenter\Logs\stats.log file, you see entries similar to:
va.util.concurrent.ExecutionException: java.lang.IllegalStateException: org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Login failed for user 'domain\vCenterhost$'.)
        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 (Login failed for user 'domain\vCenterhot$'.)
        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

Cause

When using Windows authentication with SQL server, the name of the server is passed to the SQL server and not the user.

Resolution

To resolve the issue, you need to update the registry file with the domain user account that has permissions to connect to the SQL server. This is usually the user account that is used to start the service.

To update the registry file:

Note: Before making any changes to the registry, ensure that you have a current and valid backup of the registry and the virtual machine. For more information on backing up and restoring the registry, see the Microsoft Knowledge Base article 136393.

  1. Log in to vCenter Server.
  2. Click Start > Run, type regedit, and click OK. The Registry Editor window opens.
  3. Navigate to HKEY_LOCAL_MACHINE > SOFTWARE > VMWARE, Inc. > VMware VirtualCenter > DB.
  4. Verify if key 2 is blank.
  5. If this is blank, add the domain user to the key's Value data field. For example, domain\domain user.
  6. Restart the VMware vCenter Management Webservices. For more information, see Stopping, starting, or restarting vCenter services (1003895).

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.

Feedback

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