Post reply

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

  • August 3, 2005 at 2:56 am

    #102683

    Hello there,

    I'm having some problems with a SQL Server 2000 SP3 cluster on Windows 2000 Advanced Server.

    It have mixed authentication, and the users use Windows users to log in.

    The instance was OK until monday. It started to give these errors:

    1. (the most important) When the users try to connect, they get this error:

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

    I also cannot connect with the enterprise manager. With a Windows user or SQL user.

    This problem fixes when I restart the instance, but will be down again in about 1 or 2 hours.

    In the event viewer I don't have any entry.

    In the SQL Server log I only have this:

    WARNING: Failed to reserve contiguous memory of Size= 131072.

    Query Memory Manager: Grants=0 Waiting=0 Maximum=153651 Available=153651

    (...)

    Error: 17882, Severity: 18, State: 1

    Does anyone have a idea?

  • August 3, 2005 at 3:10 am

    #579059

    I'm going to install a fix...

    http://support.microsoft.com/?kbid=891311

  • August 4, 2005 at 3:11 am

    #579469

    Just on a side note.. we are using NT authentication only and yesterday I received precisely the same error message when I changed my domain password from another computer, and then continued to work on my own PC without restarting (forgot to logoff/logon after the password change).

  • August 4, 2005 at 3:33 am

    #579479

    I have just install the SP4, but still having the same problem...

  • August 4, 2005 at 5:25 am

    #579503

    Hi,

    are there any events in the system event log about not finding the nt domain server?

    karl

    Best regards
    karl

  • August 4, 2005 at 5:48 am

    #579509

    In the begining I thought that that was the problem. But in the event viewer is not a error of that kind :-/

  • August 4, 2005 at 6:31 am

    #579526

    I see this problem any time my SQL Server looses contact with a Domain Controller (it doesn't switch to another DC, either). Also as Vladan suggested, if you are running SQL as a domain user, check the account to see if it's getting locked out.

  • August 4, 2005 at 7:53 am

    #579565

    Hello Jerry, if the problem were this, I could do login with a SQL Server user, but I get the same error with both kind of users...

  • August 4, 2005 at 9:13 am

    #579621

    Could it be that SQL Server Agent or MSSQLService is running under an account that has expired?

  • August 4, 2005 at 9:26 am

    #579627

    You're right David. Sorry, I missed the SQL logon failure part. Could it be you are running out of memory to support new connections?

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply