I'm experiencing the same errors. The domain account used is set as a server admin and as sysadmin.

Setting the jobs to run under 'sa' is a workaround, but best practice...