Home Forums SQL Server 2008 SQL Server 2008 Administration Renamed AD users' accounts, now some SQL Servers can't get info RE: Renamed AD users' accounts, now some SQL Servers can't get info

  • July 11, 2012 at 12:41 pm

    #1511737

    schleep (7/11/2012)

    We changed some users AD accounts to a new name (samaccountname, displayname, logon, etc..)

    On one SQL server (2 instances), we get the following error on setuser.

    Could not obtain information about Windows NT group/user 'cipsewname', error code 0xffff0002

    On 4 other SQL servers here, setuser with new name works fine.

    Any ideas? I've forced replication of the AD controllers; everything appears OK in AD, there is no trace of the old name.

    Win2K8 R2, SQL 2K8 R2.

    Any ideas?

    Without looking at your machine I suspect that one of those users owned the dbo schema. Go into the DB > Security > Users, open the dbo properties and look at the login name. Does one of those users show up for login name?

    I ran into this recently when removing an old DBA's account from the server - she was the owner of the dbo schema. It had the same error. Setting the owner to a valid user fixed the issue.

    "I cant stress enough the importance of switching from a sequential files mindset to set-based thinking. After you make the switch, you can spend your time tuning and optimizing your queries instead of maintaining lengthy, poor-performing code."

    -- Itzik Ben-Gan 2001