Recent Posts

Topics

Archives


« | Main | »

SSPI handshake failed with error code 0x8009030C while establishing a connection with integrated security. Event ID 17806

By Jesse | October 8, 2009

This article is solved in a previous post.

Basically this error is sometimes seen when you are trying to access sql from the SQL server either via ODBC or via an application such as during the installation or RMS (Rights Management Services) .   To resolve this issue you can add the DisableLoopbackCheck registry entry.

this will fix the three errors you may see in Event Viewer on the SQL server.  These errors are:

Failure Audit :: Login failed for user ‘<DOMAIN>\<USERNAME>’. (CLIENT x.x.x.x)     where domain and username are the ones supplied to access SQL.

Error :: SSPI handshake failed with error code 0x8009030C while establishing a connection with integrated security; the connection has been closed (CLIENT: x.x.x.x)   — Event ID 17806

Failure Audit :: Login failed for user “. The user is not associated with a trusted SQL Server connection.

To see the full resolution of this issue please follow this link.

_______________________________________
PLEASE HELP BY BOOKMARKING OUR SITE...
[del.icio.us] [Digg] [StumbleUpon]

Topics: Uncategorized | 1 Comment »

One Response to “SSPI handshake failed with error code 0x8009030C while establishing a connection with integrated security. Event ID 17806”

  1. How to Set Up Aliases For Named Instances In SQL Server « 36 Chambers – The Legendary Journeys: Execution to the max! Says:
    April 8th, 2010 at 7:12 pm

    […] looked all over the internet for a while, and eventually hit on the solution.  That came from this post, which is actually on an only tangentially related […]

Comments