vmware vsphere client error parsing server"IP" client.xml on windows 7

[wadihmurr]

i need working vsphere client for windows 7

any solution?

[wadihmurr]

Error Parsing the server 1.2.3.4 clients.xml file. Login will continue contact your system administrator

After clicking OK, you get the real message:

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

A workaround for the solution was posted by ftublo on the VMware Communities forums.

1. Create a folder (e.g.<code># Lib</code># ) in the Windows 7 machine where the vSphere client is installed (<code># %ProgramFiles%\[VMware|http://blog.ozmonet.com/tag/vmware/|Posts tagged with vmware]\Infrastructure\Virtual Infrastructure Client\Launcher\</code># ).

2. Obtain a copy of<code># %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\System.dll</code># from a non-Windows 7 machine that has .NET 3.5 SP1 installed. Copy this file into the folder created in Step 1.

3. In the vSphere client launcher directory, open the<code># VpxClient.exe.config</code># file in a text editor and add a<code># &lt;runtime&gt;</code># element and a<code># &lt;developmentMode&gt;</code># element within the<code># &lt;configuration&gt;</code># element. Save the file.
   bq.<code># &lt;?xml version="1.0" encoding="utf-8"?&gt;
   &lt;configuration&gt;
   ...
   &lt;runtime&gt;
   &lt;developmentMode developerInstallation="true"/&gt;
   &lt;/runtime&gt;
   &lt;/configuration&gt;</code>

1. Create a batch file (e.g.<code># VpxClient.cmd</code># ) in a suitable location (e.g. Desktop). In this file add a command to set the DEVPATH environment variable to the folder where you copied the System.dll assembly in step 2 and a second command to launch the vSphere client. Save the file.
   bq.<code># SET DEVPATH=%ProgramFiles%\[VMware|http://blog.ozmonet.com/tag/vmware/|Posts tagged with vmware]\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
   "%ProgramFiles%\[VMware|http://blog.ozmonet.com/tag/vmware/|Posts tagged with vmware]\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe"</code>

NOTE: If you are running 64-bit Windows, replace all instances of

Program Files

with

Program Files (x86)

.

You can now use the VpxClient.cmd (or the shortcut) to launch the vSphere client in Windows 7.

This workaround bypasses the normal .NET Framework loading mechanism. Assembly versions found in the DEVPATH folder are not checked. Handle with care.

this solution work properly

t y

[Texiwill]

Hello,

Moved to vSphere forum.

Check out http://www.techhead.co.uk/running-vmware-vsphere-client-on-windows-7

These instructions also work for W2K8 R2 as well.

Best regards,

Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009, Virtualization Practice Analyst[/url]
Now Available: 'VMware vSphere(TM) and Virtual Infrastructure Security: Securing the Virtual Environment'[/url]
Also available 'VMWare ESX Server in the Enterprise'[/url]
[url=http://www.astroarch.com/wiki/index.php/Blog_Roll]SearchVMware Pro[/url]|Blue Gears[/url]|Top Virtualization Security Links[/url]|Virtualization Security Round Table Podcast[/url]

[ealaqqad]

Hi Everyone,

In case you are using Windows XP, then the solution was provided in here is not for you. In case of windows XP & you are facing the same error you should just download the latest vSphere client or follow my following post:

I hope this help some one, if it does please reward points.

Enjoy,

Eiad Al-Aqqad

System X & Storage Technical Specialist

Founder of http://www.VirtualizationTeam.com

Founder of http://www.TSMGuru.com

[hellesangel]

Perhaps someone can confirm this workaround would also solve this similar problem.  The first dialog error message I get is the same as listed above, however in place of the exception error comes this one

For the benefit of the search engines the text is 'Content-Type' is an unexpected token.  The expected token is "'" or "". Line 4, position 18

Googling showed no results so far for this text.

This is the latest vSphere Client 4.1 Update 1, downloaded today, installed on a clean Win7 64bit Home Premium.

Thanks in advance.

Edit: I can confirm it doesn't work, at least because of 32/64bit problems with the provided system.dll

[hellesangel]

The problem was an incorrect IP address for the VMWare server...  With the correct address it now works perfectly.  The error message could be a bit more informative...