Recent Posts



« | Main | »

Fix for Login failed for user “. The user is not associated with a trusted SQL Server Connection.

By Jesse | October 8, 2009

This article provides a fix for the error:

Login failed for user “. The user is not associated with a trusted SQL Server Connection. (CLIENT:

This error has several causes- one of which is an application or ODBC connection that is initiated from the same machine as the SQL server (ie the server is connecting to itself). The easiest fix for this is to temporarily or permanently disable the loopback check ….

  1. Edit the registry using regedit.  (start –> run … Regedit <Enter>)
  2. Browse to :  HKLM\System\CurrentControlSet\Control\LSA
  3. Add a DWORD value called “DisableLoopbackCheck”
  4. Set this value to 1

You should now find that the connection will complete successfully.  Another place to check is in event viewer.   For this particular error we had 3 events logged in event viewer:

1. Failure Audit :: Login Failed for user ‘<DOMAIN>\<USERNAME>’. (CLIENT

2. Error :: SSPI handshake failed with error code 0x8009030C while establishing a connection with integrated security; the connection has been closed. (CLIENT

3. Failure Audit :: Login Failed for user “. (CLIENT

The above steps resolve this issue.

Below is an article that discusses in more detail disabling the loopback check.

[] [Digg] [StumbleUpon]

Topics: Uncategorized | 7 Comments »

7 Responses to “Fix for Login failed for user “. The user is not associated with a trusted SQL Server Connection.”

  1. Dirk Niehoff Says:
    January 29th, 2010 at 4:26 am

    Thank you!
    That worked. I had that Problem on a Windows Server 2008R2 with MSSQL Server 2008.
    Now it’s gone :)

  2. Subi Thayamkery Says:
    March 20th, 2012 at 5:19 pm

    Thank you for this fix. Worked for our Windows 7 Sql 2008 environment.

  3. John Says:
    August 9th, 2012 at 4:44 am

    Yeah!!!! this worked. Thanks so much. BTW you can’t copy and paste? Why… you can just view source and why block me the Dword is quite long, making newbies type it just increases the chance they get it wrong.

    thanks anyway

  4. Uttam Says:
    February 26th, 2013 at 12:21 pm

    Thanks you it worked as a charm

  5. Mark Says:
    March 20th, 2013 at 2:38 pm

    I had same error. In my case it was caused by a user trying to hit the SQL when AD account has expired. After changing the password, the error went away.

  6. John Says:
    March 28th, 2013 at 3:59 pm

    This fix worked perfectly on SQL Server 2008 to get the Bakcupexec 12.5 services to start. I had the exact same issue described in this article.

    Well written and thank you for taking the time to help others.

  7. Alexander Hagel Says:
    April 7th, 2013 at 5:24 am

    Thnx! Still works for windows server 2012 with SQL server 2012.