URGENT---Why I adding new user failed?

  • exec xp_logininfo 'INTL\RTXIE'

    exec xp_logininfo 'Intl\rtxie'

    exec xp_logininfo 'INTL\Rtxie'

    exec xp_logininfo 'INTL\rtxie'

    ALL RETURNS

    Msg 15404, Level 16, State 11, Procedure xp_logininfo, Line 62

    Could not obtain information about Windows NT group/user 'INTL\rtxie', error code 0x534.

    BUT THE ACCOUNT "INTL\Rtxie" IS ALREADY IN SERVER->SECURITY->LOGINS

  • rudy komacsar - Doctor "X" (2/23/2010)


    I would first try to execute:

    exec sp_validatelogins

    If this does not produce any results the next step is to retry xp_logininfo:

    exec xcp_logininfo 'intl\abd

    THIS RETURNS ONLY TWO LOGINS, I have dozens logins in the server logins setting. But the one "INTL\RTXIE" is one of the two logins. Does this mean anything?

  • Then I would check with the AD folks to see if that account was dropped and readded within AD (if it has is got a new SID). This may seem confusing because SQL Server shows you a domain\username but internally it actually uses the AD SID as a token for authentication.

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

  • Please post the SQL executed to return the 2 successful executions and the results.

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

  • rudy komacsar - Doctor "X" (2/23/2010)


    Please post the SQL executed to return the 2 successful executions and the results.

    Sorry I don't quite get you, what do you want me to post?

  • rudy komacsar - Doctor "X" (2/23/2010)


    Please post the SQL executed to return the 2 successful executions and the results.

    Do you want to see the 2 results return by exec sp_validatelogins?

    Here it is:

    SID NT Login

    0x010500000000000515000000FBDB6FA67C557002B8AE62A5423E0000SCGLOBAL\abcd

    0x0105000000000005150000007F4A685C3F382BEA7EB10091BD7B0400INTL\Rtxie

  • what does the output of the following produce:

    exec sp_logininfo 'INTL\Rtxie'

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

  • rudy komacsar - Doctor "X" (2/23/2010)


    what does the output of the following produce:

    exec sp_logininfo 'INTL\Rtxie'

    Msg 15404, Level 16, State 11, Procedure xp_logininfo, Line 62

    Could not obtain information about Windows NT group/user 'INTL\Rtxie', error code 0x534.

  • Have you tried dropping the login from the SQL Server and then readding it ?

    I am guessing that this is the only recourse left.

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

  • There must be something wrong with the ID, INTL\RXie, I dropped it and then try to re-add it, it now pops up "Windows NT user or group 'INTL\Rtxie' not found.

    Although I can search for that user, I am actually logging into another computer using that ID.

    Any idea? It seems like a Active Directory problem again. but then why I was able to add this login before?

  • I think now that it is time to have an AA Admin sit next to you and check as you are doing this.

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

  • I just talked to AD guys, one of the clue is: How SQL talks to AD to authenticate a valid user? is it possible to manually configure (hardcode it) to let SQL talk to a specific Domain Controller? (That INTL has almost 400 DC, it is possible that some of them are down)

  • halifaxdal (2/24/2010)


    I just talked to AD guys, one of the clue is: How SQL talks to AD to authenticate a valid user? is it possible to manually configure (hardcode it) to let SQL talk to a specific Domain Controller? (That INTL has almost 400 DC, it is possible that some of them are down)

    I am unaware of any configuration that would allow you to specify which DC the server contacts. If I remember correctly, Windows broadcasts a request and the "nearest" DC responds to that request. The only thing I can think of at this time is that not all the DC's are insync with the Primary.

    This would be an OS setting, by the way, not a SQL setting. If you can tell the Server which DC to use, then that may work, remembering what I have said above.

Viewing 13 posts - 16 through 27 (of 27 total)

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