view 4.6 client runtime error

[CianoKuraz]

Hi

absolutely random i get this error on some view 4.6 desktops part of the same pool:

Clicking ok lets you put your domain username and password but on the next step you get the error that is impossible to connect to domain controller due to incativity.

On windows logs i founded:

vmware-svi-ga.exe terminate in unusual way.

A single recompose not solved the problem.

Sometimes, and on ly on some clients, trying multiple recompose seems to solve the problem.

No activities done before the problem appeared.

really cannot figure out how to solve it.

All vmware view/vsphere components are up to date.

Any tips?

thx

[mpryor]

That doesn't look good, it's the first time I've seen the process crash like that. Since the process is crashing I think you need to open a support request so that we can figure out what the cause is and fix it, support will most likely ask you to generate a process dump to help them identify this.

The process that is crashing is responsible for customizing the VM and joining it to the domain during quickprep, along with updating the machine password used in AD, so if it's crashing halfway through that process it's certainly possible that the other things you've seen are additional side effects.

[CianoKuraz]

Ok thank you,

i'll open a SR immediatly .

bye

Alan

[IP2008]

Hi,

Did you get a resolution on this from VMware? We are running View 4.5 and after a recompose of a pool of, 2 of the VM's are giving this error and not completing the recompose. The other VM's recomposed fine.

Thanks

[CianoKuraz]

well, not exactly

i mean, nothing usefull was found on logs,

but i've noticed that, for some unknow reason, the scsi bus was setted to buslogic, instead of LSI logic, as suggested by vmware.

so i've changed the scsi bus type, and tryed a recomose again. This time all worked perfectly.

hope this will help you.

if u need ant further informatio on changing the scsi bus just ask

bye

Alan

[IP2008]

Just changed to LSI Logic SAS and tried a recompose but the error is still there.

If anyone else has any suggestions they would be welcomed?

Thanks

[CianoKuraz]

The error still persist on View 5..really don't know what to think..

[Linjo]

Did you open an SR? Please post the SR-number.

// Linjo

[CianoKuraz]

Hi,

yes sure

the SR is 11067576805 but was closed on 23/05/2011

thank you

[ZebS]

Have a look here http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=102777...

[Sergei13]

I have the exact same error message with an XP linked clones pool.

This happens on occasions, fortunately not too often. I usually delete the machine from the admin and it recompose.

Since I have all the patchs described in the KB on muy master, any other idea ?

Thanks.