I'm getting this weird error on 3 of 200 of this type of computer. The error is FDICopy ( ) failed: code 11 [User aborted] and I can't figure out what it is. I've searched Google and all I can find is something to do with a file that doesn't even exist on my system. These machines are very limited on what users can do, so no deletion of files has taken place. Any ideas?

Error occurs under what circumstances? M2

It just randomly pops up while users are at the computer. We're running a security program called Fortres to keep students from entering the start menu, My Computer, deleting files, etc. Symantec AntiVirus Corporate is also installed.

Dunno, but did you look in Google "Groups" too? I see someone reckoned they cured it by re-installing IE (maybe just IE Repair is worth a go for starters). Derek.W

Just to try something, I ghosted them at work last night. They seem to work fine now, but I'm still looking into the problem to find out what caused it. Thanks for your help!

The cause maybe a path/write access problem, I believe. The application is attempting to extract a file form a cabinet files (.CAB) using the CABINET.DLL. When it fails to write the file out, because the directory is MIA or the file exists and is read only (to the user who is attempting to write to it) the DLL responds with a Code 11 and the application relays that response. Mind you, I did not read this off a site, I pieced it together after about an hour of debugging an application I have authored. It was an oversight of mine when testing the application, test environments rarely have alternate applications locking down its paths with write restrictions hence very little way a developer could stumbled upon it and why when you blasted the machines with a ghost it 'resolved' the issue. Aiding the user with something a little better then Code 11, simply not a user friendly response, is surely needed in much of today’s development. By the way, I noting your post in the debug process, figured I would give anyone falling upon your note a heads up as to a possible cause (it was one of the top Google Hits so perhaps this helps the next reader...