vSphere Client Overview Performance Charts fail with the error: Perf Charts service experienced an internal error
Article ID: 311745
Updated On:
Products
VMware vCenter Server
VMware vSphere ESXi
Issue/Introduction
Symptoms:
- vSphere Client Overview Performance Charts fail
- You see the error:
Perf Charts service experienced an internal error:
Message: Report application initialization is not completed successfully. Retry in 60 seconds
- In the stats.log file located at %ProgramData%\VMware\VMware VirtualCenter\Logs\, you see entries similar to:
[5:22:24,211 Thread-2 ERROR com.vmware.vim.common.lifecycle.InitializerExecutor] Initialization error; attempt 2 will begin in 60 seconds...
java.util.concurrent.ExecutionException: java.lang.IllegalStateException: org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Cannot open user default database. Login failed.)
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 (Cannot open user default database. Login failed.)
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 (Cannot open user default database. Login failed.)
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: com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open user default database. Login failed.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:196)
at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:246)
at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:83)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(SQLServerConnection.java:2532)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(SQLServerConnection.java:1929)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.access$000(SQLServerConnection.java:41)
at com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(SQLServerConnection.java:1917)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:4026)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1416)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1061)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:833)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:716)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:841)
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
Environment
VMware vSphere Web Client 5.1.x
VMware vSphere Web Client 5.0.x
VMware vCenter Server 5.5.x
VMware vCenter Server 5.1.x
VMware vCenter Server 5.0.x
VMware vSphere Web Client 5.5.x
VMware vSphere Web Client 5.0.x
VMware vCenter Server 5.5.x
VMware vCenter Server 5.1.x
VMware vCenter Server 5.0.x
VMware vSphere Web Client 5.5.x
Cause
This issue occurs because of old entries in the vcdb.properties file that reference a stale entry for the Database Server for the vCenter Server.
Resolution
To resolve this issue, remove or comment out the stale entries in the vcdb.properties file.
To remove or comment out the stale entries:
- Remove or comment out the stale entries in the vcdb.properties file.
For example, if the stale entries are similar to:
For Windows, just deduce the JDBC URL and user/password from the
data source information in the VC registry
usevcdb=true
url=jdbc:sqlserver://SERVER\\INSTANCE
dbtype=mssql
driver=com.microsoft.sqlserver.jdbc.SQLServerDriver
Comment these entries by adding a hash (#) sign before them similar to:
# For Windows, just deduce the JDBC URL and user/password from the
# data source information in the VC registry
usevcdb=true
#url=jdbc:sqlserver://SERVER\\INSTANCE
#dbtype=mssql
#driver=com.microsoft.sqlserver.jdbc.SQLServerDriver
Note: By default, the vcdb.properties file is located at:
- Windows Server 2008 – C:\ProgramData\VMware\VMware VirtualCenter\
- Windows Server 2003 – C:\%ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter\
- Restart the VirtualCenter Management Webservices. For more information, see Stopping, starting, or restarting vCenter services (1003895).
Additional Information
Feedback
Yes
No
Powered by
