Clients.xml Error Vsphere Client

following errors to be displayed and does not allow you to connect....   Error parsing the server "SERVER IP" "clients.xml" file. Login will continue, contact your system administrator.   Note: This issue is now fixed... From VMware: "If the build number for your vSphere Client is 208111 or higher, then you have vSphere Client Update 1 or later, and should not be affected by this issue." Press OK, and https://kb.vmware.com/kb/1011329 another error will be displayed. The type initializer for "VirtualInfrastructure.Utils.HttpWebRequestProxy" threw an exception.   There is currently no official fix from VMware for this, so for now the following unsupported workaround allows it to work.     1. On the Windows 7 computer create a folder named: "%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure https://www.vmadmin.co.uk/resources/36-virtualcenter/148-vsphereclientserrxml Client\Launcher\Lib+"   2.On a Windows XP or Vista computer with .Net 3.5 SP1 installed: Copy "%SystemRoot%\Microsoft.NET\Framework\v2.0.50727\System.dll" to the "Lib+" folder on your Windows 7 computer.   3. Run the vSphere client in developer installation mode: Edit"VpxClient.exe.config" adding the following: ...   4.Create a batch file named "VpxClient.cmd" in the same folder as "VpxClient.exe.config".   5. Add the following line to the "VpxClient.cmd" file: SET DEVPATH=%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib "%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe"   6. Modify the start menu shortcut. Change the shortcut to to point to the batch file "VpxClient.cmd".       Note: This issue is now fixed... From VMware: "If the build number for your vSphere Client is 208111 or higher, then you have vSphere Client Update 1 or later, and should not be affected by this issue." Note: Please beaware this is not supported by VMware.       Share this blog pos

WindowsWindows 10 Windows Server 2012 Windows Server 2008 Windows Server 2003 Windows 8 Windows 7 Windows Vista Windows XP Exchange ServerExchange Server 2013 Exchange Server http://windowsitpro.com/virtualization/q-how-do-i-fix-error-parsing-server-servername-clientsxml-file-when-opening-vsphere-c 2010 Exchange Server 2007 Exchange Server 2003 Outlook Unified Communications/Lync SharePoint Virtualization Cloud Systems ManagementSystem Center PowerShell & Scripting Active Directory & Group Policy Mobile Networking Storage TrainingOnline Training IT/Dev http://serverfault.com/questions/44946/how-do-you-get-the-vmware-vsphere-client-to-work-on-windows-7-rc Connections Webcasts VIP Library Digital Magazine Archives InfoCentersIT Innovators Mobile Computing Business Now Desktop VDI All About Converged Architecture Advertisement Home > Virtualization > Q: How do I fix "Error vsphere client parsing the server "" "clients.xml" file." when opening the vSphere client? Q: How do I fix "Error parsing the server "" "clients.xml" file." when opening the vSphere client? Mar 9, 2011 Greg Shields | Windows IT Pro EMAIL Tweet Comments 0 Advertisement A: This error message occurs when the vSphere Client won't start on any Windows OS. A second the type initializer error message may also appear: "The type initializer for VirtualInfrastructure.Utils.HttpWebRequestProxy' threw an exception." If either of these error messages occur and the vSphere Client won't start, you must update your vSphere Client to Update 1 or Update 2. vSphere Clients with build numbers greater than 208111 shouldn't be affected by this problem. You can determine your build number by viewing the first line of the viclient.log file, which is found at %USERPROFILE%\Local Settings\Application Data\VMware\vpx. Print reprints Favorite EMAIL Tweet Please Log In or Register to post comments. Advertisement Related ArticlesQ. I'm upgrading from VMware Infrastructure 3.X to vSphere 4. What edition can I legally upgrade to? Q: What memory resource management tactics does vSphere 4.1 employ? Q: What's an appropriate memory size for a vSphere virtual machine (VM)? Q: How do I fix "Error parsing the server "" "clients.xml" file." when opening the vSphere client? Q. I'm trying to run the WMware vSphere Client on Windows 7, but I get an error parsing the clients.xml file and login fails. What's wrong? John Savill's Microsoft Stack Master Clas

Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top How do you get the VMWare vSphere client to work on Windows 7 RC? up vote 4 down vote favorite 1 When trying to connect to a ESXi server using the VMWare vShere Client I get an error: Error parsing the server "server" "clients.xml" file. Login will continue, contact your system administrator. Followed by: The type initializer for 'VirtualInfrastructure.Utils.HttpWebRequestProxy' threw an exception. Any clues to fix this? Windows 7 x64 RC Build 7100 vSphere client from ESXi 4.0.0 ReleaseBuild-171294 Thank you, Keith vmware-esxi vsphere-client share|improve this question asked Jul 24 '09 at 3:22 Keith Sirmons 54531223 add a comment| 8 Answers 8 active oldest votes up vote 0 down vote accepted Theres a update of the VMware vSphere Client and Host Update Utility available now directly from VM that fixes this issue without hacking your OS. Look for Version 4.0 Update 1 | 208111 - 11/19/09 share|improve this answer answered Jan 15 '10 at 14:27 Andy Davies 28916 2 Linky - downloads.vmware.com/d/details/esx40u1_a/ZHcqYmRqampiZGUlaA=‌= –Chopper3 Jan 15 '10 at 14:30 add a comment| up vote 2 down vote There is a thread on the VMware communities site that details the troubles with getting it working as well as workarounds http://communities.vmware.com/thread/211440 There is a solution in that thread involving .NET assemblies, etc. share|improve this answer answered Jul 24 '09 at 3:31 Kevin Kuphal 8,14812441 add a comment| up vote 1 down vote Because this took me ages to figure this out, mainly because I didn't read the second page of the thread here are the steps for Windows 7 x64, taken almost entirely from here. On a non Winodws 7 64-bit install of windows %SystemRoot%\Microsoft.NET\Framework64\v2.0.50727\System.dll to C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastruc