.NET Patch Breaks vSphere Client

[jason331]

I'm hoping someone else runs into this problem and comes up with a fix because I'm out of ideas. Microsoft's patch Tuesday was today and one or more of the Windows Updates breaks the vSphere client that connects to ESXi servers. I have verified this on multiple different workstations with different operating systems. The specific error I get when I try to login to my ESXi server from my Windows XP SP3 workstation is:

"Error parsing the server "myserver.mydomain.com" "clients.xml" file.

Login will continue, contact your system administrator."

and...

"The type initializer for 'VirtualInfrastructure.Utils.HttpWebRequestProxy' threw an exception."

I know this error has been around a long time and there are workarounds for Windows 7 but in this case it happens from my XP workstaion (main workstation), a 2008 server, and a Vista machine. I checked the updates that were installed today and the following ones seem to be the culprit(s):

• KB976765

• KB97990

• KB980773

• KB976769v2

I uninstalled those hotfixes and rebooted. I still get the same first error but the second error that pops up is now:

"Error creating the Web Proxy specified in the 'system.net/defaultProxy' configuration section"

Note that I can connect from a non-updated workstation so I am positive it was one of the Windows Updates that broke my vSphere client. Any suggestions or ideas would be greatly appreciated.

[mikeyr]

its FREE, they will do it when they get around to it. There are several workarounds for it already, like removing the bad update so that removes the "hurry" factor for them.

If you are using the FREE version like I am, its probably not a real business and you can wait a while and if you are a real business and using the FREE stuff, then you are getting what you are paying for. I just removed the update and continued to work.

[computech911]

The thing I take issue with is that vmware SAYS they have an update for the free version of ESXi and even POSTED a download link (see previous post). The fact that this is just a tease to waste my time makes me irritated.

[ceri]

Um, that's the version that you want. Read the KB again; no, actually read it.

[computech911]

Um no it is not. The paid version has the correct link, the free version does not. Please see my screenshot as it still applies.

[lhcrnetadmin]

That looks like vsphere client 4.0.0. 208111 to me.

Whats the problem with that?

[ceri]

If you would pick up your toys and follow me along, I'll go through it slowly for you.

You said: "the only download that is available is the OLD version which is incompatible with the new .NET update".

The KB article says that the problem will go away if you install "vSphere Client 4.0 Update 1".

Your screenshot shows "vSphere Client 4.0 Update 1".

Conclusion is an exercise for the reader, if you bothered to read this far.

[computech911]

Here is another screenshot... maybe now you will realize there are MORE than ONE build for update 1.

[lhcrnetadmin]

The download link that you posted works for me.. The file is 208111.

[ceri]

Nice try, that's not the same screenshot that you initially posted and clearly says version 4.0.0.

[lhcrnetadmin]

I would have to agree with ceri. You've posted 2 different screenshots. Maybe you have some links confused.

[osham22]

I had the exact same errors. I uninstalled / reinstalled both the .NET patch and the 208111 build several times and kept getting the same error. After I found that it was working fine for another user on the same machine I started looking at my user.

In the end the desktop shortcut I was running it from had the Run this program in compatibility mode for Windows 2000 turned on. No idea how or when that got there, but turning that off fixed my problem instantly.

[ealaqqad]

Hi Osham,

Ensure that you don't have KB980773 installed, else remove it. You can check my following post for more details on this issue.

KB980773 Breaks vSphere Client

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

[swalters]

@ Osham22:

Oh man, thank you so much. I have gone through every post imaginable to find out why I have had this issue for months on a Windows XP box that was deemed to be the one to use for the vsphere client. I gave up and utilized a Windows 2003 Server. For some reason, and I have no idea how it happened but, mine was also set to run in Windows 2000 compatibility mode. Unchecked the box and walla!