Solved

SQL 2012 error 15404

Posted on 2013-05-16
4
2,445 Views
Last Modified: 2013-06-15
I have a DBA who is getting this error from sql 2012
 SQLServer Error: 15404, Could not obtain information about Windows NT group/user 'DOMAIN\USER', error code 0x6e. [SQLSTATE 42000] (ConnIsLoginSysAdmin


This is the error from the applications log on Windows 2008 R2 SP1

Log Name:      Application
Source:        SQLSERVERAGENT
Date:          5/8/2013 1:00:00 AM
Event ID:      208
Task Category: Job Engine
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      "SERVERNAME"
Description:
SQL Server Scheduled Job 'Backup.Transaction Log Backup' (0x73F40EB3D55EFB47A865552850B3A8B7) - Status: Failed - Invoked on: 2013-05-08 01:00:00 - Message: The job failed.  Unable to determine if the owner (DOMAIN\USER) of job Backup.Transaction Log Backup has server access (reason: Could not obtain information about Windows NT group/user 'DOMAIN\USER', error code 0x6e. [SQLSTATE 42000] (Error 15404)).

After further investigation He had updated SLQ 2012 to SP1 on May 7th and added the Hotfix the day after.  He did not restarted the server after installing these updates.  He did restarted the server on May 10th.  When the errors occurred he switched the job from using his account to the account used to run the sqlagent which now works.  This used to work before he applied SP1.  

Do you have an explanation why this happened in order to give a better explanation to the DBA.  Mind you I am not a SQL expert.
0
Comment
Question by:hbpub
  • 3
4 Comments
 
LVL 18

Assisted Solution

by:x-men
x-men earned 200 total points
ID: 39171489
have you checked this? : http://support.microsoft.com/kb/834124
0
 

Author Comment

by:hbpub
ID: 39171632
The Article mentions SQL error 8198.  The SQL error he received is 15404.  It mentions SQL 2000.  Would this still apply since he is running SQL 2012.
0
 

Accepted Solution

by:
hbpub earned 0 total points
ID: 39184631
I found that the  DBA had run sql sp1 for 2012 and a hotfix.   This is when the problem statrted. He rebooted the server and it is now working.
0
 

Author Closing Comment

by:hbpub
ID: 39249726
The DBA had done a update and after rebooting the server the problem cleared.
0

Featured Post

Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

Question has a verified solution.

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

Introduction In my previous article (http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/SSIS/A_9150-Loading-XML-Using-SSIS.html) I showed you how the XML Source component can be used to load XML files into a SQL Server database, us…
JSON is being used more and more, besides XML, and you surely wanted to parse the data out into SQL instead of doing it in some Javascript. The below function in SQL Server can do the job for you, returning a quick table with the parsed data.
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 different Recovery Models available in SQL Server and explain, as well as show how full, differential and transaction log backups are performed

861 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

21 Experts available now in Live!

Get 1:1 Help Now