Post reply

Cannot Conect, Microsoft sql Server 2005, Error 18456

  • September 1, 2009 at 7:23 am

    #134656

    Connection Error 18456. Get the error with either Windows Authentication or SQL SERVER authentication.

    Environment: Windows Vista Ultimate SP1. 64 - bit operating system

    SQL Server 2005 Workgroup Edition.

  • September 1, 2009 at 7:56 am

    #1047535

    Is the firewall blocking 1433?

  • September 1, 2009 at 8:57 am

    #1047592

    Don't know. Where do I check that ?.

  • September 1, 2009 at 9:32 am

    #1047613

    control panel, windows firewall

  • September 1, 2009 at 12:31 pm

    #1047740

    If you're getting error 18456, then you're successfully connecting to the server, but the login is being denied.

    To find details, view the SQL Server logs (I'm guessing SQL Server is hosted on another computer because you're connecting to Workgroup edition from Vista, and ought to be able to read the logs from another computer), either in SSMS or by reading the file called ERROR with notepad in the [SQL install directory]\Log directory.

    The SQL Server error log will show the 18456 error, but will include a State value. More details, and a table explaining the different State values, can be found here:

    http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx

    If no 18456 error is showing in the logs, ensure you are auditing failed logins, then try logging in again to force the error.

    -Eddie

    Eddie Wuerch
    MCM: SQL

  • September 1, 2009 at 12:46 pm

    #1047750

    I see no reference to 1433 in the exceptions tab.

  • September 1, 2009 at 12:54 pm

    #1047758

    Eddie -

    Check the log and I see two types: State 8 and state 11

    I'm also login in the same computer. I'm not accesing SQL from another computer in the domain.

    Rafael

  • September 1, 2009 at 1:40 pm

    #1047787

    The link I provided explains type 8 and 11 as follows:

    Type 8: password mismatch (you typed the wrong password)

    Type 11: Valid login but server access failure

    - This one is a bit more involved. This is generally caused when using Windows authentication, and the user does not have access to the server itself. Try to log in to the server directly using that Windows login and see if there are any errors logging in; it may just be as simple as the first login creating a profile on the server, clearing the way to remotely log in to SQL Server.

    -Eddie

    ** edit ** I see you're logging in to the server... dig into the link I provided; a number of other folks have worked through the same problem

    Eddie Wuerch
    MCM: SQL

  • July 29, 2010 at 2:48 am

    #1199660

    This happened to me after I detached a database defined in the login properties for that user as the default db for this user, if that’s the case in the user properties simply change the default database from “empty” to “something”.

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

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