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

VMware vCenter Server fails to populate performance charts and displays an error message when using a custom JDBC SQL port (1021202)

  • 14 Ratings

Details

  • While populating the performance charts, vCenter Server might display the error message:

    Perf Charts service experienced an internal error

  • This might happen when you use a custom SQL server database with a custom Java Database Connectivity (JDBC) SQL port
  • This issue does not occur with Oracle or DB2 databases that are configured with custom JDBC ports

Solution

To ensure that the Performance Overview plug-in properly works with the custom JDBC SQL port, you must edit this file:
  • In vCenter Server 4.0 –statsreport.xml
  • In vCenter Server 4.1 –vcdb.properties
  • In vCenter Server 5.x– vcdb.properties

    Note: These files are located at C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\.
    For Windows 2008, 2008 R2, these files are located at C:\ProgramData\VMware\VMware VirtualCenter.
    For Windows 2012, these files are located at C:\ProgramData\VMware\vCenterServer\cfg\vmware-vpx.

To edit the vcdb.propertiesor statsreport.xml file:

  1. Open the vcdb.propertiesor statsreport.xml file.
  2. Edit this line in the file:

    usevcdb=true


  3. Set these parameters:

    Note: The integratedSecurity parameter depends on this.

    SQL DB authentication mode:

    • SQL only mode: integratedSecurity should be set to false
    • SQL & Windows (Mixed) mode and VMware VirtualCenter Management Webservices is running under Domain\User service account: integratedSecurity should be true

      url = jdbc:sqlserver://<hostname>:<port>; databaseName=<VC database name >
      integratedSecurity = <true|false>
      driver = com.microsoft.sqlserver.jdbc.SQLServerDriver
      dbtype = mssql

  4. Restart the VMware VirtualCenter Management Webservices service on vCenter Server. For more information, see Stopping, starting, or restarting vCenter services (1003895).
 
You may run these query on the Microsoft SQL Server instance in which the vCenter Server database resides to determin which port SQL Server is listening on:

USE MASTER
GO
xp_readerrorlog 0, 1, N'Server is listening on'
GO

Additional Information
 
For translated versions of this article, see:

This Article Replaces

1021826

Update History

10/02/2012 - Added reference to blog to confirm JDBC port being used 10/10/2012 - Added In vCenter Server5.0-vcdb.properties

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

  • 14 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.
  • 14 Ratings
Actions
KB: