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

By | June 14, 2010

vSphere client is well know utility to mange and administrate VMware infrastructures. This software is available with ESX, ESXi (paid version), and vCenter Server downloads. Users with appropriate permission can login into VMware environment using vSphere client.

Soon after the latest Windows .Net update, access to VMware infrastructure using vSphere client result in a “error: parsing the server “<servername>” “clients.xml” file”. This error is known to VMware Company and they have already released the patch.

Follow the instructions to solve the error: “parsing the server “<servername>” “clients.xml” file

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

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 the latest version of the vSphere Client.

a.  To download and install the vSphere Client for ESX, ESXi (paid version), and vCenter Server:

  • Go the downloads site.
    Note: The vSphere Client .exe is part of the ESX, ESXi, or vCenter Server download binaries.
  • Click Download next to your ESX, ESXi, or vCenter Server edition.
  • Log in with your VMware Account credentials.
  • Click Yes to agree to the EULA.
  • 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.
  • Follow the on-screen instructions to install the updated vSphere Client.

b. To download and install the vSphere Client for ESXi (free version):

  • Go to the ESXi download site.
  • Click Download.
  • Log in with your account credentials, or register for free.
  • Click Download next to vSphere Client and Host Update Utility.
  • Follow the on-screen instructions to install the updated vSphere Client.

2. 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.

To determine your build number:

  1. Log in to the vSphere Client.
  2. Click Help > About. There first entry is shows the build number of the vSphere Client.OR

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 SettingsApplication DataVMwarevpx on the system running the vSphere Client. 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

Reference Link: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1022611

Cheers!

Melbin Mathew

Talk2Melbin

https://www.talk2melbin.com

Melbin Mathew

I am Melbin Mathew, Systems Engineer from Kerala, India. I live with my parents, daughter and my wonderful wife. I graduated in 2004 with a bachelor’s degree in Electronics and Hardware from Mahatma Gandhi University, Kottayam and completed certification in MCITP, RHCE, CCNA, VCP ...Read More
Category: Virtualization Windows

About Melbin Mathew

I am Melbin Mathew, Systems Engineer from Kerala, India. I live with my parents, daughter and my wonderful wife. I graduated in 2004 with a bachelor’s degree in Electronics and Hardware from Mahatma Gandhi University, Kottayam and completed certification in MCITP, RHCE, CCNA, VCP ...Read More