650 Views 2 Replies Latest reply: Jul 2, 2013 4:42 AM by smuuudge
Currently Being ModeratedJul 2, 2013 4:42 AM (in response to Ludler)
The error was caused by an issue with 10.6.8. I have updated the machine in question with the 10.6.8 v1.1 update and it resolved the problem. More info here if anyone is interested.