locked
Login failed for user sa RRS feed

  • Question

  • Hi All,
    I am using sa login to connect my databse from sqlbrowser.It is logging sucessfully but if i check eventlog it is saying that Login failed for user sa .Password did not match that for the login provided eventid 18456. how i can resolver this issue any ideas/Suggestions.
    Monday, August 30, 2010 2:32 PM

Answers

  • SQL Broswer isn´t an application to login from, it is a service. Nevetheless which application you mean, if you can login successfully with that application, there might be another application, eventually from another computer, check the Client address in the event log entry which is trying to access your computer.

    -Jens


    Jens K. Suessmeyer http://blogs.msdn.com/Jenss
    • Proposed as answer by Tom Li - MSFT Tuesday, August 31, 2010 11:05 AM
    • Marked as answer by Tom Li - MSFT Sunday, September 5, 2010 9:11 AM
    Monday, August 30, 2010 3:33 PM

All replies

  • SQL Broswer isn´t an application to login from, it is a service. Nevetheless which application you mean, if you can login successfully with that application, there might be another application, eventually from another computer, check the Client address in the event log entry which is trying to access your computer.

    -Jens


    Jens K. Suessmeyer http://blogs.msdn.com/Jenss
    • Proposed as answer by Tom Li - MSFT Tuesday, August 31, 2010 11:05 AM
    • Marked as answer by Tom Li - MSFT Sunday, September 5, 2010 9:11 AM
    Monday, August 30, 2010 3:33 PM
  • Please check the password provided for login 'sa' as it says password did not match. Possibly 'sa' password could have changed.

    For Event ID 18456 with Login failed error, please refer the Understanding "login failed" (Error 18456) error messages in SQL Server 2005


    Sivaprasad S http://sivasql.blogspot.com Please click the Mark as Answer button if a post solves your problem!
    Monday, August 30, 2010 11:59 PM
  • hello Srridharr,

    sometimes when you get error 18456 and that a message related to failing to access and I think you got "State 1" in the error also ... well, not always this is the real cause of the problem ... to find out what the real cause check the server's error log, where you will find near the date and time of your attempt to login something similar to this 

    2006-02-27 00:02:00.34 Logon     Error: 18456, Severity: 14, State: 8

    and the following are the common error states and their descriptions:

     

    2 and 5 Invalid userid

    6 Attempt to use a Windows login name with SQL Authentication

    7 Login disabled and password mismatch

    8 Password mismatch

    9 Invalid password

    11 and 12 Valid login but server access failure

    13 SQL Server service paused

    18 Change password required

     

    the link is the source http://blogs.msdn.com/b/sql_protocols/archive/2006/02/21/536201.aspx

    Tuesday, August 31, 2010 10:43 PM