Hi,
I hope it is not too late.
There is a similar issue here not answered too, but it might have been solved by ppohl => http://communities.vmware.com/message/1444796#144479
Your issue could be due to the fact the database is overloaded. You should check if the CPU, Disk, Memory usage are in a reasonable window on the database server. Have you tried using another vSphere client installed on another machine?
I am not sure neither if this is the best method nor if it is supported, here is how I would try to get the stats to build the charts assuming I have not the time to fix the issue in the vSphere client/server and that the problem is not from the database.
1) vCenter uses a SQL Server backend to store data. Stats you need are likely to be stored in the database, if not then the below procedure is useless !http://communities.vmware.com/images/emoticons/happy.gif!.
2) Understand where are stored the stats you need (in which table(s)). Assuming you are not running the express version of SQL Server, you should have a utility called SQL Server Profiler that can capture the requests sent by vCenter.
There is an introduction on how to use this tool there:
This might not be an easy step depending how deep is your knowledge about the vCenter database.
3) Once you found the query(ies) that are run to build the chart in the vSphere client, use an application such as crystal report to build the charts that connects to e.g. a recent backup of your database.
Alternatively, export the results of the queries to a spreadsheet applications and build your charts there.
I highly advise you to work on a recent backup of your database, not on the production one when you attempt to retrieve the stats.
If you have a DBA sitting near you and you are not confident with the above steps, you should discuss with him how to perform them.
I hope this will help.
Yann
