I also tested this in our Q environment out of curiousity.
Its a VMware ESX Virtual Machine with 2 vCPUs and 4gb RAM. Underlying hardware has 4 x 12-core AMD cpus (48 logical cores) and 256gb of RAM, though that shouldn't matter as I think the issue would be contained
I didn't try this by changing our Q server to only have 2gb of ram, as i'm wondering if you're running into memory/paging issues. Not sure if the process consumes a ton of memory while compressing or not, though I didn't notice any issues on mine.
I tried a 1.4gb file and a 800mb file separately, and at the same time and it worked the 4 times I tried it. Normal Compression.
OS: Windows 2008 Server Standard R2, fully patched/updated
Antivirus: Symantec Endpoint Protection v12
Erik, did you mean 'Server 2003 R2 w/SP2' ? Never heard of 'SE', just curious.
Also, since its 2003, is it 32-bit or 64-bit ?
I'm going to try and reproduce this exactly, short of 100% identical hardware. Does your VC install run as a service account or does it use the default 'Local System'? What path is VC installed to on Drive F?
EDIT:
I just tried a Single CPU, 1gb RAM, 32-bit 2003 Standard R2 w/SP2, virtual machine running VC 6.1.3 ProdRelease, and compressed the same 1.4gb and 800mb files twice, all is well. Now my question is, are the failures consistent for you or is it completely random on those 3 files you mentioned?
Brian
Edited by user
2012-10-30T14:38:32Z
|
Reason: Not specified