Login Failure for NT Authority\System user

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » Administering » Login Failure for NT Authority\System user

Rate Topic

Display Mode

Topic Options

Author

Message

mdn_2k5

Posted Tuesday, June 15, 2010 12:52 AM

Grasshopper

Group: General Forum Members
Last Login: Monday, January 28, 2013 9:37 AM
Points: 12, Visits: 63

Hi Friends,

We have a prodution server which runs SQL Server 2005 (Std 64 Bit).

There is a "Login Failure for NT Authority\System" error logged in the error log every minute.

Error Message Details
--------------------
Date 6/15/2010 2:49:23 AM
Log SQL Server (Current - 6/15/2010 2:49:00 AM)
Source Logon
Message
Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <local machine>]

We could nt find what exactly causes this issue.Please let me know any solutions,suggestions and comments about this issue.

Thanks in Advance
Dhayanithy

Post #937270

Henrico Bekker

Posted Tuesday, June 15, 2010 3:41 AM

SSCommitted

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 2:24 AM
Points: 1,871, Visits: 2,692

You have a service trying to run/authenticate as NT Auth..... against your SQL Instance.

----------------------------------------------
Msg 8134, Level 16, State 1, Line 1
Divide by zero error encountered.

Post #937343

Perry Whittle

Posted Tuesday, June 15, 2010 4:06 AM

SSCertifiable

Group: General Forum Members
Last Login: Today @ 9:47 AM
Points: 5,201, Visits: 11,151

track the machine down using its ip address and find out what is trying to authenticate

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" Wink

Post #937350

mdn_2k5

Posted Tuesday, June 15, 2010 6:38 AM

Grasshopper

Group: General Forum Members
Last Login: Monday, January 28, 2013 9:37 AM
Points: 12, Visits: 63

Friends, Thanks for the Reply.

Here are few details I found on the server.

Below are the tasks which are run by the NT Authority\System user in the server.

1.EXECUTE msdb.dbo.sp_sqlagent_get_perf_counters - SQL Agent Alert Engine

2.SELECT ISNULL(SUSER_SNAME(), SUSER_NAME()) - SQL Agent EMail Logger

3.UPDATE msdb.dbo.sysjobactivity - SQL Agent Job Invocation Engine

4.msdb.dbo.sysmail_help_admin_account_sp;1 - SQL Agent90 - id <2764>

I suspect on the No.1 task which could cause the issue,since it is batched every minute when checked in the Activity Monitor.But not sure on what way its affecting.

Any ideas???

Thanks in advance
Dhayanithy

Post #937425

Henrico Bekker

Posted Tuesday, June 15, 2010 6:43 AM

SSCommitted

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 2:24 AM
Points: 1,871, Visits: 2,692

grant sysadmin rights on SQL to NT Auth\SYSTEM and see if the error still occurs.

----------------------------------------------
Msg 8134, Level 16, State 1, Line 1
Divide by zero error encountered.

Post #937430

mdn_2k5

Posted Tuesday, June 15, 2010 6:53 AM

Grasshopper

Group: General Forum Members
Last Login: Monday, January 28, 2013 9:37 AM
Points: 12, Visits: 63

Hi Henrico Bekker,

Thanks a lot for the reply

The user NT Authority\System has SysAdmin rights already.

Thanks
Dhayanithy

Post #937441

mdn_2k5

Posted Wednesday, June 16, 2010 12:37 AM

Grasshopper

Group: General Forum Members
Last Login: Monday, January 28, 2013 9:37 AM
Points: 12, Visits: 63

Hi Friends,

Just wanted to add this bit to the error message.Here in the message The state shown as 16.

Source : Logon
Message : Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <local machine>]

Date : 6/14/2010 8:03:19 AM
Log : SQL Server (Current - 6/16/2010 2:02:00 AM)
Source : Logon
Message : Error: 18456, Severity: 14, State: 16.

Thanks in Advance
Dhayanithy

Post #937948

richardgazey

Posted Wednesday, June 16, 2010 3:59 AM

Forum Newbie

Group: General Forum Members
Last Login: Monday, March 26, 2012 2:34 AM
Points: 3, Visits: 170

I had this happening - and it turned out to be a test installation of Microsoft reporting services -which was running as a service

It had been installed and developers tried and rejected it as a reporting tool.

May be worth a try

Post #938024

preity

Posted Monday, December 05, 2011 9:50 AM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, December 12, 2012 7:45 AM
Points: 4, Visits: 213

Had the same issue. Stopping the SQL Server Reporting Services worked for me.

Post #1216453

« Prev Topic | Next Topic »

Permissions