I just installed Premiere and Encore CS4, installed all the latest updates, and then managed to burn exactly one DVD. Since then (yesterday), any attempt to build a disc or an image fails with "access denied" (real helpful!) when the build gets to the "Building file system (sorting)." step.

At first, I figured my project had self-destructed, so I created a new one. Same thing. Any ideas? As usual, it seems the steepest part of the learning curve for this new release will be all the silly bugs :-(

Again, this is when building an image or a disc. Project is only around 1Gb, so disc size has nothing to do with it. The build target is accessible in either case as well. Also, to the "Did you try reinstalling?" crowd: Be gone.

Regards,
Aaron

I've seen this error with one Project. In that case, I was using a "template" of the Project, doing a Save_As, and Importing the Assets for that phase of the overall project. Just re-did that one, and it worked perfectly on the second attempt.

Now, the "access denied" error pops up under a few situations. One is if one has Windows Indexing on for that HDD. This program, besides stealing a lot of CPU cycles, will also lock a file, while it does its thing. I turn it off for every folder of every HDD. Search is only marginally compromised in search-time. I can live with that. With files that are being written and re-written a lot (NLE work, PS work), Indexing will lock the file, while it works. With big files, Indexing can take a lot of time, even with fast HDDs and a good CPU. It is accessed from My Computer (or Windows Explorer) Properties for each drive (note: each drive). I check to turn off Indexing for all files and folders. This can take some time to Apply for a 2TB HDD with an intricate folder structure. Just be patient.

Also, it *seems* that this error can also occur with Transcode/Cache files. You might wish to delete any of these, and let Encore re-build them, as is necessary. Though I did not try this when I encountered the error, what I did, re-create the Project, had the same effect.

I posted my observations on this problem, as it effected my Project, to this forum, but above is rather a distillation of that thread. However, there might be some useful info from Jeff, Ruud and Neil, that I have forgotten.

Good luck,

Hunt

Thanks a bunch, Bill; the Admin thing did it. NUTS!!! Adobe!!! This suggests to me that some resources are being created with incorrect security attributes or something. Especially since it worked the first time and then went bananas. I never had such a thing happen with CS3, and I always ran it in a "normal" (non-Admin) context. Then again, I had plenty of other issues with CS3 ;-)

Well! I'm unblocked. Thanks again,
Aaron