locked
SQL login error for NT AUTHORITY\SYSTEM RRS feed

  • Question

  • below is the error log of application in Event viewer

    07/15/2011 12:12:33,Logon,Unknown,Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <local machine>]
    07/15/2011 12:12:33,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 16.
    07/15/2011 12:11:33,Logon,Unknown,Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <local machine>]
    07/15/2011 12:11:33,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 16.
    07/15/2011 12:10:33,Logon,Unknown,Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <local machine>]
    07/15/2011 12:10:33,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 16.
    07/15/2011 12:09:33,Logon,Unknown,Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <local machine>]
    07/15/2011 12:09:33,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 16.
    07/15/2011 12:08:33,Logon,Unknown,Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <local machine>]
    07/15/2011 12:08:33,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 16.
    07/15/2011 12:07:33,Logon,Unknown,Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <local machine>]


    tushar
    Friday, July 15, 2011 6:52 AM

Answers

  • Here's an explanation I found for state = 16:

    "State=16 means that the incoming user does not have permissions to log into the target database.  So for example say you create a user FOO and set FOO's default database to master, but FOO does not have permissions to log into master.
     
    This can also happen if for example the default database for user FOO is not online (for example the database is marked suspect).
     
    So to check on this theory, try logging the user into some other database and then try using the USE DATABASE command to switch to the target database, you will get a better error message as to the root cause of the failure."

    Here is where I found the explanation: http://blogs.msdn.com/b/sql_protocols/archive/2006/02/21/536201.aspx


    Tibor Karaszi, SQL Server MVP | web | blog
    • Proposed as answer by Pradeep Adiga Friday, July 15, 2011 7:13 AM
    • Marked as answer by Peja Tao Thursday, July 21, 2011 9:10 AM
    Friday, July 15, 2011 7:10 AM

All replies

  • Here's an explanation I found for state = 16:

    "State=16 means that the incoming user does not have permissions to log into the target database.  So for example say you create a user FOO and set FOO's default database to master, but FOO does not have permissions to log into master.
     
    This can also happen if for example the default database for user FOO is not online (for example the database is marked suspect).
     
    So to check on this theory, try logging the user into some other database and then try using the USE DATABASE command to switch to the target database, you will get a better error message as to the root cause of the failure."

    Here is where I found the explanation: http://blogs.msdn.com/b/sql_protocols/archive/2006/02/21/536201.aspx


    Tibor Karaszi, SQL Server MVP | web | blog
    • Proposed as answer by Pradeep Adiga Friday, July 15, 2011 7:13 AM
    • Marked as answer by Peja Tao Thursday, July 21, 2011 9:10 AM
    Friday, July 15, 2011 7:10 AM
  • Hi,

      But in a live server environment it is good for testing


    tushar
    Monday, August 8, 2011 8:21 AM