Jobs fail after server reboot

[WinniePooh]

Three backup jobs have been set up via maintenance plans on our server. After a server reboot two of these jobs fail with the error message "The job failed. The owner () of job Transaction Log Backup Job for DB Maintenance Plan 'Daily DB Backup' does not have server access." Amending the maintenance plan and reapplying the changes back again seem to fix the problem.

Does anyone have any ideas why this would be happening?

Many thanks.

 

[Corran007]

what user is the startup account for sqlagent set to? is it local system or a specific user?

 

[mrdenny]

This happens every once and a while within SQL Server. The sql agent gets confused about who owns the job. I haven't been able to get a good answer from anyone as to why yet. Simply edit the job, change the owner to a different user, click ok, edit the job again, change the owner back, and all should be well.

I'd do a backup of msdb just to be on the safe side after you make the changes.

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[WinniePooh]

Many thanks for the updates. For information the services are running as the local administrator.

I've taken a look at the jobs scheduled through enterprise manager and cannot seem to find an option to change the owner. I've created them as part of a maintenance plan but don't believe that should remove privileges on the jobs. Could you clarify where I can find this option?

Many thanks.

 

[Corran007]

im wondering if its just an issue with running local vs a domain user. i cannot ever recall having gotten that error on my systems. but they all run a domain user account.

if you right click on the job ans select properties. one of the items on the general tab is owner. its a drop down list of all the users on the system.

 

[mrdenny]

When I've seen the problem the servers were running as a domain user.

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[WinniePooh]

For information I reviewed the owner of the jobs and noticed that the jobs failing were running under the local administrator while the successful job ran under the domain user. I've changed them all to run under the domain account and that seems to have fixed the problem. Thanks for pointing me in the right direction!

As a side point, I have checked our other SQL Servers and noticed that, although they have all been set up a similar way using Maintenance Plans, their respective jobs all run under different accounts! Some are running as local administrator, some as the domain user and some as even sa. I've never encountered the reboot problem on any of these other servers so I'm still a little mistified as to why it suddenly started happening.

 

[mrdenny]

I'm glad that you were able to fix it. I've checked with several people over the years that I've seen this problem, and we've never been able to come up with a reason for the problem, only the resolution.

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[pweegar]

Another thing to look at/try: Is the SQLAgent service up and running? If so, shut it down and restart it. I've seen the SQLAgent NOT start for whatever reason and no error generated as to the fact that it wan't running. Until I notice jobs not completing...