Error 15401 Sql 2000
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: SQL 2000: Error 15401: Windows NT User or group 'network\ASPNETACCESS' not found.
Error 15401 Sql Server 2000
Check the name again. For "virtual" users only. SQL Server > SQL Server error 15401 sql server 2012 Manageability Question 0 Sign in to vote Hi everybody. I'm not sure if this is the right forum. sql server error 15401 administrators I have a client that is experiencing the following error message in SQL 2000 when trying to add a domain user that would also be shared by the web server:
Microsoft Sql Server Error 15401
Error 15401: Windows NT User or group 'network\ASPNETACCESS' not found. Check the name again. Of course, I have actually changed the name of the user and network but still, largely the same. When adding users that are used for normal user accounts (like Mike Plumpkin or some other random person) it works fine. Does anybody know the reason or
Windows Nt User Or Group Not Found Sql Server 2012
can anybody think of a reason for this? The server recently had to go through a catastrophic rebuild of AD and the SQL databases also had to be recovered from some crashed drives. (Word to the wise, never, EVER trust your client when they say their backups are being taken care of). The Domain users themselves already exist in AD to be added. We also ran the SQL script recommended in: http://support.microsoft.com/kb/324321/en-us to see if there were any duplicate SIDs. (there were none) Anybody seen this before? I've confirmed that the SQL Server can see the users I am looknig for if I browse for them with the ... button when attempting to add them. Also the top of the error window says: Microsoft SQL-DMO (ODBC SQLState: 42000) It does not seem to write anything to the SQL event logs when I attempt this either. SQL 2000 SP4 Is there anything else I should post? MCSE 2003, Exchange. MCTS Vista, 7. Administrator of awful, neglected website http://timssims.net Edited by Timssims Wednesday, September 14, 2011 9:09 PM
Follow me on Twitter Search this Blog Archives June, 2009 (1) March, 2009 (3) February, 2009 (3) January, 2009 (3) November, 2008 (6) October, 2008 (3) September, 2008 windows nt user or group not found sql server 2014 (4) August, 2008 (10) July, 2008 (1) June, 2008 (2) May, 2008 (6) April,
Error 15401 Sql Server 2014
2008 (6) March, 2008 (4) February, 2008 (8) January, 2008 (8) December, 2007 (3) November, 2007 (2) October, 2007 (5) September, 2007 msg 15401 sql server (3) August, 2007 (4) Post Categories C# (rss) T-SQL (rss) Consulting (rss) Notification Services (rss) Other Technologies (rss) Off Topic (rss) SQL Server (rss) Misc (rss) Current Events (rss) Community (rss) Reporting Services (rss) About https://social.msdn.microsoft.com/Forums/sqlserver/en-US/18ce02d0-78e0-47df-8f96-02e4d25e477c/sql-2000-error-15401-windows-nt-user-or-group-networkaspnetaccess-not-found-check-the-name?forum=sqlkjmanageability me Recent Tweets (rss) << SQL Server 2000: when were the statistics updated? | Home | SSNS Status Codes >> Error 15401 when creating a new Login Recently, a client asked that I grant database access for several of their new employees. The client uses SQL Server 2000 and has an Active Directory in place to manage domain users and resources. Windows Authentication is used almost exclusively in this environment. As I http://weblogs.sqlteam.com/joew/archive/2007/09/07/60323.aspx dutifully created the new Logins, granted access to the required databases, and assigned the users to the appropriate database roles, everything went as expected - that is, until I got to the last two employees on the list. As I attempted to create a new Login for those two employees, I received the following error: Error 15401: Windows NT user or group MYCLIENT\Sally not found. Check the name again. Fortunately, I had seen this error before and knew its likely cause. Each user in Active Directory is given a unique security identifier, or SID. It's statistically impossible for any two users to receive the same SID. A SID is associated with a user account throughout its existence. SIDs are the reason why you cannot simply create a new user account of the same name to replace a user account that was inadvertently deleted and expect the permissions and group membership to transfer over to the new user account. A SID also persists through name changes to the user account. If a domain user account is renamed to something completely different, its SID remains the same. If you rename a user account from John Brown to Sally Smith, the Active Directory considers this the same user account. That's what happened in this cas
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 7,2000 » Administration » Error http://www.sqlservercentral.com/Forums/Topic630089-5-1.aspx 15401 happened when add windows login... Error 15401 happened when add windows login http://www.swarndeep.com/2009/10/windows-nt-user-or-group-domainuser-not.html to SQL server 2000 Rate Topic Display Mode Topic Options Author Message Judy WhyJudy Why Posted Monday, January 5, 2009 1:12 PM Mr or Mrs. 500 Group: General Forum Members Last Login: Friday, January 22, 2016 7:54 AM Points: 568, Visits: 823 I know this maybe not a right place to ask this sql server question. but somebody maybe came accoss this error before. please help me.One new windows user added to domaim controller. very brand new. not rename from old user/account. From Domain server, I Can see this user. I can schedule a meeting with this user.when I added this user to SQL server 2000, I can select from dropdown list , but when I click ok, it saids, "the error 15401 sql login 'domainname\username' does not exist. error 15401". same thing happened when I used sp_grantlogin.the following way I have tried:1. SELECT name FROM sysxlogins WHERE sid = SUSER_SID('domainname\username') no record returned.2. database is case insensitive.3. add registry key to set LaslookupCacheMaxSize=0 in SQL server 2000 server, in my computer, in user computer. no working.please advise me what I should do.Thanks Post #630089 Nicholas CainNicholas Cain Posted Monday, January 5, 2009 2:07 PM SSCrazy Group: General Forum Members Last Login: Wednesday, October 5, 2016 1:21 PM Points: 2,038, Visits: 6,198 Could you retrieve the SID from AD and then see if there is a matching SID within sysxlogins, just as a confirmation of it not existing? Shamless self promotion - read my blog http://sirsql.net Post #630132 Judy WhyJudy Why Posted Monday, January 5, 2009 2:19 PM Mr or Mrs. 500 Group: General Forum Members Last Login: Friday, January 22, 2016 7:54 AM Points: 568, Visits: 823 Thanks for your reply. I have permision to logon to AD server. But I don't know how to retrieve SID for this user.Another thing I just noticed is that error in SQL server event log. "The Group Policy client-side extension Folder Redirection
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 2