Atmos4
Enthusiast
Enthusiast

vSphere Client Exception 0xc0000005 at exit

Hi,

since upgrading to vSphere, the vSphere Client crashes with the following error, when exiting the application:

VMware Infrastructure Client unrecoverable error: (app)

Exception 0xc0000005 (access violation) has occured.

Please request support.

To collect data to submit to VMwar support, run "vm-suuport".

Thing is, there's no vm-support.exe anywhere on the machine (I only know vm-support from the linux COS of ESX) ...

Using vSphere Client and Server 4.0.0.162856 on Windows Server 2003 Standard SP2 x86 English.

Client is run with the following parameters:

VpxClient.exe --locale en_US --PassthroughAuth --server

Regards, Felix

Tags (3)
0 Kudos
34 Replies
RAMESA
VMware Employee
VMware Employee

Hi Felix,

There won't be vm-support on vCenter Server it will have vc-support.

What you can do is go to Start->Programs->VMware-> Generate vCenter Support Server log bundle

This will collect the logs and put it in zip file on desktop upload that.

One question i have is - If you open vSphere client directly from desktop with out any parameter does it work fine? or still there is an issue?

Regards,

Ramesh

Regards, Ramesh
monkeyhou2000
Contributor
Contributor

Hi:

Did you upgrade vSphere Client from Beta to GA?

We are not supporting any vSphere Client upgrade. VIClient is just coexistence no upgrade.

Please try to connect vSphere Center Server using fresh installed vSphere Client GA to make it sure.

Thanks.

Frank H

0 Kudos
fduranti
Hot Shot
Hot Shot

I've exactly the same problem running the client at least on Windows Server 2008 64 bit. It's a clean installation (it happen also on the vcenter server itself when running the client).

Francesco

0 Kudos
Atmos4
Enthusiast
Enthusiast

@monkeyhou2000: I upgraded from vCenter 2.5u4 to vSphere final, so I never had the beta installed. The build numbers posted above also indicate I'm using the most recent available build.

0 Kudos
williamz
VMware Employee
VMware Employee

This looks a problem that is not always reproducible (or producible in some rare case). Some very similar issue had been tracked before and is resolving, once we have update will get back here.

Thanks for your report.

0 Kudos
zapnet
Contributor
Contributor

Hello,

I have the same problem with the new vSphere Client.

Using vSphere Client and Server 4.0.0.162856 on Windows XP SP3 x86 german.

and the same parameter

VpxClient.exe --locale en_US --PassthroughAuth --server <vcenter hostname>

When i disable the vCenter Converter Plugin 4.1.0 it works fine.

Regards, Oli

Atmos4
Enthusiast
Enthusiast

One question i have is - If you open vSphere client directly from desktop with out any parameter does it work fine? or still there is an issue?

It also crashes at exit when launching through the default desktop icon.

0 Kudos
AndreTheGiant
Immortal
Immortal

Which versions for .NET Framework do you have?

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
williamz
VMware Employee
VMware Employee

>> When i disable the vCenter Converter Plugin 4.1.0 it works fine.

This a light. We are looking into this. Thanks!

0 Kudos
Atmos4
Enthusiast
Enthusiast

Which versions for .NET Framework do you have?

.NET 2.0 SP2

.NET 3.0 SP2

.NET 3.5 SP1

I can also see, taht viClient is no longer crashing when the converter plugin is disabled (it crashed at the end of the sessio where I switched the plugin to disabled, but not in consecutive open-exit cycles).

Would attaching the viclient.log of a crashed session help?

0 Kudos
AndreTheGiant
Immortal
Immortal

Would attaching the viclient.log of a crashed session help?

Yes

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
faster4233
Contributor
Contributor

Seems you are correct about the converter. Works fine on my 32bit server but not on my 64bit, both running server 2003. Disabled it on x64 and the error disapears.

Guess they havent sorted all the x64 bugs yet.

0 Kudos
Atmos4
Enthusiast
Enthusiast

Guess they havent sorted all the x64 bugs yet.

The problem is not specific to x64, I was statring the client on the vcenter server, which was running W2K3 SP2 32-Bit.

0 Kudos
Atmos4
Enthusiast
Enthusiast

Would attaching the viclient.log of a crashed session help?

Yes

Anonymized log attached.

0 Kudos
Hydropower
Contributor
Contributor

i have the same problem Smiley Sad any solution?

0 Kudos
faster4233
Contributor
Contributor

Havent seen anything yet. It doesnt actually seem to make any difference to the operation of the system that i have seen though. Saying that i havent used the VSphere Client to convert Hosts yet.

I'm currently just ignoring it as i convert most machines from a Cold Conveter CD. If you want to stop the error just disable the Converter Plugin in the VSphere Client.

0 Kudos
AviH
Contributor
Contributor

i have the same problem

there is any solution ?

0 Kudos
Atmos4
Enthusiast
Enthusiast

yea, wait for an update Smiley Wink or disable the converter plugin as mentioned before.

0 Kudos
JudgeB
Contributor
Contributor

Think I know the cause of this one. It's to do with Regional Settings!

If you change the regional settings on your machine to "English (United States)" under 'standards and formats' you should find that the vSphere client no longer crashes with the Converter plugin enabled.

I just discovered this was the case and have raised a ticket with VMware.

Judge

0 Kudos