Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

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

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 168321Language:
Chinese (Simplified)Portuguese (European)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

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>

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.

Related 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

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (European)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
ESXi 4.x/5.x に VMware Tools 用の RPM 形式が含まれていない (1024047)

KB
•
SNMP 陷阱的团体字符串中的特殊字符不会保留 (1023998)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware VirtualCenter

VMware vCenter Server

VMware ESX Server

Related Versions:

VMware VirtualCenter 2.5.x

VMware VirtualCenter 2.0.x

VMware vCenter Server 4.0.x

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESX 4.0.x

Take Our Survey

Copyright © 2024 VMware, Inc. All rights reserved.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant