Cannot launch vSphere Client after installing in Windows 7, Windows 2003, or Windows 2008 R2

Products

VMware vCenter Server VMware vSphere ESXi

Issue/Introduction

Symptoms:

You cannot launch the vSphere Client
After installing the vSphere Client in Windows 7, Windows 2003, or Windows 2008 R2, connecting to the vSphere server fails
You see these errors:
- Error parsing the server "<servername>" "clients.xml" file.
- The type initializer for VirtualInfrastructure.Utils.HttpWebRequestProxy' threw an exception.

Note: A recent update from Microsoft for the .NET Framework exhibits this behavior on all Windows operating systems. For more information, see <servername></servername> vSphere Client does not open on any Windows operating systems with the error: parsing the server "<servername><servername>" "clients.xml" file (1022611)</servername>

Environment

VMware ESXi 4.0.x Installable
VMware ESXi 4.0.x Embedded
VMware vCenter Server 4.0.x
VMware VirtualCenter 2.0.x
VMware ESX 4.0.x
VMware VirtualCenter 2.5.x

Resolution

This issue is resolved in VMware vSphere 4.0 Update 1. Prior to this update, the vSphere Client is not supported in Windows 7, Windows 2003, or Windows 2008 R2 and it does not run in Compatibility Mode. This issue may occur because of the .NET loading mechanism change in Windows 2008 R2, Windows 7, and Windows 2003.

To download and install vSphere 4.0 Update 1, see the VMware Download Center.

For more information, see the VMware vCenter Server 4.0 Update 1 Release Notes.

If you cannot upgrade to VMware vSphere 4.0 Update 1, there are 2 possible workarounds. Perform one of these options:

Using VMware Player or VMware Workstation, install a Windows XP virtual machine in Windows 7, Windows 2003, or Windows 2008 R2.
Bypass the normal .NET Framework loading mechanism.

Warning: This workaround is unsupported.

To bypass the normal .NET Framework loading mechanism:

Download the file system.dll. This file is typically located in %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\ directory of a non-Windows 7 or Windows 2008 R2 machine with .NET v3.5 SP1 installed.
Copy the file to C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\lib.

Note: If the lib directory does not exist, create it.
Open VpxClient.exe.config in a text editor. The file is located at C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher.
Add the following three lines to VpxClient.exe.config, just before </configuration>:

<runtime>
<developmentMode developerInstallation="true"/>
</runtime>
In Windows 2008 R2, Windows 7, or Windows 2003 System Properties, click the Advanced tab > Environment Variables.
Create a new System variable called DEVPATH and assign the value:

C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib

Note: For 32-bit operating systems, replace Program Files (x86)with Program Files.

You can now launch vSphere Client from a Windows 7, Windows 2003, or Windows 2008 R2 machine. You may have to right-click on the vSphere Client icon and choose Run as administrator.

THE CONTENT OF THIS ARTICLE IS PROVIDED "AS-IS," AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, VMWARE DISCLAIMS ALL OTHER REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, REGARDING THIS CONTENT, INCLUDING THEIR FITNESS FOR A PARTICULAR PURPOSE, THEIR MERCHANTABILITY, OR THEIR NONINFRINGEMENT. VMWARE SHALL NOT BE LIABLE FOR ANY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF THIS CONTENT, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF VMWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Additional Information

vSphere Client does not open on any Windows operating systems with the error: parsing the server "<servername>" "clients.xml" file
Não é possível iniciar vSphere Client após a instalação no Windows 7, Windows 2003 ou Windows 2008 R2
vSphere Client を Windows 7、Windows 2003 または Windows 2008 R2 にインストールした後、起動できない
无法在 Windows 7、Windows 2003 或 Windows 2008 R2 中启动 vSphere Client