I have a problem creating a particular SQL login from a windows login. SQL is getting a ghost SID that was associated with the windows login before renaming in the AD.
Running SQL2008 Enterprise edition + SP2 on Windows 2008 Datacentre
An Active Directory (AD) account was created for a user [Domain\UserA]
A SQL login was created for the account above and then granted access to a number of databases
The AD account was renamed/modified to [Domain\UserB]
At this stage the user would encounter an error when connecting to the server
The sql log show this error message
Error: 18456, Severity: 14, State: 11.
Login failed for user 'domain\user'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: xxx]
Action on Server 1 SQL (the one with the problem)
Dropped the user from the databases
Re-Created the login from the windows account [Domain\UserB]
Created the user in the respective databases
But the user still unable to connect to the server
On server 1, the SID of the user in SYSUSERS was Matching SYSLOGINS and matches with result of SUSER_SID(Domain\UserA)
But it does not match the SID in the AD
The rest of the servers all have the correct SIDs
When I use SUSER_SNAME(Incorrect-Sid) and SUSER_SNAME(Correct-Sid) on this server they both return [Domain\UserB]
The problematic server is always returning the incorrect SID when recreating the user login and when using SUSER_SID(Domain\UserA) as if it is cached somewhere. Another 4 SQL servers (of different editions 2000 and 2008 standard) are fine and recognise the correct SID.
I can't specify the SID when creating the SQL login because it is using the Windows account
Any idea on how to fix this problem is highly appreciated