Viewing 2 posts - 1 through 2 (of 2 total)
Yes, see my second post above - resolved by adding our SQL Agent account to "Replace a process level token" in Local Security Policy.
August 3, 2016 at 3:19 am
#1893424
In case anyone else comes across this same issue, the source of the problem was a server security setting - our SQL Agent account needed to be added to "Replace...
December 22, 2015 at 5:24 am
#1847394