Perf Charts service experienced an internal error

I got that error after upgrading my VMware Cluster from vSphere 4 update 2 to vSphere 4.1. Also, I had to migrate my vCenter 4 update 2 (on 32-bit Windows 2003 with MSSQL 2005 installed locally) to vCenter 4.1 (on 64-bit Windows 2008 R2 with a remote MSSQL 2008 R2 Cluster) as vCenter must be install on 64-bit OS.

Anyways, after the upgrade everything went fine escept for some issues like this error:


This error may occure because you are using a custom SQL server database with a custom Java Database Connectivity (JDBC) SQL port

Here are the steps to fix it:

  1. On the vCenter Server system, navigate to: C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter
  2. Open the file.
  3. Comment out the string usevcdb = true.
  4. Ensure that the values for url, driver, and dbtype are as follows or add them (after the “usevcdb = true” line) if they don’t exist:
                      url = jdbc:sqlserver://<hostname>:<port>;integratedSecurity=true
                      driver =
                      dbtype = mssql
  5. Restart the VMware VirtualCenter Management WebServices service.

, ,

  1. #1 by Ed Cates on November 4, 2010 - 7:24 PM


    FINALLY a solution that worked. Yay, Perf Charts!

  2. #2 by P Ramirez on November 1, 2011 - 8:01 PM


    Unbelievable, after looking for a solution for almost 4 hours, finally came to this blog and found an solution that worked!
    I have migrated to vCenter 5 on W2k8 R2 with SQL 2008 R2, and the only issue found so far was the Perf Charts, and the Hardware Status.
    After applying this solution, everything started working just great!

  3. #3 by JF on December 2, 2012 - 1:16 AM

    Thanks for the post, this fixed my problem as well, although the path was different since I was on 2K8R2. The path for me was:
    C:\ProgramData\VMware\VMware VirtualCenter
    The string I used needed the instance name and did not include a port.
    in my case the current string had the instance name wrong (leftovers from old upgrades?)
    (SQLEXP_VIM instead of VIM_SQLEXP)

  1. Website

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: