Hello Gary,
If I understand the issue correctly, you are getting error trying to
register the SQL server 7.0 from central admin SQL Server Enterprise
Manager.
Usually there are two types of errors you might get
18452: Login failed for user '%ls'. Reason: Not associated with a trusted
SQL
Server connection.
18452: Login failed for user '(null)'. Reason: Not associated with a
trusted SQL
Server connection.
If the user is 'null', that means that Windows could not pass the
authentication
through. The failure is occurring outside of SQL Server. If the user is not
null,
then the problem is within the SQL Server permissions.
Potential causes,
1. Is the SQL Server listening on the correct protocol with which the
Central Server is trying to connect?
verify actual protocol with
"HKLM\Software\Microsoft\MSSQLServer\Client\ConnectTo" rather
than relying on clicnfg.exe (Client Network Utility)
2. Is the Central server and SQL Server 7.0 on different domain ? If yes,
are they trusted ?
3. Is SQL 7.0 configured for Mixed mode security ?
4. Can you register SQL 7.0 using the IP Address ?
5. Whats is the startup account used for SQL Server 7.0 Service ? Make sure
that
this account has following rights,
- act as part of OS
- logon as a service
- increase quotas
- replace a process level token
6. Make sure that the account which which you are trying to register the
SQL 7.0, has "access this computer from the network" user right on the
SQL Server 7.0 Machine.
Please let me know if the above suggestions help resolve the problem.
Thanks for posting to Microsoft MSDN Managed Newsgroup.
Vikrant Dalwale
Microsoft SQL Server Support Professional
Microsoft highly recommends to all of our customers that they visit the
<a rel="nofollow" style='text-decoration: none;' href="http://www.microsoft.com/protect" target="_blank">http://www.microsoft.com/protect</a> site and perform the three straightforward
steps listed to improve your computer’s security."
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>Content-Class: urn:content-classes:message
>Subject: SQL Server Registration Failed.
>Date: Thu, 6 Nov 2003 05:16:10 -0800
>Lines: 18
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="iso-8859-1"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
>Thread-Index: AcOkaCT0oFvIQ12cRrqAGQR2emf+Gg==
>Newsgroups: microsoft.public.sqlserver.connect
>Path: cpmsftngxa06.phx.gbl
>Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.connect:38673
>NNTP-Posting-Host: TK2MSFTNGXA13 10.40.1.165
>X-Tomcat-NG: microsoft.public.sqlserver.connect
>
>I am having problems registering a SQL 7 database in
>Enterprise manager.
>
>The node that is causing problems is running W2KSP3 and
>SQL7SP3. Each node (bar this one) on our network (VPN) is
>registered with our central admin node for any maintenance
>we need to perform.
>
>I have tried the registration of the troublesome node
>using both NT authentication and the SA account. For both
>instances i get the same login failure for either user:
>
>'Not associated with a trusted SQL Server connection'.
>
>Any help or pointer would be greatly appreciated.
>
>Thanks
>Gary.
>
>> Stay informed about: SQL Server Registration Failed.