Pages

Saturday 13 April 2013

vSphere Client stops responding when trying to view custom performance charts (1030983)

vSphere Client stops responding when trying to view custom performance charts (1030983)

Symptoms
  • Using custom performance charts with a custom time range can cause the vSphere Client session connected to vCenter server to stop responding and consume 100% of one client logical CPU. For information about using custom performance charts refer to Customize Advanced Chart Views section from the vSphere Datacenter Administration Guide.

  • The vSphere client log may show these errors:
    SSL Validation failed in WebRequestPatch.
    System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.21.xx.xx:8443
       at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
       at VirtualInfrastructure.Utils.WebRequestPatch.PreAuthSSL(HttpWebRequest request, Uri uri)
    SSL Validation failed in WebRequestPatch.
    System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.21.xx.xx:8443
       at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
       at VirtualInfrastructure.Utils.WebRequestPatch.PreAuthSSL(HttpWebRequest request, Uri uri)
    Invoke 67 Start WaitForUpdates on PropertyCollector:propertyCollector [xx.vmware.com].
    Initial socket creation and SSL authentication failed:
    System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.21.xx.xx:8443
       at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
       at VpxClient.Plugins.WebBrowserProxy.RedirectBrowser()
    Invoke 67 Finish WaitForUpdates on PropertyCollector:propertyCollector [xx.vmware.com] - Serial:0.002, Server:018.225

Note: For the location of vSphere client logs, see Common vCenter Server and vSphere Client Windows paths (1028185).

Resolution

VMware is aware of this issue and is working on a fix to resolve this issue.

However, you can workaround this issue by clearing the custom performance chart from the client, and avoid using a custom start time on a whole round hour (e.g. 1:00, 2:00, 3:00...).

To delete the custom chart information from the vCenter client:

  • Browse to the this directory:
    On Windows 7/2008:
    %USERPROFILE%\AppData\Roaming\VMware
    On previous versions of Windows:
    %USERPROFILE%\Application Data\VMware
  • The <VS host>-charts.xml file contains the custom chart data.

  • This file can be deleted completely if this is the only custom chart
    or

  • You can edit the file to retain other custom charts:

    1. Open the XML file in a text editor.
    2. Locate the offending chart by searching for its Name
    3. Select all lines starting from and including <object> until you find </object> corresponding to the chart name and Delete them
    4. Save the file. The changes take effect in the vSphere client right away.

Note: This article assumes that you are familiar with XML concepts and that you have made adequate backups before proceeding.