Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server

From: Jonas Back (jonasback_at_noway.com)
Date: 05/25/04 

Date: Tue, 25 May 2004 06:24:38 -0700

We have a problem on a SQL Server 2000 with SP3a and
latest security patch running on Windows 2003.

We have several other SQL-servers aswell but this one
seems to have problems with Windows Authentication. It
worked properly first but then when we changed to Windows
authentication and then back to SQL Server and Windows
authentication it stopped working properly. I have
successfully got this problem in my lab aswell (see
below).

The problem: We're running the SQL Service using a
domainaccount (sql1) which is in the local Administrators
group on the server. If I login using this account I can
open Ent Manager using Windows Authentication. I login to
Windows using another domainaccount (user1) that is also
a member of Administrators on the server, when I open up
Ent Manager I get "Login failed for user '(null)'.
Reason: Not associated with a trusted SQL Server
connection.". This is also logged in the Event Log. If I
use SQL Authentication it works. Same goes when I try to
connect remotly to a database with an ODBC-connection.

If I check the permissions I can see that
BUILTIN\Administrators have the System Administrators
role. I also try to att DOMAIN\user1 manually and give
permission. Still doesn't work. The SQL Server is
configured for both SQL Server and Windows Authentication.

I have restarted the server to make sure settings are
changed. I've also looked through MS KB's and found a
registrykey:
HKLM\Software\Microsoft\MSSQLServer\MSSQLServer\LoginMode
and it's set to 2.

In my lab I installed SQL2000. I could use Ent Manager
with both sql1 and user1. Then I switched to Windows mode
and then back to SQL Server and Windows and restarted the
server. Now I have the problem mentioned above and I can
only use sql1 to open Ent Manager.

I've looked through many posts in this forum but none
have supplied with me with any solution.

Relevant Pages

  • Re: Slow booting xp home.
    ... Changing the boot order to boot first from your hard disk might save you a half second, but you won't be able to boot from a CD until you change it back - and the time spent to do that will erase any previous time saved. ... 2- Consider what software you really want to start with Windows and also how you've configured your applications at startup ... Installing and Registering Visual Studio Express Editions Smart Device ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: Slow booting xp home.
    ... Thirty seconds to boot Windows? ... I read somewhere that Microsoft suggest 30s boot up on xp home, I have seen videos on youtube of 8s boot up on xp, I'd be delighted with 30s and happy just to get below a minute. ... Installing and Registering Visual Studio Express Editions Smart Device ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: Windows security
    ... sp_change_users_password only works with SQL Server ... Authentication, not Windows Authentication. ... > Windows NT environment but still have entries in the Microsoft SQL Server ...
    (microsoft.public.sqlserver.security)
  • Re: Very basic login question
    ... Both computers are NOT members of a domain. ... In order to use Windows Authentication the two computers have to be ... you should have a login at the SQL Server on the XP Pro ...
    (microsoft.public.sqlserver.security)
  • Re: Why do I have to enable File and Printer sharing to connect through the XP firewall?
    ... connecting using a Windows account or using a SQL Server account? ... For Windows authentication, SQL Server need to enumerate the SIDs for the account you pass with Windows. ...
    (microsoft.public.sqlserver.clients)
Quantcast