June 8, 2009 at 1:55 pm
SQL Server 2005 - on Windows Server 2003 Enterprise
Every time we reboot the SQL server (power outages, maintenance work, etc.), the SMSS maintenace plan backup jobs fail:
"The job failed. The owner () of job
Restarting the SQL Server Agent service correts the issue each time, but not until a number of backups have already failed. There are a number of postings here at SSC.com and elsewhere that hint that changing the backup owner might help, or changing the login credentials for the SQL Server Agent service.
I haven't found an answer yet that is explained clearly enough that I can understand it. Just what does everyone here do to:
1) Login the SQL Server Agent service (we use domain\administrator).
2) Change the owner of the job (which owner should I choose, and where can I change the job owner?)
While I am sure there are thousands of documents out there that provide instruction on best practices for SQL Server security, I don't have the time (or the patience) to read thousands of documents, and haven't found one yet that deals with this specific issue. As I mentioned before: lots of hints, but nothing I can use.
I anyone can help me unravel this mystery I'd appreciate it. I'm sure this is no mystery to some out there, but I am getting dizzy from reading discussions on the topic that have many words but no real suggestions...
Thanks.
June 17, 2009 at 8:15 am
Wow, nothing...
Even a link to a concise previous discussion would be helpful.
Thanks,
June 17, 2009 at 9:07 am
When you right click on the job->properties there is a test box with owner: specify a username like your domain/admin account here and see if this works.. This is a normal issue when user ont ahve access to a system resource to execute a job, so it fails...
do you use the same service account for SQL Agent and SQL engine?
I use the same acocunt accounts, to rule out any possibilities of treasure hunting at a later stage.
Maninder
www.dbanation.com
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply