Upgraded to Windows 7? Trying to use VMWare vSphere Client? Getting the messages:
Error parsing the server “YOUR SERVERS IP” “clients.xml” file. Login will continue, contact your system administrator.
You click OK and they you get:
The type initializer for ‘VirtualInfrastructure.Utils.HttpWebRequestProxy’ threw an exception.
You click OK and vSphere fails to launch 🙁
After upgrading to Windows 7 you may have suddenly read horrible threads that tell you VMWare vSphere client will not work. Well its all lies. Its true that it wont work out the box, but a quick tweak and you’ll be good to go in minutes.
Follow these steps, which will get you up and working again in a flash.
1:) Obtain a copy of .NET framework system.dll from a non Windows 7 box. In my case I took it from a Windows 2003 server. The file is located at %SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727 which for me was c:\windows\Microsoft.NET\Framework\v2.0.50727
2:)Create a folder (call it Lib+) in your VMWare vSphere installation to put this file. I created the following (on a 32bit installation) C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib+
A quick summary, you should now have a folder called C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib+ with a file called System.dll from a non windows 7 installation of .NET Framework v2.0.50727
3:) Now go into C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher and edit the file VpxClient.exe.config in textpad or notepad etc..
Add in the following lines just before the final line (which reads </configuration>)
Save this file
Now create a batch file called whatever you choose – I choose vSphereLauncer.cmd but it doesnt matter, and put the following in it (on the assumption that the paths are correct etc..) – Note it is 2 seperate lines.
SET DEVPATH=%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib+
“%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe”
Run your newly created batch file, and you should no longer get that irritating message!
If this post was useful, please click some of the Ad blocks which help me to keep this site running. Thanks!