Post reply

Login failed for user ''NT AUTHORITY\SYSTEM''.[CLIENT: ]

  • September 6, 2007 at 2:34 pm

    #118581

    Can anyone offer some help on how I can clean up a login failure which is showing up my SQL Server Logs? It occurs about 4 or 5 times a minute.

    The message appears as the following:

    Login failed for user 'NT AUTHORITY\SYSTEM'.[CLIENT:]

    Error: 18456, Severity: 14, State: 16.

    From what I understand the state:16 indicates the incoming user doesn't have permissions to log into the target database. Is there any way to determine what the target database is? How can I get more info on what exactly is trying to log in?

    I haven't a clue on how I can begin to track this down.

    Ideas?

    Regards,
    Bob Szymanski
    Blue Mule Software

  • September 7, 2007 at 2:41 am

    #732051

    Bob,

    Probably the easiest method is to run SQL Profiler against your server for a short period of time filtering on the 'NT AUTHORITY\SYSTEM' i.e. the local system account of your SQL Server, if you have no luck there grab a profile without filters and see what you can find, you shouldn't have to run it for long if it's happening so frequently. 

    You should then see what process is trying to connect.  I would assume it's a process or service running under the context of the local system account.  Backup agent, IIS, .NET service etc?

    Also have a look through your local services for any services running as 'Local System' that seem out of place

    ll

  • September 7, 2007 at 6:31 am

    #732106

    Bob,

    This is a clear example of Kerberos authentication being failed.  Check for configuring kerberos on your domain.

    You have a lot of documentation on support.microsoft.com for this error message.

     

    In casee you dont find any please let me know.

     

  • September 7, 2007 at 8:11 am

    #732166

    Thanks for your help.

    I was able to get it to stop by turning off the Reporting Services service. However, this doesn't explain why. Eventually, I am going to need to turn on Reporting Services.

    Hmmmmm, what next?

    Regards,
    Bob Szymanski
    Blue Mule Software

  • September 7, 2007 at 9:14 am

    #732186

    You will probably need to change the identity that the Reporting Services service runs under to a domain account, and then create a login in SQL Server for that account and give it permissions to the RS databases.

    Hope this helps

  • September 7, 2007 at 9:23 am

    #732190

    Thanks Richard, I'll give this a whirl.

    Regards,
    Bob Szymanski
    Blue Mule Software

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply