vSphere Client does not open on any Windows operating systems with the error: parsing the server “” “clients.xml” file

Symptoms

  • When trying to launch the vSphere Client you receive errors similar to:

    Error parsing the server “<servername>” “clients.xml” file.

    The type initializer for VirtualInfrastructure.Utils.HttpWebRequestProxy’ threw an exception.

Resolution

You cannot use vSphere Clients prior to the Update 1 release, to access the vCenter Server or ESX hosts because of a Microsoft update that targets the .NET Framework (980773), released on June 9th 2010.  
 
Perform one of these two options to correct the issue:
  1. Download and install vSphere Client 4.0 Update 1 (build 208111) or Update 2 (build 258672) using method a or b below, depending on your environment.
  1. To download and install the vSphere Client for ESX, ESXi (paid version), and vCenter Server:
    1. Go the downloads site.

      Note
      : The vSphere Client .exe is part of the ESX, ESXi, or vCenter Server download binaries.
    2. Click Download next to your ESX, ESXi, or vCenter Server edition.
    3. Log in with your VMware Account credentials.
    4. Click Yes to agree to the EULA.
    5. Click the .exe link next to vSphere Client and Host Update Utility.

      Note: You do not need to download the entire vSphere suite, only the vSphere Client.

    6. Follow the on-screen instructions to install the updated vSphere Client.
  2. To download and install the vSphere Client Update 1 for ESXi (free version):
    1. Click Download.
    2. Log in with your account credentials, or register for free.
    3. Click Download next to vSphere Client and Host Update Utility.
    4. Follow the on-screen instructions to install the updated vSphere Client.

 

  • Remove the MS update from your Windows operating system. The vSphere Client works after the update is removed.
  • Note: This affects Windows XP, Windows 2003, Windows 2008, Windows Vista, and Windows 7.
     
    If the build number for your vSphere Client is 208111 or higher, then you have vSphere Client Update 1 or later, and should not be affected by this issue.
     
    You can determine the version of vSphere Client by reviewing the build number located in the first line of a viclient.log file, located in %USERPROFILE%\Local Settings\Application Data\VMware\vpx on the system running the vSphere Client if the OS is Windows XP or 2003 and %USERPROFILE%\AppData\Local\VMware\vpx in 64 bit Windows 7 or 2008. Build 208111 or higher indicates you are using vSphere Client 4.0 Update 1 or later.
     
    For example:
     
    2010-05-19 03:08:58.508  Log for vSphere Client Launcher, pid=4756, version=4.0.0, build=build-208111, option=release
    VMware KB 1022611