locked
Error: 18456, Severity: 14, State: 16. RRS feed

  • Question

  • Hi,

    I have below @@version of SQL Server

    Microsoft SQL Server 2005 - 9.00.4035.00 (X64)   Nov 24 2008 16:17:31   Copyright (c) 1988-2005 Microsoft Corporation  Standard Edition (64-bit) on Windows NT 6.0 (Build 6001: Service Pack 1)

    Since a few days i am getting below messages continuously in my Error Logs

    'MOIL\DOH-SVC-SQL-DBA06' has sysadmin server role on that SQL server....and also included in Administrators group on the server.

    ...................

    2009-10-04 17:55:00.27 Logon Error: 18456, Severity: 14, State: 16.

    2009-10-04 17:55:00.27 Logon Login failed for user 'MOIL\DOH-SVC-SQL-DBA06'. [CLIENT: <local machine>]

    2009-10-04 17:56:00.35 Logon Error: 18456, Severity: 14, State: 16.

    2009-10-04 17:56:00.35 Logon Login failed for user 'MOIL\DOH-SVC-SQL-DBA06'. [CLIENT: <local machine>]

    2009-10-04 17:57:00.43 Logon Error: 18456, Severity: 14, State: 16.

    2009-10-04 17:57:00.43 Logon Login failed for user 'MOIL\DOH-SVC-SQL-DBA06'. [CLIENT: <local machine>]

    2009-10-04 17:58:00.48 Logon Error: 18456, Severity: 14, State: 16.

    2009-10-04 17:58:00.48 Logon Login failed for user 'MOIL\DOH-SVC-SQL-DBA06'. [CLIENT: <local machine>]

    2009-10-04 17:59:00.54 Logon Error: 18456, Severity: 14, State: 16.

    2009-10-04 17:59:00.54 Logon Login failed for user 'MOIL\DOH-SVC-SQL-DBA06'. [CLIENT: <local machine>]

    2009-10-04 18:00:00.59 Logon Error: 18456, Severity: 14, State: 16.

    2009-10-04 18:00:00.59 Logon Login failed for user 'MOIL\DOH-SVC-SQL-DBA06'. [CLIENT: <local machine>]

    2009-10-04 18:01:00.68 Logon Error: 18456, Severity: 14, State: 16.

    2009-10-04 18:01:00.68 Logon Login failed for user 'MOIL\DOH-SVC-SQL-DBA06'. [CLIENT: <local machine>]

    2009-10-04 18:02:00.76 Logon Error: 18456, Severity: 14, State: 16........................................................................

    Wednesday, November 11, 2009 10:34 AM

Answers

  • RubSay

    Have you installed SQL Reporting Services on this server?

    It looks like this has been installed and not configured, and now the service is starting automatically and is unable to connect to its ReportServer database.

    Probable solutions are to either configure SSRS, or disable the service if it's not required.

    HTH

    Ewan



    If you have found this post helpful, please click the 'Vote as Helpful' link (the green triangle and number on the top-left).

    If this post answers your question, click the 'Mark As Answered' link below. It helps others who experience the same issue in future to find the solution.
    • Marked as answer by RubSay Wednesday, November 11, 2009 12:47 PM
    Wednesday, November 11, 2009 12:36 PM

All replies



  • Hi,

    Perhaps there is some database offline and 'MOIL\DOH-SVC-SQL-DBA06'  cannot get access.

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

    BR,

    JoukoK
    Wednesday, November 11, 2009 10:52 AM
  • Hi Joukok...

    I donot have any databases offline on this server.

    I run below SQL st. and it all says ONLINE for my databases.

    select

     

    name, user_access_desc, is_auto_close_on, is_in_standby, state_desc from sys.databases

    Wednesday, November 11, 2009 11:24 AM
  • Hi,

    The best way to identify your problem is to run profiler for Login Failed event, also refer this thread http://social.msdn.microsoft.com/Forums/en-US/vblanguage/thread/747f01b4-288d-49ae-ab85-0fdf34ea2bfa/

    Regards
    Hemantgiri S. Goswami | http://www.sql-server-citation.com/ | http://www.surat-user-group.org/ -- Surat SQL Server User Group
    Wednesday, November 11, 2009 11:36 AM
  • State 16 mean that the logi do not have access to the database in question. Below is a quote "from the net":

    "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. "


    Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://sqlblog.com/blogs/tibor_karaszi
    Wednesday, November 11, 2009 12:17 PM
  • Thanks Tibork...

    The account 'MOIL\DOH-SVC-SQL-DBA06' is a Service account which is a sysadmin on the SQL sevrer

    Profiler says that

    Audit Loin Failed for ApplicationName Report Server DatabaseName master Error 18456 LoginName MOIL\DOH-SVC-SQL-DBA06 TextData Login failed for user 'MOIL\DOH-SVC-SQL-DBA06'

    Does it ring any bells for any of you guys??

    FYI...I donot see
    ReportServer or ReportServerTempDB databases
    Reporting Service in Configuration Manager


    So not sure why ApplicationName is referring as Report Server...?????

    Wednesday, November 11, 2009 12:33 PM
  • RubSay

    Have you installed SQL Reporting Services on this server?

    It looks like this has been installed and not configured, and now the service is starting automatically and is unable to connect to its ReportServer database.

    Probable solutions are to either configure SSRS, or disable the service if it's not required.

    HTH

    Ewan



    If you have found this post helpful, please click the 'Vote as Helpful' link (the green triangle and number on the top-left).

    If this post answers your question, click the 'Mark As Answered' link below. It helps others who experience the same issue in future to find the solution.
    • Marked as answer by RubSay Wednesday, November 11, 2009 12:47 PM
    Wednesday, November 11, 2009 12:36 PM
  • Hmmm....

    Thanks. I have disabled SQL Server Reporting Service under Services (Run -> Services.msc).

    Strange as i was not able to see any Reporting Service in SQL Server Configuration Manager...!

    Hence i am not getting the error message anymore!
    Wednesday, November 11, 2009 12:46 PM