Sign in
 
Home20122008 R2200820052000LibraryForums
SQL Server >
> 
> 
Window Authentication Login Failed

Answered Window Authentication Login Failed

  • Thursday, May 17, 2012 11:58 PM
     
     
    Sign In to Vote
    0

    Hi Folks,

    Today I m having issues with the Windows Authentication login failed, it is effecting to three users are facing the issue: and they are NOT able able log on SQL Server by using SSMS (SQL Server Management Studio)  :(. (and I m able to impersonate those logins through query analyzer)

    Error Message:

    Login failed for user XXXXXX\SatishKumar'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors.

    NOTE: UAC has already disabled on this server. Please let me know other than than UAC ;-)

    Thanks,

    Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

     

All Replies

  • Friday, May 18, 2012 12:33 AM
     
     
    Sign In to Vote
    0

    You might think silly but worth a try to specifically grant connect to SQL like:

    GRANT CONNECT SQL TO [XXXXXX\SatishKumar];

     
  • Friday, May 18, 2012 12:51 AM
     
     
    Sign In to Vote
    0

    NO luck dude :-), I already tried with all of those attemtps :( final option i came to forums

    Thanks,

    Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

     
  • Friday, May 18, 2012 1:43 AM
    Moderator
     
     
    Sign In to Vote
    1
    Do you have windows groups added in SQL Server and you are part of any group?
    Is your account directly added as Login?

    I remember one case where SID mismatch caused this.

    Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker
    --------------------------------------------------------------------------------
    This posting is provided "AS IS" with no warranties, and confers no rights.
    --------------------------------------------------------------------------------
    My Blog | Team Blog | @Twitter

     
  • Friday, May 18, 2012 2:01 AM
     
     
    Sign In to Vote
    0

    Logins are directly Mapped...

    Thanks,

    Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

     
  • Friday, May 18, 2012 2:04 AM
     
     
    Sign In to Vote
    0
    Have you granted the user rights 'Replace a process level token' to your SQL server service account?

     
  • Friday, May 18, 2012 2:08 AM
    Moderator
     
     
    Sign In to Vote
    0

    Logins are directly Mapped...

    Thanks,

    Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)


    Okay. Can you check if SID of your account (account which is failing) is same in Windows and SQL?

    Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker
    --------------------------------------------------------------------------------
    This posting is provided "AS IS" with no warranties, and confers no rights.
    --------------------------------------------------------------------------------
    My Blog | Team Blog | @Twitter

     
  • Friday, May 18, 2012 3:15 AM
     
     
    Sign In to Vote
    0

    Hi Steven Wang,

    Just checked, Already SQL Service account is a Member of 'Replace a process level token' .

    Thanks,

    Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

     
  • Friday, May 18, 2012 3:16 AM
     
     
    Sign In to Vote
    0

    Hi Bala,

    It seems SID's are okay to me becuase I was droped and re-created the problamatic logins :(

    Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

     
  • Friday, May 18, 2012 4:13 AM
    Moderator
     
     
    Sign In to Vote
    0
    Check http://blogs.msdn.com/b/sqlserverfaq/archive/2010/10/27/troubleshooting-specific-login-failed-error-messages.aspx

    Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker
    --------------------------------------------------------------------------------
    This posting is provided "AS IS" with no warranties, and confers no rights.
    --------------------------------------------------------------------------------
    My Blog | Team Blog | @Twitter

     
  • Friday, May 18, 2012 10:14 AM
     
     
    Sign In to Vote
    0

    Hi Bala,

    I already that the link which you are given but NO luck.

    Thanks,

    Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

     
  • Friday, May 18, 2012 10:24 AM
    Moderator
     
     
    Sign In to Vote
    1

    Hi Bala,

    I already that the link which you are given but NO luck.

    Thanks,

    Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

    Now that needs investigation. Ping me via MSN Messenger blakhani (at) koolmail (dot) in

    Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker
    --------------------------------------------------------------------------------
    This posting is provided "AS IS" with no warranties, and confers no rights.
    --------------------------------------------------------------------------------
    My Blog | Team Blog | @Twitter

     
  • Friday, May 18, 2012 10:53 AM
     
     
    Sign In to Vote
    0

    Today I m having issues with the Windows Authentication login failed, it is effecting to three users are facing the issue: and they are NOT able able log on SQL Server by using SSMS (SQL Server Management Studio)  :(. (and I m able to impersonate those logins through query analyzer)

    Error Message:

    Login failed for user XXXXXX\SatishKumar'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors.

    hello Satish

    are all SQL Logins with Windows Authentication affected or only a few ?

    did you check the event log on the server where the SQL Server is running? are there any errors or warning and did you check that the server does have identical time as the AD or your Kerberos server?

    is it possible to reboot this server and check if the error still occurs?

    Please use Mark as Answer if my post solved your problem and use Vote As Helpful if a post was useful.

     
  • Friday, May 18, 2012 12:53 PM
     
     
    Sign In to Vote
    1

    I got same issue some time and when finding the root cause it occurs in changing users password. Then i drop these users from logins and recreate to work properly.

    Shamas Saeed (if Post helpful please mark as Answer) http://shamas-saeed.blogspot.com

     
  • Friday, May 18, 2012 3:23 PM
     
     
    Sign In to Vote
    0

    Hi Daniel,

    Only few Logins are effected and I already re-booted the server once :( but even no luck.

    Thanks,

    Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

     
  • Friday, May 18, 2012 3:24 PM
     
     
    Sign In to Vote
    0
    Hi Shamas, the same trick didn't worked for me :(

    Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

     
  • Friday, May 18, 2012 4:33 PM
     
     
    Sign In to Vote
    0

    Hi Daniel,

    Only few Logins are effected and I already re-booted the server once :( but even no luck.

    hello Satish

    could you check if the clock on their computer is not synchronous with the clock of the AD / Kerberos - a difference of more than 5 minutes make the Kerberos ticket invalid.

    could those logins try to connect from another computer where another login successfull ?

    Please use Mark as Answer if my post solved your problem and use Vote As Helpful if a post was useful.

     
  • Friday, May 18, 2012 6:14 PM
     
     
    Sign In to Vote
    0

    Hi Daniel,

    Thanks for ur comment.. I m facing for those users with the 21P only not from other server.

    Thanks

    Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

     
  • Friday, May 18, 2012 8:32 PM
     
     
    Sign In to Vote
    0

    Hi Daniel,

    Thanks for ur comment.. I m facing for those users with the 21P only not from other server.

    Thanks

    21P = ?

    could they connect to the SQL Server with SSMS from another computer using their Windows login ?

    Please use Mark as Answer if my post solved your problem and use Vote As Helpful if a post was useful.

     
  • Saturday, May 19, 2012 12:57 AM
     
     
    Sign In to Vote
    0

    Yes they are able to connect other servers with out any issues,

    Thanks.

    Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

     
  • Saturday, May 19, 2012 10:08 AM
     
     
    Sign In to Vote
    0
    could you check that the SPN (Service Principal Name, Kerberos) are correctly set on the SQL Server ?

    Please use Mark as Answer if my post solved your problem and use Vote As Helpful if a post was useful.

     
  • Sunday, May 20, 2012 4:13 PM
     
     
    Sign In to Vote
    0

    Hi Daniel,

    I esclated this issue to one of our AD engineer in onsite, it seems he resolved that issue.

    I m waiting from him to hear on resolution steps, once i hear back i wil update and thanks to all to be with me up to now :)

    Thanks,

    Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

     
  • Monday, May 21, 2012 7:41 AM
     
     
    Sign In to Vote
    0

    Did you try following steps:

    1- delete required user from all databases you need to work with

    2- delete user from database logins list as well

    3- create new user and create mapping for that user with database

    4- restart db server (optional)

    please also verify that the user you have used to install sql server must also not expired with in last few days.

    Shamas Saeed (if Post helpful please mark as Answer) http://shamas-saeed.blogspot.com

     
  • Monday, May 28, 2012 3:58 AM
     
     Answered
    Sign In to Vote
    0

    Hi All,

    thanks for your comments,

    As I informed earlier, this issue i was escalted to AD engineer, he informed me the windows logins @ AD level were corrupted. So he recreated @ AD level. later i droped and recreated on SQL Server Level, Its working fine now :)

    Thanks,

    Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)