15401 Error Sql Server
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: Windows NT user or group ‘username'
Sql Server 2008 Error 15401
not found. Check the name again.This is quite a famous error and I was sql server error 18456 asked to write about it by couple of readers. The reason I was not writing about this as the solution
Sql Server Error 15401 Administrators
of this error is very well explained in Book On Line. All the potential causes and their solutions are explained well here. This post/article should be considered as book mark to solution.Fix/WorkAround/Solution: Refere Microsoft sqlserver 15401 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 - Comparison : Similarity and Difference #TempTable vs @TempVariable July 3, 2007Pinal Dave SQL SERVER - Index Levels, Page Count, Record Count and DMV - sys.dm_db_index_physical_stats July 4, 2010Pinal Dave SQL SERVER - Denali - Introduction to SEQUENCE - Simple Example of SEQUENCE January windows nt user or group not found sql server 2008 29, 2011Pinal 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 Server. Everything seems to work fine. However, under Security -> Logins there are 3 groups that are prefixed by the old server name and also contain the old server name within their name (for example: oldservername\SQLServer2005SQLAgentUser$oldservername$MSSQLSERVER)Can you please advise how to fix it?I found out lots of useful information from your web
Editions: US United States Australia United Kingdom Japan Newsletters Forums Resource Library Tech Pro Free Trial Membership Membership My Profile People Subscriptions My stuff Preferences Send a message Log Out TechRepublic Search GO Topics: CXO Cloud Big Data Security Innovation Software Data Centers Networking
Error 15401 Sql Server 2014
Startups Tech & Work All Topics Sections: Photos Videos All Writers Newsletters Forums Resource Library Tech msg 15401 sql server Pro Free Trial Editions: US United States Australia United Kingdom Japan Membership Membership My Profile People Subscriptions My stuff Preferences Send a message Log
Q322988
Out TechRepublic | Forums | Networks Networks Register Now or Log In to post Welcome back, My Profile Log Out Recent Activity FAQs Guidelines Question 0 Votes Locked SQL Server User Error 15401 - How to work around it? By 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/ esalo · 9 years ago Hi,I get this error message when I try and create a new user in MS SQL Server 2000 by attempting to create a new user with
Start 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 more about hiring http://serverfault.com/questions/247780/sql-server-2008-r2-error-15401-when-trying-to-add-a-domain-user developers or posting ads with us Server Fault Questions Tags Users Badges 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 http://www.swarndeep.com/2009/10/windows-nt-user-or-group-domainuser-not.html it works: Anybody 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 sql server I am trying to add a domain user. I am doing the following. Expand Security Right click on Logins Select New Login... Login name 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 sql server 2008 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 DNS servers are the same on both... sql-server sql-server-2008 sql share|improve this question edited Mar 16 '11 at 11:00 splattne 23.8k1685138 asked Mar 15 '11 at 16:46 Alice migrated from stackoverflow.com Mar 15 '11 at 19:24 This question came from our site for professional and enthusiast programmers. Is this a Virtual Machine? –Robert Miller Jul 26 '11 at 1:36 add a comment| 4 Answers 4 active oldest votes up vote 2 down vote Old question but I had the same issue today on SQL Server 2012 (web) when trying to create a login for a domain user, something I've done numerous times before. The issue for me turned out to be
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-