i had the same issue. The only way i could resolve it was to add the account that is running the sql agent service as an admin on the box the job is running on.

for me if the sql agent service user is admin on box then i no longer get the issue