| Author |
Topic |
|
dwhritenour
Starting Member
6 Posts |
 Posted - 2008-06-27 : 14:18:26
|
| Here is the problem in a nutshell:•In SQL Server 2005, when I attempt to create a Login using a 'user' created account, I get a 15401 error. In other words, I can only create SQL Server Logins using 'BUILTIN' accounts that Windows Server automatically creates (i.e. 'BUILTIN\Users').•The exact error is: Windows NT user or group 'TITANFCI\Domain Users' not found. Check the name again. (Microsoft SQL Server, Error: 15401)•I have been through Microsoft's "How to troubleshoot error 15401 (Article ID : 324321)" located at http://support.microsoft.com/?kbid=324321 but none of this information applies to me. The SQL Server’s default collation is set to case sensitive (do not know why) but it does not matter what case is used to enter the SQL logins, the same error occurs.•I have been working the Microsoft Tech Support and have eliminated Active Directory as a potential problem. At this point, Microsoft Tech Support has given up. •As a side note, I have SQL Developer Edition installed on my workstation (within the same some domain) and I do not have these problems. So, I am fairly confident that the problem is specific to this instance of SQL Server installed on the Primary Domain Controller.•We are a small, single domain and single server company. SQL Server 2005 Standard Edition is installed on the domain controller. Unfortunately, I did not perform this install so I can not vouch for its integrity.David Whritenour |
|
|
maninder
Posting Yak Master
100 Posts |
Posted - 2008-06-27 : 15:03:08
|
| Does this Login Exists as a Server principal (in Security under you Servername)Maninder |
 |
|
|
dwhritenour
Starting Member
6 Posts |
Posted - 2008-06-27 : 15:40:03
|
| I am unclear what you are asking.Could you please explain futher?David Whritenour |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-06-27 : 15:42:37
|
quote:
Originally posted by dwhritenour
I am unclear what you are asking.Could you please explain futher?David Whritenour
Check this out:http://support.microsoft.com/kb/324321 |
|
|
|
maninder
Posting Yak Master
100 Posts |
Posted - 2008-06-27 : 15:47:15
|
| Try this : I am gonna talk in laymans Terms:Under your serverName, you should see a Security Group.(I am not talking about Database/security)right click and New Login.Create a Login here.Now goto your Database, where you want to add this user, double click on Database name then right click on Security and NEW-> User.Add the Newly Created Login here.and you are good to go.Maninder |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-06-27 : 15:49:36
|
quote:
Originally posted by maninder
Try this : I am gonna talk in laymans Terms:Under your serverName, you should see a Security Group.(I am not talking about Database/security)right click and New Login.Create a Login here.Now goto your Database, where you want to add this user, double click on Database name then right click on Security and NEW-> User.Add the Newly Created Login here.and you are good to go.Maninder
Once you give permission in server level, why you have to go database level and again give permission.Doesn't make sense.Try the link that should help you. |
|
|
|
maninder
Posting Yak Master
100 Posts |
Posted - 2008-06-27 : 16:01:07
|
| It was in Laymans Terms:He can Do it while in the SQL Server login Dialog. but to make things easier on him... Maninder |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-06-27 : 16:06:59
|
| maninder, you are missing the point of this thread. How would the user exist in the server principals if he can't even add it?sodeep, the poster already said he looked at that. Check his very first post.Both of you need to read threads more closely.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
|
|
|
maninder
Posting Yak Master
100 Posts |
Posted - 2008-06-27 : 16:21:12
|
| Well, i am trying to get the simplest answers out from the use when he says " when I attempt to create a Login using a 'user' created account, I get a 15401 error. In other words, I can only create SQL Server Logins using 'BUILTIN' accounts that Windows Server automatically creates " ???so, it seems He either has a login as a Server Principal, or He has a database user and he is trying to create it as a server Principal and add it to Database as well.. I might be wrong at the interpretation.. but still am waiting for the user to RESPOND.Maninder |
|
|
|
dwhritenour
Starting Member
6 Posts |
Posted - 2008-06-27 : 16:39:51
|
| Okay, let me simplify this…Within SQL Server Management Studio > Server Name > Security > Logins.If I right click > New Login and choose anything but a Builtin Windows NT account (i.e. Builtin\Users) as a login name, I will receive the above error. Domain groups and user accounts do not work.David Whritenour |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
dwhritenour
Starting Member
6 Posts |
Posted - 2008-06-27 : 16:52:31
|
| Yes Tara.It always seems to be a very difficult task to get MS to escalate a case. I do not know if it is pride or policy. I am still waiting on a response from tech support regarding this request.David Whritenour |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-06-27 : 23:49:51
|
| Is sql server in same domain with the account? |
|
|
|
dwhritenour
Starting Member
6 Posts |
Posted - 2008-06-28 : 14:27:49
|
| Yes, it is a single domain network.David Whritenour |
|
|
|
dwhritenour
Starting Member
6 Posts |
Posted - 2008-06-28 : 15:28:07
|
quote:
Originally posted by tkizer
dwhritenour, have you asked that your MS case be escalated?Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/
Tara, any suggestion on how to get MS to escalate my case. The tech I am working with is stonewalling me and I am really beginning to get frustrated.David Whritenour |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-06-28 : 17:55:17
|
| Does your company have a support agreement with MS, which gives you a representative? We escalate through our TAM (the representative, can't remember what TAM stands for). If you don't have a TAM, then I'd suggest asking to speak to the person's supervisor if they are unwilling to escalate. If they are unwilling to give you to their supervisor, then I'd hang up and call back into the call center and explain the situation to the operator. They will probably be able to get you to the SQL Server PSS lead.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-06-29 : 08:09:54
|
| TAM- Technical Account Manager. |
|
|
|
|
Trouble adding SQL Server Logins