Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

Search the VMware Knowledge Base (KB)

View by Article ID

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

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 vSphere Client does not open on any Windows operating systems with the error: parsing the server "<servername>" "clients.xml" file (1022611).

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.

You can download and install the VMware vSphere 4.0 Update 1 from the download page.

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.

This Article Replaces

1014316

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

1 2 3 4 5

1 2 3 4 5

Actions

Bookmark Document

Did this article help you?
This article resolved my issue. This article did not resolve my issue. This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)