• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2169
  • Last Modified:

Error adding domain account to SQL Server in 2008 R2 AD

We are having an issue adding a domain user as an SQL server login.
Environment:
Server: SQL Server 2008 R2, Windows 2008 R2. Computer is on a domain
Domain Controller: Windows 2008 R2, Active Directory on same machine, running on 2008 R2 compatibility mode (not 2000 or 2003 mode as in other posts on this problem!).

When we try to add a domain user to Sql server we get an error 15401 (user or user group not found). However, the active directory can be browsed from that machine - we see the domain users when browsing them in sql server but cannot add them.

The problem has identical symptoms like the often-discussed problem found in Windows 200/2003 active directories and we tried all suggestions we found for this (MS hotfix, kicking the server out of the domain and back in, changing group policy, even disabling the firewall for a moment). Nothing works. It doesn't matter if we try to add the login after having logged into Windows with a local or a domain account. We can add local users as new logins to SQL server without a problem. The behaviour is identical on a second (test) machine running only SQL Server Express 2008 R2 on Win2008R2.

Any ideas how to solve this?

BTW: We stumbled across this when trying to install Team Foundation Server - it's setup stops with a message that the domain controller is unavailable. However, the DC is available as we can login with domain accounts and browse the AD from that server with no problem. We couldn't get this to work so I figured I give it a try in SQL server.
0
NilsIT
Asked:
NilsIT
  • 2
  • 2
2 Solutions
 
Marten RuneSQL Expert/Infrastructure ArchitectCommented:
Is it possible that this name of ther user/group has been altered in the AD?
if so check: http://social.msdn.microsoft.com/forums/en-US/sqlsecurity/thread/240775af-690a-46bf-be21-e1ae63ea024e
(there is also a hotfix at the end of this thread)

This article shows how to errorseek it: http://support.microsoft.com/kb/324321/en-us

//Marten
0
 
NilsITAuthor Commented:
We found the problem was that we used cloned Hyper-V virtual machines that had been cloned AFTER installing Windows Server but without using the sysprep utility. Of course we changed the Netbios name and joined the domain after cloning. Everything SEEMED to work fine but then we got these strange Active Directory errors.

We solved the problem by creating a new virtual machine and installing Windows on it from the scratch (instead of cloning an existing virtual machine). The AD-related problems both in SQL server and Team Foundation Server are gone.

Thank you martenrune for pointing me to that thread as it contained a hint by Chris that the problem can be related to cloned virtual machines.
0
 
Marten RuneSQL Expert/Infrastructure ArchitectCommented:
Glad to se it resolved
//Marten
0
 
NilsITAuthor Commented:
Solution is described in comment NilsIT
0
 
Tec-FuturesCommented:
I had the same issue and ran sysprep to resolve the problem. Removed servers from network and added them back.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now