VMware Cloud Community
einstein-a-go-g
Hot Shot
Hot Shot

The type initializer for threw an exception for 'VirtualInfrastructure.Utils.ClientsXml' threw an exception.

When running VI Client 4 or 4 U1, on Vista SP1 x64, I get the following error message.

The type initializer for threw an exception for 'VirtualInfrastructure.Utils.ClientsXml' threw an exception.

and the VI Client exists.

Any ideas, I've found similiar with users running on Windows 7, I've followed those treads, but it still gives me the error message, VI Client used to work, but has stopped.

e.

27 Replies
Troy_Clavell
Immortal
Immortal

there was a M$ .net patch that broke the vSphere Client. It may be worth looking at the KB article below

The below KB article may be worth looking into as well and it references the above KB

http://kb.vmware.com/kb/1011329

Reply
0 Kudos
einstein-a-go-g
Hot Shot
Hot Shot

yes, I knew this, hence why I'm using U1!

version=4.0.0, build=build-208111

e.

Reply
0 Kudos
einstein-a-go-g
Hot Shot
Hot Shot

my error message is subtly different.

if I have to install it in a VM on the client I will or use another laptop, but it just puzzles me why it doesn't work!

Reply
0 Kudos
Troy_Clavell
Immortal
Immortal

yes, I I know you are running U1. However, it may not hurt to check to see if the .net patch has been installed onto your workstation, and either remove it or look into the workaround posted in the second KB. Or if all else fails, have to tried to re-install the client?

Reply
0 Kudos
einstein-a-go-g
Hot Shot
Hot Shot

yep, uninstalled, re-installed.

the wierd thing is it manages 2.5 (old virtual center fine!), just will not connect to vcenter or ESX 4i.

Reply
0 Kudos
Troy_Clavell
Immortal
Immortal

yes, but when connecting to a VI3 environment the client downgrades itself. Check the help--about. You'll see a different build.

Reply
0 Kudos
einstein-a-go-g
Hot Shot
Hot Shot

kb980773 is specific only to WinXP and Win2k3 and not Vista.

e

Reply
0 Kudos
einstein-a-go-g
Hot Shot
Hot Shot

oh well, that explains that!

umm, looks like more incompatible software witrh x64!

e...

Reply
0 Kudos
Troy_Clavell
Immortal
Immortal

Vista Enterprise and Business x64 are the only compatible Vista x64 OS's that will work with the vSphere4 Client. I'd have to assume you are running one of the two

http://www.vmware.com/pdf/vsphere4/r40/vsp_compatibility_matrix.pdf

Reply
0 Kudos
einstein-a-go-g
Hot Shot
Hot Shot

yep, Business x64, it's weird because it used to work, and has just stopped recently. in May 2010. I've just been picking up my netbook or laptop to manage clients and our ESXi farms.

it's just my workstation has a much larger screen and quad desktops! (for multiple VM working!)

e

Reply
0 Kudos
ealaqqad
Enthusiast
Enthusiast

Hi All,

You might want to look into KB980773 and remove it or get the latest vSphere client which should fix this problem. Please look at my following post for more details:

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[http://www.TSMGuru.com]

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

This issue has returned.  I'm running the newest version of vSphere (downloaded and reinstalled today).  My x64 Win7 box started generating this error last week, possibly due to MS updates, but I haven't been able to narrow it down.

Any help would be much appreciated.

Reply
0 Kudos
MaxWyatt
Contributor
Contributor

Also,  I have just fully updated an x32 Win7 client and seems uneffected.

Reply
0 Kudos
bschmeltz
Contributor
Contributor

I was also having this problem and after much research it appears that this is a very wide spread sporadic issue and it isn't always the same cause.  What I have found is you may also get this same error on Windows 7 using client 5.1 and it is being caused by the UAC, so you can either turn UAC off (if allowed by your company policy) or you can "run as administrator" everytime you need to launch vSphere.  Hope this helps.

Ermakov20111014
Contributor
Contributor

I had the same problem after I cleaned my pc with desinfect. I tried all suggestion the only thing what helped was an repairintall of Win7.

Reply
0 Kudos
GeraldBegin
Contributor
Contributor

It's in relation with Internet Explorer and your xml tmp folder profile.

If you open Internet Explorer, your vSphere Client will work.  🙂

____________

Gerald Begin

Reply
0 Kudos
einstein-a-go-g
Hot Shot
Hot Shot

thanks for reply, with IE open, it still fails, when trying the vSphere Client with same error message as posted.

Reply
0 Kudos
GeraldBegin
Contributor
Contributor

Strange, . it works for me.  hmmm ...

Even if you re install the vSphere Client ?

Are you full admin of your PC ?  Did you try with a new user profile on your machine ?  Maybe a beginning of a Corruption profile and you loose rights on folders.  Try this and let me know.  🙂

thanks

________________

Gerald Begin

Reply
0 Kudos
einstein-a-go-g
Hot Shot
Hot Shot

Yes, full Admin rights on PC, happens with all profiles, profiles are not corrupted. All Admin users that log on...

oh yes, re-installed the vSphere Client, on 5.5 now, and still the same, after every new client comes out, we uninstall and re-install in hope one day, it will be fixed.

I seemed to remember ths happened after a bunch of Windows updates, a long time ago, we use vSphere Client remotely now, and it's going away now with 5.5./Web Client....

thanks for trying, many VMware Admins have spent many hours over the years, in their "spare time" trying to fix, with no solution yet!

One day the PC will be retired, but not yet..

Reply
0 Kudos