Login failure messages in log

From: Daryl (darmstro_at_bccancer.bc.ca)
Date: 08/28/03 

Date: Thu, 28 Aug 2003 13:24:59 -0700

Hi,

I'm seeing lots of messages in the SQL Server Logs that
say: "Login failed for user '(null)'. Reason: Not
associated with a trusted SQL Server"

Also, "Login failed for user 'DOMAIN\username'" happens
once a day for two users, even though they login
successfully and authentication is by SQLServer logins.

Are these messages normal? Do they mean something is
setup wrong?
The users are running an application which connects to SQL
Server database using ODBC.

Thanks.
Daryl

Relevant Pages

  • Re: Update string too long?
    ... > And we won't question to reason for this routine as you asked... ... Pro SQL Server 2000 Database Design - ... > support the full length of the inserted data? ...
    (microsoft.public.sqlserver.programming)
  • RE: Identity/Seed Values
    ... is not a substitute for this. ... SQL Server doesn't change the IDENTITY value ... IDENTITY yourself except by deleting and then inserting a row (another reason ... why you shouldn't tie external meaning to an arbitrary IDENTITY value). ...
    (microsoft.public.sqlserver.programming)
  • Re: SQL 2005 Password Expiration
    ... New error codes ... Reason: Password change failed. ... password does not meet policy requirements because it is too short. ... Mike Epprecht, Microsoft SQL Server MVP ...
    (microsoft.public.sqlserver.security)
  • Re: Different results in SQL and Access
    ... This suggests a reason why you are getting different results. ... in MS-Access, with a table Linked to the SQL Server table, I get the ... This email account is my spam trap so I ...
    (microsoft.public.access.queries)
  • Re: Migrating from 97 to 2002+ / JET to MSDE
    ... On the other hand with such system now that includes emailing of data ... If you move to sql server, then it seems reasonable to have each of the ... I see no reason to migrate to sql server unless you going to use the extra ... And, as mentioned, ms-access is not going ...
    (microsoft.public.access.forms)