-
Access Denied –
I am having a major issue – and I found a brief explanation – but I need a bit more HELP…
We have 3 systems networked to a XSAN – 2 G5s and 1 Of new Intel breeds. I had jumped around different systems last week – working on the same project – and now I have the “File Error: Access Denied” when I want to render. I understand that logging on as a different user on the same computer can do this – but the fact that I was on 3 different computers – what do I need to do??
-
4 Replies
-
The file permissions on the render directory may have gotten screwed up. Locate the render directory for the project and delete it. If you need what’s inside the directory then check the file permissions on the directory with the right click>get info.
The owner permissions should say that you can Read/Write if it doesn’t say that then the permissions need to be changed (not repaired, changed). If you are not an admin user on the machine then get the admin to sort it.
Emma
-
Hi. I am getting the same error message and I cleaned my render files but whenever I render my project it still comes up “file error: access denied”…. Do you have any more suggestions?
-
Access Denied is the message when I try to render. I checked the permissions on all folders and the program and I made it so all have access to read and write, so that can’t be the problem. In the past adjusting the sequence settings and A/V settings and then creating a new sequence and copying and pasting the timeline contents onto the new sequence has rectified rendering issues, but this time I am at a loss. Any ideas? It’s FCP 6 on the same Quad Intel Power Mac I’ve been using for this project for 2 years. Another issue is that FCP won’t launch on the Root User, but I’m less concerned about that at the moment.
-
Hi all,
I’ve been having a similar problem with FCP7 – “File Error: Access Denied” on render. This is typical of a read/write permissions problem. But when I changed the read/write permissions, no effect initially. However, when I changed the capture/render scratch in System Settings to another hard drive, and then changed it back again it worked. Bizarre, but i’m rendering again.
The most likely explanation I can offer is that FCP hadn’t realised that the read/write permissions had changed. FCP does occasionally come up with some weird minor glitches like this, as does Snow Leopard (like applying read only permissions to drives without your knowledge).
I recommend changing your render scratch drive, rendering a couple of clips, then changing it back again.
Reply to this Discussion! Login or Sign Up