June 4, 2007 at 2:47 pm
Ok,
I have been all over MS website trying to figure out what I'm missing and so far, no success. I am trying to create a new DB login by browsing to my NT domain account. When doing so I receive the following error.
"Windows NT group or user name, "Domain\user" not found.
I know that it is there as I'm using it now. I also check AD and see it is there with no errors showing.
I then looked in the sys.syslogins table and don't see it there either.
What am I missing here? Why can't I create this account?
Thanks!!
Bob
June 5, 2007 at 1:08 am
what's the DDL you are issuing to create the login?
---------------------------------------
elsasoft.org
June 5, 2007 at 2:29 am
I assume you try to create the login through the GUI by selecting new and the browsing the domain. Do you see the account, can you select it ? Or you type directly domain\username in the GUI ?
Is the SQL server in the same domain ? If not are the domain trusted ?
June 5, 2007 at 9:13 am
Good morning,
The account is valid, I am logged in with it on the domain, the server and I are both in the same domain, the login did exist at one time but I had to delete and recreate all logins and DB accounts, which is when my problem started.
Bob
June 5, 2007 at 12:02 pm
Have you tried using T-SQL:
USE MASTER
GO
CREATE LOGIN [domain\user] FROM WINDOWS
GO
USE [database_name}
GO
CREATE USER [domain\user] FOR LOGIN [domain\user]
GO
June 6, 2007 at 6:11 am
June 6, 2007 at 12:09 pm
Ok, so here's where I'm at now.
When I try to create the login via TSQL I get the following.
Windows NT user or group 'nwdc.net\rboursaw' not found. Check the name again.
My sys.syslogins table looks like this (name and loginname):
sa sa
##MS_SQLResourceSigningCertificate## ##MS_SQLResourceSigningCertificate##
##MS_SQLReplicationSigningCertificate## ##MS_SQLReplicationSigningCertificate##
##MS_SQLAuthenticatorCertificate## ##MS_SQLAuthenticatorCertificate##
BUILTIN\Administrators BUILTIN\Administrators
NT AUTHORITY\SYSTEM NT AUTHORITY\SYSTEM
NWDC58AP\SQLServer2005MSSQLUser$NWDC58AP$WFMPROD NWDC58AP\SQLServer2005MSSQLUser$NWDC58AP$WFMPROD
NWDC58AP\SQLServer2005SQLAgentUser$NWDC58AP$WFMPROD NWDC58AP\SQLServer2005SQLAgentUser$NWDC58AP$WFMPROD
NWDC58AP\SQLServer2005MSFTEUser$NWDC58AP$WFMPROD NWDC58AP\SQLServer2005MSFTEUser$NWDC58AP$WFMPROD
##MS_AgentSigningCertificate## ##MS_AgentSigningCertificate##
TCSDBOWNER TCSDBOWNER
TCSADMIN TCSADMIN
TCSACDPROC TCSACDPROC
TCSAPPROC TCSAPPROC
TCSAUTORUN TCSAUTORUN
TCSCHECKER TCSCHECKER
TCSTALLYSERVER TCSTALLYSERVER
TCSUPDATER TCSUPDATER
WFMEXPORTER WFMEXPORTER
WFMIMPORTER WFMIMPORTER
WFMSCHEDEVENT WFMSCHEDEVENT
WFMSSMONITOR WFMSSMONITOR
NWDC-NET\s.tcsservices NWDC-NET\s.tcsservices
NWDC-NET\LLenz NWDC-NET\LLenz
NWDC-NET\LHemphil NWDC-NET\LHemphil
NWDC-NET\s.rtalisten NWDC-NET\s.rtalisten
NWDC-NET\s.wfmdispatcher NWDC-NET\s.wfmdispatcher
RTALISTEN RTALISTEN
I am 100% certain that the accout in the domain is fine.
both teh account and the DB are in the same domain.
Not sure what else to do here and following the above link from the MS site didn't resolve the issue either.
June 7, 2007 at 3:15 am
Hey, maybe I got it use mwdc\username without .net otherwise SQL get a problem....I bet now it will work
June 7, 2007 at 3:59 am
Or NWDC-NET\Username ?
If it ain't broke, don't fix it...
June 7, 2007 at 4:05 am
OK I see your point. Let say, if domain is microsoft.com type microsoft\username
June 8, 2007 at 2:40 pm
I believe that if your SQL Server was installed with a case-sensitive collation, the login name must be specified with the exact same case as how the Windows user account was defined.
November 1, 2018 at 1:49 am
This was removed by the editor as SPAM
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply