Virtualization, Cloud, Infrastructure and all that stuff in-between
My ramblings on the stuff that holds it all together
vSphere Performance Overview Page – This Program Cannot Display the Webpage
Posted by on November 23, 2009
When trying to browse the performance overview tab in the vSphere client you may get this error;
“This program cannot display the webpage”
However, the advanced tab works ok and you can still build custom charts.
Luckily, this is pretty simple to fix, the cause of this problem is that the VMware Virtual Centre Management Webservices service is not running.
the VI client breaks out to an internal webservice to deliver the graphs on the performance overview page.
to fix this problem you can start the service manually.
I have seen this problem on virtualised Virtual Center installations where the VC box cannot reach it’s back-end SQL server at start-up; either because of a network problem or delayed/out of sequence start-up.
you can set the recovery options to try and work around this if you cannot fix the root cause.
Once it’s working again you get all the following charty goodness again
Virtualization, Cloud, Infrastructure and all that stuff in-between 
thanks
it fixed me up
I also had this happen recently. It can also happen if port 8443 is not open to your vCenter server. This situation can be identified by checking using both a vSphere client locally (on the vCenter server) and remotely.
This issue is independent of the port 8443,
If starting the service does not help, Try following
Stop the VMware VirtualCenter Server service in Windows.
Restart the database service.
Start the VMware VirtualCenter Server service.
Open a new vSphere Client instance and log into vCenter Server.
Reference – http://www.vmware.com/support/vsphere4/doc/vsp_esx40_u1_rel_notes.html
Didn’t work. However this did: http://communities.vmware.com/thread/221838
it worked. in fact in had to add loopback ip address to the IE trusted sites. sicne due to GP restrictions performance tab not dislaying any thing.
once again thanks.
Thanks for the post! I ended setting this service as a delayed start because Tomcat seems to be a resource hog.
for vsphere 5, mine was more or less solved using this link (in addition to some of the above):
http://communities.vmware.com/docs/DOC-19422