Another VMware error...

[somecanadianguy]

[10:52:46] 
[10:52:46] + Processing work unit
[10:52:46] Core required: FahCore_a2.exe
[10:52:46] Core found.
[10:52:46] Working on Unit 08 [October 25 10:52:46]
[10:52:46] + Working ...
[10:52:46] 
[10:52:46] *------------------------------*
[10:52:46] Folding@Home Gromacs SMP Core
[10:52:46] Version 2.10 (Sun Aug 30 03:43:28 CEST 2009)
[10:52:46] 
[10:52:46] Preparing to commence simulation
[10:52:46] - Ensuring status. Please wait.
[10:52:55] - Assembly optimizations manually forced on.
[10:52:55] - Not checking prior termination.
[10:52:56] Couldn't Decompress
[10:52:56] Called DecompressByteArray: compressed_data_size=4578816 data_size=24052157, decompressed_data_size=0 diff=24052157
[10:52:56] - Fatal: Could not decompress work unit data
[10:52:56] Error: Could not open work file
[10:52:56] 
[10:52:56] Project: 1862926336 (Run 419430400, Clone 218103808, Gen 1929379840)
[10:52:56] 
[10:52:56] Error: Could not write local file.  Exiting.
[10:52:56] - Shutting down core

Getting that error on one of my VMware clients.
Anyone know what's going on and how to fix it?

[stoanee]

Delete work unit, queue, logfile, unitinfo and try again? I had some a while ago and I had to do all of the above, plus the core, then reboot my computer before restarting the VM. It kept repeating but eventually gave me some good work units.

[somecanadianguy]

I've done that at least 10 times... still no luck.
Then I just gave up.
Going to play some GTA4 for a while now (that'll get my frustrations out).
I'll try and get the client working again in a while.

[somecanadianguy]

Still having the problem today on the one client

[lemonlime]

I'm having the exact same issue, did you ever find a solution?

[chrisk]

Did you try the solutions mentioned in stoanee's post?

If that does not work you could try the 'nuclear' method and just delete the whole vmmachine, and setup from scratch.

[lemonlime]

Originally Posted by chriskwarren

Did you try the solutions mentioned in stoanee's post?

If that does not work you could try the 'nuclear' method and just delete the whole vmmachine, and setup from scratch.

I did, unfortunately nothing worked, so I went with the nuclear method as you mentioned

Seems to be up and running once again. Hopefully it won't stop.