Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a SQL Server 2008 R2 cluster on Win2008 R2. I am unable to add a login for the service account. Any other login I add to this instance works fine and I have been able to add the same service account login to numerous other SQL instances. Moving the instance to other node does not resolve the issue.

when I run

 CREATE LOGIN [DOMAIN\ServiceAccount] FROM windows; 

I get the error

Msg 15401, Level 16, State 1, Line 1
Windows NT user or group 'DOMAIN\ServiceAccount' not found. 
    Check the name again. 

When I run

exec xp_logininfo 'DOMAIN\ServiceAccount', 'all'; 

I get the error

Msg 15404, Level 16, State 11, Procedure xp_logininfo, Line 62
Could not obtain information about Windows NT group/user 
    'DOMAIN\ServiceAccount', error code 0xffff0002. 

Any suggestions would be appreciated.

share|improve this question
Is the machine account properly registered in AD? Can you browse your directory from the GUI? – Eric Higgins Oct 24 '12 at 14:42

Is the service account a domain account? Sounds to me like the service account may in fact be an account that is local to the machine, not a domain account.



If this works, the account is not a domain account.

share|improve this answer

I had a similar issue where the domain controller was in Asia and the SQL Server was in Los Angeles. See if this is relevant to you:

Does this fail with any user you try to create or only specific ones? If it's all then you should look at if you could contact the domain controller from the sql server and the authentication settings described in the bottom of that post.

share|improve this answer
up vote 1 down vote accepted

Thanks for the suggestions but I have found the issue.

The service account was entered in SQL Server Configuration manager with a different case than AD. the instance is case sensitive so I guess when it was validating the name/SID of the login I was trying to create it saw that it did not match the name the engine already knew about with the same SID

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.