Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2008 Forums
 SQL Server Administration (2008)
 Agent jobs failing

Author  Topic 

Peter99
Constraint Violating Yak Guru

498 Posts

Posted - 2013-06-06 : 16:22:15
SQL server 2008 R2 agent jobs starting failing with following error:
"The job failed. Unable to determine if the owner (domain\login) of job MaintenancePlan - ABC.Full backup has server access (reason: Could not obtain information about Windows NT group/user 'domain\login', error code 0x5. [SQLSTATE 42000] (Error 15404))".

Any help.
Thanks

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2013-06-06 : 17:42:50
Change the job owner to sa.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

djj55
Constraint Violating Yak Guru

352 Posts

Posted - 2013-06-07 : 14:01:15
Do not use sa. create a user with the permissions needed.

djj
Go to Top of Page

jeffw8713
Aged Yak Warrior

819 Posts

Posted - 2013-06-10 : 14:07:49
quote:
Originally posted by djj55

Do not use sa. create a user with the permissions needed.

djj



Why not use sa?
Go to Top of Page

djj55
Constraint Violating Yak Guru

352 Posts

Posted - 2013-06-10 : 14:51:46
It is a best practice. By locking the sa account you have one less security leak point.

djj
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2013-06-10 : 18:58:32
We don't use sa either, but it's easier to reply to use sa as people will know to use whatever sysadmin account replaced it.

So our jobs owners point to our renamed sa account rather than sa. We rename it for sid purposes.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

Peter99
Constraint Violating Yak Guru

498 Posts

Posted - 2013-06-11 : 11:41:13
Database Engine Service Account was locked. Issued resolved after unlocking it.
Go to Top of Page
   

- Advertisement -