locked
Msg 18456, Level 14, State X, Server (...) Login failed Possible causes RRS feed

  • General discussion

  • This error is the most related in terms of Login problems. There is an exhaustive list about the cause this might occur in your system. If you did not solve the problem according to the information mentioned here, feel free to post a question in the security forum.

    Understanding "login failed" (Error 18456) error messages in SQL Server 2005
    http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx

    Jens K. Suessmeyer



     
    Sunday, February 15, 2009 12:27 PM

All replies

  • IF you could describe more details will be batter to solve the login issue. Try  login by Use Login Name as
    ComputerName\UserName 
    (
    example : Computer name is  Databasetimes and username is : Faiz
    You will use log in as  Databasetime\Faiz )

    Thanks
    Faiz Farazi
    http://databasetimes.blogspot.com/
    Faiz Farazi http://databasetimes.blogspot.com
    Sunday, June 14, 2009 3:04 AM
  • IF you could describe more details will be batter to solve the login issue. Try  login by Use Login Name as
    ComputerName\UserName 
    (
    example : Computer name is  Databasetimes and username is : Faiz
    You will use log in as  Databasetime\Faiz )

    Thanks
    Faiz Farazi
    http://databasetimes.blogspot.com/
    Faiz Farazi http://databasetimes.blogspot.com
    I recently did a fresh install of sql server 2008, and my choices to login are to pick 'active directory', which forces the selection of the user I'm currently logged in as (the domain admin; logged in on the sql server, which itself is not a DC), or I can login using sql authentication, allowing me to type in the 'sa' account and password.

    Neither works.  Still haven't found a solution for it.
    Monday, July 13, 2009 2:34 PM
  • I am having the exact same issue as posted above. I recently did a fresh install of sql server 2008 on a 2008ent server and my choices to login are to pick Windows Authentication or SQL Server Auth, which forces the selection of the user I'm currently logged in as (the domain admin; logged in on the sql server, which itself is not a DC).
    Error Number: 18456
    Severity: 14
    State: 1

    Thanks

    Darren
    Monday, October 19, 2009 8:32 PM
  • I am having the exact same issue as posted above. I recently did a fresh install of sql server 2008 on a 2008ent server and my choices to login are to pick Windows Authentication or SQL Server Auth, which forces the selection of the user I'm currently logged in as (the domain admin; logged in on the sql server, which itself is not a DC).
    Error Number: 18456
    Severity: 14
    State: 1

    Thanks

    Darren

    There's a few things I'm not sure of here. Are you installing on Windows 2003 or 2008? Is the target computer properly joined to the domain?
    When installing SQL 2008 on one of the OS's above joined to a domain you have two options for login security: Windows Authentication or "Both" SQL and Windows. There is no "SQL Server Auth" only option as you seem to indicate above. That's probably just me being picky and reading that the wrong way though ;)

    When you're given the chance to add Windows accounts to the local admin role at setup you have the option of selecting the account doing the install, or specifying specific groups or accounts. In a domain a good way to enforce security and aid in auditing is to setup a security group for DBAs, and then grant permissions to that group at setup time.
    The easy default is to add the current user, but you do have options at install time.

    Now, if somehow you have installed SQL in a way in which you don't have sysadmin and/or are denied access you can get around that by starting it in single user mode which will grant sysadmin access to anyone in the Local Administrators group on the computer. Then, simply grant the appropriate accounts/groups access and restart the service.
    Link to Single User Mode Startup Process: http://msdn.microsoft.com/en-us/library/ms188236.aspx

    Note that other AD login errors could also indicated domain controller communication or configuration issues.

    Good luck!
    -Andrew


    Sunday, November 8, 2009 4:46 PM