Highlighted
Contributor
Contributor

Error parsing the server clients.xml file - after Windows XP update

Jump to solution

After a lot of Googling, all discussion of this "Error parsing the server clients.xml file" is centered around problems in Windows 7 before the latest upgrade. But i'm at v4.0 on Windows XP and it was working fine for several months ... AFter that latest round of XP updates a few days ago, i'm getting the parsing connection problem now and a reinstall of the client didn't change anything.

More accurately, i had used the client to connect to ESXi machine, then was downloading a large vmdk to the local computer from the datastore and it was aborted in the wee hours at 67% complete, and when i discovered it in the morning, the local PC had been restarted, with the Windows system tray alert "Windows had to install an important update and restart your computer" etc. I also restarted the management agents on the ESXi machine, to no avail.

Have not tried restoring to an older restore point yet - ultimately need to keep the machine updated to latest windws stuff. I can hit the ESXi machine from another XP computer adjacent to the problem computer, same vlan, etc. using the Virtual Client, no problem.

The logs show that the error comes from a check of the clients.xml file (presumably on ESXi) resulting in an "ambiguous match". Uninstalling the vSphere client must leave registry info behind, or the ESIi machine is remembering something about my local computer's connection to it somewhere ...

-steve

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Contributor
Contributor

here's your problem

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=102261...

If you found this or other information useful, please consider

awarding points for "Correct" or "Helpful".

Gregg Robertson, VCP, MCSE, MCSA, MCTS, MCITP

View solution in original post

0 Kudos
4 Replies
Highlighted
Contributor
Contributor

here's your problem

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=102261...

If you found this or other information useful, please consider

awarding points for "Correct" or "Helpful".

Gregg Robertson, VCP, MCSE, MCSA, MCTS, MCITP

View solution in original post

0 Kudos
Highlighted
Contributor
Contributor

You nailed it. I suspected .net updages, since one hosed my digital audio production software a year ago, but didn't see anything on that page when i was there a couple days ago and nothing in Google that i could find. Good eye.

0 Kudos
Highlighted
Contributor
Contributor

This SOLUTION worked perfect for me as I couldn't find an update to my build of Vsphere client since I have XP.

http://www.evanhoffman.com/evan/2010/06/23/vcenter-error-parsing-the-server-clients-xml-file/

"I got the above error today after running Windows Update on my XP VM a

few days ago. A quick search showed that the error is caused by a

Microsoft update to the .NET framework. To resolve it, remove update

KB980773 (Add/Remove programs, make sure “Show Updates” is checked;

KB980773 is under “Microsoft .NET Framework 2.0 Service Pack 2″). I

removed it and was able to log in without problems. "

0 Kudos
Highlighted
Enthusiast
Enthusiast

Hi,

It seems the solution is as crankinrankin to remove the KB980773, or the other option will be to download the latest vSphere client as VMware has already resolved that in the latest client. You can found more details on this at my post:

vSphere Client Error parsing the server “SERVER IP” “clients.xml” file. Login will continue, contact...

I hope this help some one, if it does please reward points.

Enjoy,

Eiad Al-Aqqad

System X & Storage Technical Specialist

Founder of http://www.VirtualizationTeam.com

Founder of

Regards, Eiad Al-Aqqad Technology Consultant @ VMware b: http://www.VirtualizationTeam.com b: http://www.TSMGuru.com
0 Kudos