Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4758
  • Last Modified:

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.
0
data_bits
Asked:
data_bits
  • 2
1 Solution
 
ZberteocCommented:
To resolve this issue:
Launch Microsoft SQL Server Management Studio and connect to the database.
In the Object Explorer, navigate to SQL Server Agent > Jobs.
Right click the maintenance plan that you used during the initial creation of the job and click Properties.

Note: The maintenance plan has the format MaintenancePlan_Name.Subplan_x.

Navigate to Job Properties > General Page.
Set the value of Owner to SA.
Click OK.
2
 
data_bitsAuthor Commented:
Zberteoc,
This works as you have outlined. Is it possible to have the Owner as some id other than SA?
0
 
ZberteocCommented:
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..
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now