9 Mar
2017
9 Mar
'17
2:27 p.m.
Ted,
I had a similar problem on SQL Server 2012. I figured out that I had to give full rights to whatever user it was scheduled to run under to both the program and folder it was running in. (I would assume also to any resources it uses as well). Once I did that, it ran like a charm. Before that, nothing, unless I was logged in.