Re: Migrating the WSUS database from a Windows Internal Database instance to a SQL Server 2005 instance on a remote server

From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
Date: Fri, 27 Jul 2007 09:53:43 +0000 (UTC)

MartinH (nick@xxxxxxxxxxxxxx) writes:

Oops my bad indeed no brackets. now i do and i get this message. both
sql as the comuter i want added are in the same domain and i can ping
the computer from the sql computer.

Msg 15401, Level 16, State 1, Line 1
Windows NT user or group 'domain\server' not found. Check the name
again.

Is there actually a user with this name? Sue's original post had a $ at
the end:

CREATE LOGIN [YourDomain\ServerName$] FROM WINDOWS

--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.

Follow-Ups:
- Re: Migrating the WSUS database from a Windows Internal Database instance to a SQL Server 2005 instance on a remote server
  - From: MartinH

References:
- Migrating the WSUS database from a Windows Internal Database instance to a SQL Server 2005 instance on a remote server
  - From: MartinH
- Re: Migrating the WSUS database from a Windows Internal Database instance to a SQL Server 2005 instance on a remote server
  - From: Sue Hoegemeier
- Re: Migrating the WSUS database from a Windows Internal Database instance to a SQL Server 2005 instance on a remote server
  - From: MartinH
- Re: Migrating the WSUS database from a Windows Internal Database instance to a SQL Server 2005 instance on a remote server
  - From: Erland Sommarskog
- Re: Migrating the WSUS database from a Windows Internal Database instance to a SQL Server 2005 instance on a remote server
  - From: MartinH

Prev by Date: Re: Changing Default SQL ports on SQL 2000 Server
Next by Date: Re: Migrating the WSUS database from a Windows Internal Database instance to a SQL Server 2005 instance on a remote server
Previous by thread: Re: Migrating the WSUS database from a Windows Internal Database instance to a SQL Server 2005 instance on a remote server
Next by thread: Re: Migrating the WSUS database from a Windows Internal Database instance to a SQL Server 2005 instance on a remote server
Index(es):
- Date
- Thread

Relevant Pages

Re: Login failed for user (null)
... Not associated with a trusted SQL Server connection. ... However, if you deal with the Domain controller, most of the controls there ... > (Windows 2003 server, domain member). ...
(microsoft.public.inetserver.asp.db)
Re: Login failed for user (null)
... Not associated with a trusted SQL Server connection. ... However, if you deal with the Domain controller, most of the controls there ... > (Windows 2003 server, domain member). ...
(microsoft.public.sqlserver.connect)
Re: Login failed for user (null)
... Not associated with a trusted SQL Server connection. ... However, if you deal with the Domain controller, most of the controls there ... > (Windows 2003 server, domain member). ...
(microsoft.public.sqlserver.security)
Re: Login failed for user (null)
... Not associated with a trusted SQL Server connection. ... However, if you deal with the Domain controller, most of the controls there ... > (Windows 2003 server, domain member). ...
(microsoft.public.inetserver.iis.security)
Re: Login failed for ServerGuest
... I think it is not a limitation in Windows 2000. ... access SQL server on Win2000 server by using Windows authenctication if I ... | I have noticed that when I try to log in using Windows Authentication ...
(microsoft.public.sqlserver.connect)