Error: 18456, Severity: 14, State: 16

  • kiruba-370649

    SSC Veteran

    Points: 292

    Hi All,

    i am using SQL Server 2005,

    one day i getting error in SQL Server Logs

    Starting up database ' '.

    SQL Server has encountered 3 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.

    SQL Server has encountered 3 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.

    SQL Server has encountered 3 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.

    CHECKDB for database ' ' finished without errors on 2008-07-10 22:47:10.507 (local time). This is an informational message only; no user action is required.

    Login failed for user ' '. [CLIENT: Client IP]

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

    Login failed for user ' '. [CLIENT: Client IP]

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

    Login failed for user ' '. [CLIENT: Client IP]

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

    Login failed for user ' '. [CLIENT: Client IP]

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

    Login failed for user ' '. [CLIENT: Client IP]

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

    Login failed for user ' '. [CLIENT: Client IP]

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

    Starting up database ' '.

    CHECKDB for database ' ' finished without errors on 2008-07-10 22:47:10.507 (local time). This is an informational message only; no user action is required.

    Starting up database ' '.

    CHECKDB for database ' ' finished without errors on 2008-07-10 22:47:10.507 (local time). This is an informational message only; no user action is required.

    Starting up database ' '.

    CHECKDB for database ' ' finished without errors on 2008-07-10 22:47:10.507 (local time). This is an informational message only; no user action is required.

    myself i checked in google,its give some link

    http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=627471&SiteID=1

    http://www.eggheadcafe.com/software/aspnet/30907006/error-18456-severity-1.aspx

    http://www.corkchop.com/journal/2007/3/28/error-18456-severity-14-state-16.html

    Solution:

    Change DB Option "Auto Close" to False

    can any one explain why its happened?

    Any help is greatly appreciated.

    Best,

    Kiruba sankar.S

  • Gail Shaw

    SSC Guru

    Points: 1004474

    When a database is set to autoclose, it is shut down when the last user disconnects. That's what's causing the cache flush. SQL's removing anything related to that DB from memory.

    When a user wants to connect to the DB, it takes a few seconds to restart the DB. The login failures are caused by users who have that DB as their default DB. With the database closed, SQL can't confirm rights upon login, hence resulting in a login failure with state 16 (default database not accessible)

    Does that help?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • kiruba-370649

    SSC Veteran

    Points: 292

    Thanks SSCarpal Tunnel

  • Gail Shaw

    SSC Guru

    Points: 1004474

    kiruba (7/15/2008)


    Thanks SSCarpal Tunnel

    <grin> That's the forum ranking, not username.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • bguo

    SSC Veteran

    Points: 290

    I had same problem

    "Login failed for user 'sa' [CLIENT: IP_address]

    error 18456, security 14, state 16"

    I have check all online results, no answer.

    Recently, we installed Spotlight 2.5, and it has Quest Diagnostic Server, ....

    How did I fix it: As soon as I stopped "Quest Diagnostic Server", the error is gone. Spotlight 2.5 has Quest Diagnostic Server.

  • Gail Shaw

    SSC Guru

    Points: 1004474

    That means whoever configured the Quest tool configured it to use the sa account and specified an incorrect password. Not the fault of the tool

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • timl 69197

    SSC Rookie

    Points: 39

    Thank you, O great Gila Monster. 🙂 :beer: :beer: :beer: :beer: :beer:

    It seems as if this has solved a long running issue for us. I am in an online transaction processing environment, and we had issues where the transactions were timing out. This seems to have fixed this.

  • bindview

    Right there with Babe

    Points: 772

    I have a similar issue..

    Login Failed for user 'NT AUTHORITY\SYSTEM'. [client:IP]

    error:18456 severity:14 state:16

    Its default database is master.

    Any idea why i am receiving this error even if the default database is online and accessible.

    Also the login had sysadmin privilege

  • Ninja's_RGR'us

    SSC Guru

    Points: 294069

    bindview (8/2/2011)


    I have a similar issue..

    Login Failed for user 'NT AUTHORITY\SYSTEM'. [client:IP]

    error:18456 severity:14 state:16

    Its default database is master.

    Any idea why i am receiving this error even if the default database is online and accessible.

    Also the login had sysadmin privilege

    Please start a new thread.

Viewing 9 posts - 1 through 9 (of 9 total)

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