Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
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,561 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

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Load balancing is the method of dividing the total amount of work performed by one computer between two or more computers. Its aim is to get more work done in the same amount of time, ensuring that all the users get served faster.
In this article we will learn how to fix  “Cannot install SQL Server 2014 Service Pack 2: Unable to install windows installer msi file” error ?
Via a live example, show how to extract information from SQL Server on Database, Connection and Server properties
Viewers will learn how the fundamental information of how to create a table.

791 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