keymoo (7/8/2016)
Phil Parkin (7/7/2016)
Just to totally rule out a permissions issue, can you temporarily change the SQL Agent logon credentials to be yours, rerun the job & then verify (again from the All Executions report) that the job was, in fact, run with your credentials.
Good one! It was a permissions issue. The share permissions were correct, but the NTFS permissions to the folder were locked down and SQL Agent didn't have permission. I've changed it now and all is good.
What annoys me about this, is that I didn't get an Access Denied error bubbling up from the OS. Grrrr. Thanks for your help.
Great that you tracked it down in the end. You are right to be annoyed about the lack of errors – and I assure you that you are not alone in being annoyed about it.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.