We help IT Professionals succeed at work.

VMWare 4 Error parsing the servers clients.xml file

BCHCAdmin
BCHCAdmin asked
on
27,447 Views
Last Modified: 2012-06-22
Just today when I tried logging into the vcenter client (VMWare 4) I am getting an error that says: "Error parsing the server xx.xx.xx.xx Clients.xml file".   I was in a few days ago to it.  I am running Windows XP on my client - the vcenter server is a windows server 2008 VM.   I read somewhere it may be related to a windows update?  Anyone have any ideas?
Comment
Watch Question

Joseph GanSystem Admin
CERTIFIED EXPERT

Commented:
Have you installed VMware ESX / ESXi 4.0 Update 1 ?
This problem has been solved!
(Unlock this solution with a 7-day Free Trial)
UNLOCK SOLUTION

Author

Commented:
Thanks - that resolved the problem.

Commented:
Is there not a vmware fix for this issue? Surely we're not expected to play the shell game with various MS patches and versions of the vsphere client?

btw, removing KB980773 worked for me...
If you are running a version of the vSphere client from Update 1 or later you were not affected.  This was the same error seen with the original version of the vSphere 4 client with x64 operating systems.

Here is the official VMware response (KB article) to the issue:

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

Commented:
I just updated my computer this morning and received the same PARSING error described in this thread. Removing update:  KB980773  worked for me as well.

Thank you.
Thanks a lot!
Worked like charm. Removing this KB worked for me. Have to exlude from WSUS update.

Commented:
Removing the update fixed it for me too.  Thanks!

Commented:
thanks.  repped
Top Expert 2010

Commented:
Just a minor correction - it was a .NET 2.0 SP2 KB/patch, not .NET 3.0 SP2. I couldn't find it on mine until I selected 'updates' in Add/Rem pgms. It wasn't under the .NET 3 install, but .NET 2. Just wanted to clarify to assist others who may need it.

Regards,
~coolsport00
Download the vsphere 4.0 update 1 or update 2 client from www.vmware.com and install it. This issue is fixed in the client version of vsphere 4.0 u1 & 4.u2.

Kind regards,
Sandy