data_bits
asked on
New agent jobs fails with : Could not obtain information about Windows NT group/user 'DOM\USER', error code 0x6e. [SQLSTATE 42000] (Error 15404)
Our windows engineer installed SQL Server 2012 and created an instance of SQL Server. I'm trying to get things set up for backups, etc. The creations of the maintenance plans and agent jobs are successful. However, when I try to execute them, they fail with the following errors:
Log Job History (LOCUS System Database FULL Backups.Subplan_1)
Step ID
Server DEVLOCKDB1\LOCUSSYSTEM
Job Name LOCUS System Database FULL Backups.Subplan_1
Step Name
Duration 00:00:00
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
The job failed. Unable to determine if the owner (LOCUS\locusadmin) of job LOCUS System Database FULL Backups.Subplan_1 has server access (reason: Could not obtain information about Windows NT group/user 'LOCUS\locusadmin', error code 0x6e. [SQLSTATE 42000] (Error 15404)).
I found mention of this kind of error when there has been service packs and hot fixes applied without reboot. That is not the case here.
Thanks.
Log Job History (LOCUS System Database FULL Backups.Subplan_1)
Step ID
Server DEVLOCKDB1\LOCUSSYSTEM
Job Name LOCUS System Database FULL Backups.Subplan_1
Step Name
Duration 00:00:00
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
The job failed. Unable to determine if the owner (LOCUS\locusadmin) of job LOCUS System Database FULL Backups.Subplan_1 has server access (reason: Could not obtain information about Windows NT group/user 'LOCUS\locusadmin', error code 0x6e. [SQLSTATE 42000] (Error 15404)).
I found mention of this kind of error when there has been service packs and hot fixes applied without reboot. That is not the case here.
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Yes but sa is preferable because is a persistent user and has the privileges it needs. If you set up an actual user and that user leaves the company and it's account is removed the job will fail... Whatever user you set it for it needs admin right in order to make sure can do anything it needs.
It is a good practice to setup sa as owner for all the SQL jobs..
It is a good practice to setup sa as owner for all the SQL jobs..
ASKER
This works as you have outlined. Is it possible to have the Owner as some id other than SA?