Solved

SQL 2012 error 15404

Posted on 2013-05-16
4
2,463 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

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

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

Suggested Solutions

Nowadays, some of developer are too much worried about data. Who is using data, who is updating it etc. etc. Because, data is more costlier in term of money and information. So security of data is focusing concern in days. Lets' understand the Au…
International Data Corporation (IDC) prognosticates that before the current the year gets over disbursing on IT framework products to be sent in cloud environs will be $37.1B.
Viewers will learn how to use the SELECT statement in SQL to return specific rows and columns, with various degrees of sorting and limits in place.
Viewers will learn how to use the SELECT statement in SQL and will be exposed to the many uses the SELECT statement has.

832 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