December 2, 2011 at 11:21 am
I have a mostly successful implementation of Kerberos delegation between SQL Servers. However, on occasion I see the classic "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'." error message when running procedures across linked servers. I would say that the delegation works without issue 99.99% of the time. I'm at a loss as to how to troubleshoot / correct this issue, especially because I can't reproduce it. Usually I can just re-run the query that generated the anonymous login error without issue.
What are some efficient and accurate ways to track down what is happening that I would get the anonymous login error? Any help or insight is hugely appreciated.
Thanks.
December 2, 2011 at 11:32 am
Are there any further details about the login failure in either the SQL error log or the system or application event logs?
I have seen something "similar", but it did not actually have to do with a login failure so mush as heartbeat or tcp connection failure.
If you have not checked in the system event logs and application logs as well as server logs, I would start there. The error you see may not have full description of the problem.
A couple references (will not exactly answer your problem but might help if you are seeing a connection issue from any other logging):
http://blogs.msdn.com/b/sql_protocols/archive/2005/09/28/474698.aspx
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply