If you are vSphere administrator, you’ve probably run into this yourself or know someone who has. Some have this problem, don’t. There seems to be no rhyme or reason why it happens to some and not others. Here is how to fix it though.
When attempting to run the client the following errors are received and you are unable to proceed any further:
"Error parsing the server "
"The type initializer for 'VirtualInfrastructure.Utils.HttpWebRequestProxy' threw an exception."
I am running the x64 version of Windows 7 so you will notice that any reference to the ‘Program Files’ will have an ‘(x86)’ at the end of it. If you are running the x86 version of Windows 7 then ignore the ‘(x86)’ portion of the directory path (ie: C:\Program Files (x86) > C:\Program Files).
Follow these 4 basic steps and you’ll be up and running in no time!
Step 1
(file download temporarily offline)
*Note: This DLL is usually found in the %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\ directory of a non Windows 7 PC with .NET v3.5 SP1 installed.
Step 2
Once downloaded install it in the C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib directory.If the ‘lib’ directory doesn’t exist then create it and drop the dll file into it.
Step 3
Next edit the “VpxClient.exe.config” file which can be found in the “C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher” directory and add the following three lines to it in the location specified in the screenshot below.Then save the changes.
<runtime>
<developmentMode developerInstallation="true" />
</runtime>
Step 4
From the Windows 7 ‘System Properties’ click the ‘Advanced’ tab and then the ‘Environment Variables’ button as we want to add a new ‘System’ variable.
Create a new ‘System’ variable called ‘DEVPATH’ and assign the following variable value:
C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
You are now ready to start using the VMware vSphere Client on your Windows 7 machine!Some people have reported having to run the client as an ‘Administrator’ so if you are having difficulties it may pay to try this – I luckily didn’t experience this problem. Also you will likely have to reboot your machine (or restart the explorer.exe process) for your new path information to come into effect.