The other week I noticed some of the Jobs that we have scheduled in our MSSQL setup had started repeatedly failing. They were giving the message, "MSSQL: The owner () of job <Job Name> does not have server access".

I thought this was weird, especially since other jobs were running fine. I investigated a little further and found this forum that discussed this issue.

What I gathered is that if using the DOMAIN/Username (Windows Login) syntax for the Owner field when setting up a job, sometimes after a server restart it has trouble verifying the admin privileges to allow the job to actually run.

The ways to fix this are:

  1. Restart the SQL Server Agent service as a temporary solution.
  2. Change the job owner field for your job to read "sa" (without the quotes) as a permanent solution.

Hope this helps someone!

This entry was posted on March 11, 2011 at 2:09 PM and has received 855 views. There are currently 0 comments. Print this entry.