Hi Ryan
Long Time No See! 
We continue to have the “Access is denied” error… is this normal? I send you the error report.
But the BIG PROBLEM here, and it happened more than once during the night, if one machine gives a error on all the jobs (like the Access is denied error) that machine alone can fail all jobs and stop all the renders!!!
We have configure on the monitor the failure detection options like the print screen I send you.
Is there a way that, if one machine gives errors on a job, the monitor can exclude that machine from that job automatically? If not this could be a excelente new feature! 
Thanks
Mario
This isn’t normal, but we can’t reproduce it on any of our machines, which consist of Windows 2000, XP (32 and 64 bit), and Vista (32 and 64 bit). We’ve from a few other people that have run into this that restarting the machine often fixes the problem. If this works for you, you could enable the Machine Restart feature in Power Management to restart your render nodes at certain intervals (which requires you to run Pulse if you’re not doing so already).
This is accomplished using the “Error Limit Before A Job Is Marked Bad” setting. This is the number of consecutive errors a slave will generate for a job before it marks it as bad and moves on. Maybe set this value to 3 or 5.
Cheers,
If you have more than 7 machines trying to render on the same job/accessing the same computer at the same time, you can trigger that error. We had this issue early on, the render locally option seemed to fix it.