Error 15401 Sql Server Login
Contents |
SERVER - Fix : Error : Error 15401: Windows NT user or group ‘username' not found. Check the name again. June 7, 2007Pinal DaveSQL, SQL Server, SQL Tips and Tricks24 commentsFix : Error :
Sql Server Error 15401 Administrators
Error 15401: Windows NT user or group ‘username' not found. Check sqlserver 15401 the name again.This is quite a famous error and I was asked to write about it by couple
Sql Server 2012 Error 15401
of readers. The reason I was not writing about this as the solution of this error is very well explained in Book On Line. All the potential causes and windows nt user or group not found sql server 2008 their solutions are explained well here. This post/article should be considered as book mark to solution.Fix/WorkAround/Solution: Refere Microsoft Help and Support : How to troubleshoot error 15401Reference : Pinal Dave (http://blog.SQLAuthority.com) Tags: SQL Error Messages, SQL Login, SQL Scripts1Related Articles SQL SERVER - Introduction and Example for DATEFORMAT Command September 28, 2007Pinal Dave SQL SERVER - A Quick Puzzle error 15401 sql server 2014 on JOIN and NULL - SQL Brain Teaser February 10, 2012Pinal Dave SQL SERVER - Install Error - The /UIMode setting cannot be used in conjunction with /Q or /QS February 5, 2016Pinal Dave 24 comments. Leave new Nebu June 8, 2008 5:23 pmpls slove this errorWindows NT user or group ‘username’ not found. Check the name again.Reply David April 13, 2009 4:45 pmHi,I have one suggestion, now that it works for me. I was unable to add a new login for a local windows user on a local sql server just because of case. The Sql Server management studio process would always give my user login like this : AMITY\Dave. In fact, the right case is Amity\Dave.By executing sp_grantlogin "Amity\Dave" it worked fine.Bad GUI tools don't ease the use at all.DavidReply Alice April 30, 2009 12:51 amHi Pinal,I got this err when I tried to manually change the Window group name after the physical server got renamed.After renaming the server, I use sp_dropserver and sp_addserver to bring SQL in sync with the n
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the
Msg 15401 Sql Server
workings and policies of this site About Us Learn more about sp_revokelogin Stack Overflow the company Business Learn more about hiring developers or posting ads with us Database Administrators Questions
Q322988
Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from http://blog.sqlauthority.com/2007/06/07/sql-server-fix-error-error-15401-windows-nt-user-or-group-username-not-found-check-the-name-again/ others in the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Difficulty creating logins on SQL Server 2012 (error: 15401) [closed] up vote 2 down vote favorite I have the following setup A Windows Server http://dba.stackexchange.com/questions/27198/difficulty-creating-logins-on-sql-server-2012-error-15401 2008 machine as a domain controller [DC] A Windows Server 2008 machine running SQL Server 2012 [SQL-A] [Both machines are virtual and are running on virtual box] I am logged into both machines as CONTOSO\Administrator On the DC I create a global security group named domain_group_b in the Users container. Similarly I create a user account named domain_user_b. However when I try to create Windows Authenticated logins on SQL Server using these accounts it doesn't work irrespective of whether I use Transact-SQL or SQL Server Management Studio. I get an error Windows NT user or group 'CONTOSO\domain_user_b' not found. Check the name again. (Microsoft SQL Server, Error: 15401) When I use the "Check Names" feature it does find the user and underlines it. Adding local users works OK. Any ideas? sql-server-2012 share|improve this question edited Oct 19 '12 at 12:10 codingbadger 338520 asked Oct 19 '12 at 2:35 Antonio2011a 1234 closed as off-topic by Jon Seigel, Max Vernon, Mike Walsh, Kin, Mark Storey-Smith Nov 19 '13 at 19:27 This question appears to be off-topic. The users wh
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn http://stackoverflow.com/questions/15089617/windows-nt-user-or-group-domain-user-not-found more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping http://www.swarndeep.com/2009/10/windows-nt-user-or-group-domainuser-not.html each other. Join them; it only takes a minute: Sign up Windows NT user or group 'DOMAIN\USER' not found? up vote 4 down vote favorite 2 I am trying to create users on a SQL server from an sql server Active Directory group as an application I am working with does not natively support Windows authentication and relies upon individual logins being created on the SQL server, as application level permissions are managed in the application rather than using SQL roles. Due to this, each user that is to access the application needs their own user creating against the SQL instance that the applications database is on, so that the user can then be assigned individual 15401 sql server permissions within the application. I am reading the list of users from the Active Directory group we have designated using the following; exec master..xp_logininfo 'domain\groupname', 'members' This returns output similar to the following; account name type privilege mapped login name permission path DOMAIN\USER user user DOMAIN\USER DOMAIN\GROUPNAME For the most part, the users returned in this list can be created on the SQL instance without any drama. I am creating the users as SQL accounts using sp_grantlogin in the first instance, before moving on to allow each new login access to the application database. However, a handful of users are being reported as not existing. I get the following error as a result of running sp_grantlogin; Msg 15401, Level 11, State 1, Procedure sp_grantlogin, Line 49 Windows NT user or group 'DOMAIN\USER' not found. Check the name again. Obviously in the above error message, I have removed the actual username. Why would xp_logininfo return a user that cannot be created with sp_grantlogin? Is there anything obvious that I am missing? sql-server active-directory share|improve this question asked Feb 26 '13 at 12:52 user1451185 support.microsoft.com/kb/324321/en-us –David Brabant Feb 26 '13 at 13:08 the user definitely exists in AD, the potential for the suser_sid being a duplicate is unknown, as select suser_sid('DOMAIN\USER') returns NULL, the domain controller is available (I assume) as I'm able to run
you may see error Windows NT user or group 'Domain\User' not found. Check the name again. (Microsoft SQL Server, Error: 15401). This error message is very general and it does not explain any specific problem or reason itself. Microsoft has a very good article to fix this issue at http://support.microsoft.com/kb/324321/en-us. However, there is another scenario which is not covered in above article (at the time when writing this article) or may be I am the first person who faced this issue. This scenario can be reproduced on Windows 2008 Server with SQL 2008 Server where the Domain Controller is Windows 2000 server. On Windows 2008 server, 2 new policies have been enabled by default that encrypts the secure channel data when new LOGIN request is sent to Domain Controller by Domain member(Also SQL Server). In this scenario, Domain Controller is Windows 2000, thus it does not understand the encrypted request thus refuses the LOGINrequest. All you need to do is to fix this behavior in Windows 2008 (SQL Server) to not to send encrypted secure channel data to Domain Controller. To do this follow the steps below and it should fix the issue. From the SQL Server running Windows 2008 R2, Click Start-> Run and type the command GPEDIT.MSC. This will open the Policy Editor. From Policy Editor Expand "Computer configuration" - > Windows Settings -> Security Setttings -> Local Policies -> Security Options. You will see all security policies on right hand side window. Make changes into the following two policies. Domain member: Digitally encrypt secure channel data (when possible) - Disable this policy Domain member: Digitally sign secure channel data (when possible) - Disable this policy After making these changes, close the policy editor and reboot the box. (Not SQL Server, but restart entire system). In case your local policy does not allow you to make changes, you may have to make changes using Group Policy Management Console. Instructions to install GPMC are located at http://blogs.technet.com/askds/archive/2008/07/07/installing-gpmc-on-windows-server-2008-and-windows-vista-service-pack-1.aspx. Run gpmc.msc (Group Policy Management)