I had a similar problem and it was resolved by changing the permissions of the SQL login. There is a windows user that SQL Agent runs under and there...