February 4, 2010 at 8:25 pm
I just installed SS2K8 Developer on W2K8 (64-bit) and am in the process of configuring/setting up. I can fire up Management Studio locally on the server and log in with Windows Authentication as domain admin.
When I try to create a login using a domain user, either through the GUI by typing it in or searching for the user via the search button, or via DDL, I get a 15401 error: "Windows NT user or group '<domain>\<user>' not found." This is a fresh install; no logins exist except the <machine>\administrator one I added during install and the builtin ones.
I tried the basics in http://support.microsoft.com/kb/324321/en-us and none apply. I can ping the DC, the collation is CI and DNS seems okay.
Can anyone help diagnose this?
Additionally, all services are running as NT AUTHORITY\NETWORK SERVICE. Could this be the issue?
February 5, 2010 at 1:44 am
You'll need the account you open management studio with to be a sysadmin. You should have defined the administrator account(s) for SQL Server during install. If you didn't then you might have a problem -
Nothing obvious other than that springs to mind for such a failure.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
February 10, 2010 at 1:38 pm
Well, I've done a couple of things, so I am answering my own question for posterity's sake.
The W2K8 R2 was actually a clone of a master install, all virtual images. Turns out that the event log was kicking up SID-related messages. Also, I was having issues applying the service pack, getting installer errors due to a .NET issue.
After a fresh reinstall of the OS and an SQL server hotfix which allowed the service pack to install, I am now easily able to add domain users to the logins list.
February 10, 2010 at 4:45 pm
For cloned installs Microsoft has a tool that you could run to prevent the SID problem. Take a look at NewSID and SysPrep.
Thanks for posting back with the resolution.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
February 10, 2010 at 6:20 pm
Yeah. What confused me was the information at the top of NewSID's page about how the program was being pulled because it wasn't necessary. In fact, I did find an old download and used it on the server, at which point I was unable to boot the machine and it would BSOD at startup.
However, events in the Event Log clearly indicated my budding SQL Server was not happy with with the SID matching not only other servers, but one that was a domain controller.
Instead of sysprepping, I just rebuilt the server just to be sure it was all clean.
February 10, 2010 at 6:55 pm
Must be part of the reason for pulling NewSID. Good information.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply