Error 15401 Windows Nt User Or Group Not Found
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 error 15401 sql server 2012 : Error 15401: Windows NT user or group ‘username' not found. Check error 15401 sql server 2014 the name again.This is quite a famous error and I was asked to write about it by couple windows nt user or group '\administrators' not found. 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
Msg 15401 Sql Server
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 SQLAuthority News - Presenting at Virtual Tech Days TechEd Pre-Con - February 9, 2011 February 7, 2011Pinal Dave sp_revokelogin SQL SERVER - 2008 - Interview Questions and Answers - Part 6 September 17, 2008Pinal Dave SQL SERVER - Count Duplicate Records - Rows July 11, 2007Pinal 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 new server name. Then I restart SQL
Azure(1) Code Samples(2) Data Collector(3) DB Maintenance(6) Dude Musings(1) FTS (Full-Text Search)(3) General Thoughts(3) Indexing(4) Memory(1) Opinion Poll(1) Performance(6) q322988 PowerShell(1) Query Optimization(2) Security(10) Setup(4) SQL News(5) Startup(2) Startup & Recovery(1) Storage
Microsoft Sql Server Reported Sql Message 15401 Severity 16
Engine(2) T-SQL(12) Tools(3) Uncategorized(1) Webcast(1) Windows(2) Archaic Posts Archaic Posts Select Month September 2016 (1) June 2016 (4)
Sp_grantlogin
May 2016 (2) April 2016 (1) February 2016 (1) December 2012 (5) October 2012 (2) September 2012 (1) August 2012 (1) July 2012 (2) June 2012 (2) May 2012 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/ (4) April 2012 (3) March 2012 (3) February 2012 (2) January 2012 (4) December 2011 (1) October 2011 (2) September 2011 (3) August 2011 (9) July 2011 (2) Partitioned By Date() October 2012 M T W T F S S « Sep Dec » 1234567 891011121314 15161718192021 22232425262728 293031 Recent Posts Azure Automation - How to get your https://thesqldude.com/2012/10/17/error-15401-when-trying-to-create-a-new-windows-login/ 1st Runbook workingproperly… Scan, Find & Understand Missing Indexes in your SQLDatabase Seek & Evaluate Unused Indexes in your SQLdatabase Checklist for SQL Server Database Audit & SecurityHardening Seek & Understand Top Indexes by Size in your SQLdatabase Seek & Destroy Duplicate Indexes in your SQLDatabase SQL Server 2016 - General Availability DateAnnounced Quick SQL Server Info -Script theSQLDude - Back from DownUnder.. A scenario on Query Tuning–Included Columns are a goodthing! Posts by Date() October 2012 M T W T F S S « Sep Dec » 1234567 891011121314 15161718192021 22232425262728 293031 NetworkedBlogs NetworkedBlogsBlog:The SQL Dude!Topics: Database, Thesqldude, Sql Server Follow my blog Hash Tags Auditing Azure Code Samples Data Collector DB Maintenance Dude Musings FTS (Full-Text Search) General Thoughts Indexing Memory Opinion Poll Performance PowerShell Query Optimization Security Setup SQL News Startup Startup & Recovery Storage Engine T-SQL Tools Uncategorized Webcast Windows Feed theSQLDude RSS - PostsRSS - Comments Vistor's Location (Eye of Sauron) FREE Email Subscription Enter your email address to subscribe to this blog and receive notifications of new
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings http://serverfault.com/questions/247780/sql-server-2008-r2-error-15401-when-trying-to-add-a-domain-user and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges http://www.swarndeep.com/2009/10/windows-nt-user-or-group-domainuser-not.html Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody sql server can ask a question Anybody can answer The best answers are voted up and rise to the top SQL Server 2008 R2 Error 15401 when trying to add a domain user up vote 6 down vote favorite I am trying to add a domain user. I am doing the following. Expand Security Right click on Logins Select New Login... Login name 15401 sql server select search Click on location and select entire directory Type username Click checkname The name goes underlined and add some more info Click OK Click OK I then get the following error: I have found http://support.microsoft.com/kb/324321. The Login does exist There is no Duplicate security identifiers Authentication failure I don't think is happening as I can browse AD Case sensitivity should not be the problem as I am doing the checkname and it is correcting it. Not a Local account Name resolution again I can see the AD I have rebooted the server (VM) and the issue is still happening. Any ideas? Edit I have also: Domain member: Digitally encrypt secure channel data (when possible) – Disable this policy Domain member: Digitally sign secure channel data (when possible) – Disable this policy Rebooted server http://talksql.blogspot.com/2009/10/windows-nt-user-or-group-domainuser-not.html Edit 2 I have also: Digitally encrypt or sign secure channel data (always)- Disabled Rebooted Edit 3 Since the question have moved site I no longer haves access to comment etc... I have checked the dns on the server to a machine where it is working. The DN
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) Expand your Domain Go to and select and then follow steps 2 and 3 from above. Newer Post Older Post Home Subscribe to: Post Comments (Atom) About Me Swarndeep's Blog Archive ► 2016 (2) ► September 2016 (1) ► May 2016 (1) ► 2015 (3) ► November 2015 (1) ► October 2015 (2) ► 2012 (1) ► September 2012 (1) ► 2011 (2) ► December 2011 (1) ► October 2011 (1) ► 2010 (3) ► August 2010 (1) ► June 2010 (1) ► May 2010 (1) ▼