any idea why I'm getting this errors:
Error parsing the server "SERVER IP" "clients.xml" file. Login will continue, contact your system administrator.
and after pressing OK buttom I'm getting another error:
The type initializer for "VirtualInfrastructure.Utils.HttpWebRequestProxy" threw an exception
when I try to connect to ESXi 4.0 with vSphere client?
My clients.xml file contents (https://SERVER IP/client/clients.xml):
<ConfigRoot> \\ <clientConnection id="0000"> \\ <authdPort>902</authdPort> \\ <version>4</version> \\ <exactVersion>4.0.0</exactVersion> \\ <patchVersion>1.0.0</patchVersion> \\ <apiVersion>4.0</apiVersion> \\ <downloadUrl>https://*/client/VMware-viclient.exe</downloadUrl> \\ </clientConnection> \\ </ConfigRoot> \\
Just got off the phone with VMWare and it is fixed in v4 update 1, and it does appear that the recent Windows updates breaks it for Server 2003 and XP at the very least. Workaround is to not install June Windows updates. Solution is to update VMWare to v4 update 1.
This might be stupid, but how do I update my Virtual Center Server and VI Client? I'm running my Virtual Center Server on Windows Server 2008 Standard 32 bit, and getting the same errors.
Hmmm... I'm running vcenter on XP, and 2 clients on XP. One client without the June 9 Windows updates can still get to vcenter using the client, and one with the updates can't. That fits the recent pattern so far, but I just got finished updating the vcenter machine and the client on the non-working workstation, but still no dice. What am I missing?
I have the same problem with my Vsphere on XP since yesterday and the windows' update.
But the server is ESXi 4 Single Server #1 SMP Release build-171294 Jun 11 2009 12:44:08.
And when I tried to use VMWare infrastructure Update to update my server, I got this response : "No updates available". Then How can I resolve this issue ?
ok, I have tried to use the KB 1022611. But I always have the error message concerning the licensing :
VMware ESXi 4 Update 2 Installable
Sorry, at the moment you are not authorized to download VMware ESXi 4 Update 2 Installable. You have the following options:
If you have a valid serial number of VMware ESXi 4 Update 2 Installable and you have not registered it, please register it here, so you can get download access.
If you want to get more information about VMware ESXi 4 Update 2 Installable, please contact the VMware Sales department per email or telephone 1-877-4-VMWARE.
And I tried all editions and I obtained always the same response although I have an account with my licence number. I don't understand.
I finally resolved my issue : I have applied an update to vsphere (VMware-viclient-all-4.0.0-208111.exe). But I am not sure I will be able to retrieve the way to download this file if needed. The vmware licencing is very difficult to understand.
We use also Windows XP (SP3) and this week, the same issue "appeared" to us. So I think it has nothing to do with Windows Version (XP, Vista, 7, XP compatibility mode etc).
I assume this has something to do with a Windows Update. I haven't discover anything more specific yet.
Please if anyone comes up with any work arround for it, reply.
After a recent update to .net framework this problem also affected Vista clients also. I tried many of the fixes posted within the forums many where missing a few little details. I eventually tried a fix by Fernando which worked on both Win7 and Vista (not tried and XP clients yet), I wish to thank Fernando for his fix wish I'd tried that one first than spending 2 days on this (including an upgrade from Vista to Win7 to replicate the environment everyone else in this thread talks about. THIS FIX DOES WORK.
Below I have attached the 3 files you need (already configured) and the basic instructions needed, plus Fernando's original fix post.
vShere Client will come up with the following error (this is vista and windows 7):
error parsing the server (ip address) clients.xml
The fix is as follows:
1. Download the 3 attached files.
2. Navigate to - %ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\
3. Copy and replace VpxClient.exe.config file from your download folder into the above folder.
4. Copy the file VPXClient.cmd from your download folder into the folder at step 2.
5. In the folder at step 2 create a new folder called Lib.
6. Copy the file system.dll from your download folder into your newly created Lib folder.
7. Edit the vSphere Client desktop shortcut target to - "C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VPXClient.cmd"
8. In the 'Run:' drop down box select 'Minimized'.
9. Run the programme from the shortcut all should be good.
THE ACTUAL CREATION OF THE FIX FROM START TO FINISH IS BELOW: (By Fernando)
Here's a possible workaround for this problem.
1. Obtain a copy of %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\System.dll from a non Windows 7 machine that has .NET 3.5 SP1 installed.
2. Create a folder in the Windows 7 machine where the vSphere client is installed and copy the file from step 1 into this folder. For example, create the folder under the vSphere client launcher installation directory (%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib).
3. In the vSphere client launcher directory, open the VpxClient.exe.config file in a text editor and add a
3. Create a batch file (e.g. VpxClient.cmd) in a suitable location. In this file add a command to set the DEVPATH environment variable to the folder where you copied the System.dll assembly in step 2 and a second command to launch the vSphere client. Save the file. For example,
SET DEVPATH=%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
"%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe"
4. (Optional) Replace the shortcut on the start menu to point to the batch file created in the previous step. Change the shortcut properties to run minimized so that the command window is not shown.
You can now use the VpxClient.cmd (or the shortcut) to launch the vSphere client in Windows 7.
Note that this workaround bypasses the normal .NET Framework loading mechanism so that assembly versions in the DEVPATH folder are no longer checked. Handle with care.
I don't know why everybody went off on a tangent. This problem has nothing to do with Windows 7. I have a VMware client which has been running fine for months on a Win2k3 machine and it suddenly had this same problem today. All I can think is a MS update broke it but again: Has nothing to do with Win7.
I don't have a solution yet as I'm still investigating. Just wanted to share this with you all.
As I said earlier in this thread (in an official capacity), this problem is addressed here:
VMware KB Article 1022611
Social Media Specialist