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.
data_bitsdbaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
data_bitsdbaAuthor 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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.