Solved

New agent jobs fails with : Could not obtain information about Windows NT group/user 'DOM\USER', error code 0x6e. [SQLSTATE 42000] (Error 15404)

Posted on 2014-10-10
3
3,206 Views
Last Modified: 2014-10-15
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
Comment
Question by:data_bits
  • 2
3 Comments
 
LVL 26

Accepted Solution

by:
Zberteoc earned 500 total points
ID: 40373141
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.
1
 

Author Comment

by:data_bits
ID: 40373436
Zberteoc,
This works as you have outlined. Is it possible to have the Owner as some id other than SA?
0
 
LVL 26

Expert Comment

by:Zberteoc
ID: 40373593
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

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

If you have heard of RFC822 date formats, they can be quite a challenge in SQL Server. RFC822 is an Internet standard format for email message headers, including all dates within those headers. The RFC822 protocols are available in detail at:   ht…
In this article I will describe the Copy Database Wizard method as one possible migration process and I will add the extra tasks needed for an upgrade when and where is applied so it will cover all.
This video shows, step by step, how to configure Oracle Heterogeneous Services via the Generic Gateway Agent in order to make a connection from an Oracle session and access a remote SQL Server database table.
Using examples as well as descriptions, and references to Books Online, show the documentation available for datatypes, explain the available data types and show how data can be passed into and out of variables.

757 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now