Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Login failure for user 'NT AUTHORITY\ANONYMOUS LOGON' Expand / Collapse
Author
Message
Posted Monday, December 16, 2013 6:05 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, February 18, 2016 7:52 AM
Points: 31, Visits: 145
Would someone help with error message that a developer kept getting when editing some custom made stored procedures and trying to execute them.

Msg 18456, Level 14, State 1, Line 1
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

I googled it and some sugest that to create user 'NT AUTHORITY\ANONYMOUS LOGON' and give execute access to it on these stored procedures and I did and still does not work. Some suggest to also modify the registry by entering a key in the Lsa "TurnOffAnonymousBlock" with a value of 1 and reboot the server. I did that and still does not work.

I don't know what else to do. Your help will be greatly appreciated.

Regards
Post #1523177
Posted Monday, December 16, 2013 6:21 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 3:40 AM
Points: 14,306, Visits: 37,372
look at the stored procedure in question...i'd bet it is referencing a linked server. the login is failing at the linked server because whoever is calling it doesn't have mapped credentials set up.

accessing a linked server is probably being blocked by how it is set up; it's probably set up witht eh radio button below that says "be made without a security context"


Lowell

--
help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!
Post #1523182
Posted Monday, December 16, 2013 6:28 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, February 18, 2016 7:52 AM
Points: 31, Visits: 145
Thanks very much for replying. I have used the sa account by logging as the sa and try to execute the stored procedure and still does not work. I have realized, it does not matter what user is used, it is problematic and that is what puzzled me about this.
Post #1523187
Posted Monday, December 16, 2013 6:50 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 3:40 AM
Points: 14,306, Visits: 37,372
whoops i cross posted from anotehr post;
can you show us /script out your linked server?
that would help us diagnose the issue for you.


Lowell

--
help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!
Post #1523195
Posted Monday, December 16, 2013 1:27 PM
SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Monday, May 9, 2016 6:53 AM
Points: 649, Visits: 603
Check the Login failure error from sql error log and identify the status there after.

This may help
http://sqlblog.com/blogs/aaron_bertrand/archive/2011/01/14/sql-server-v-next-denali-additional-states-for-error-18456.aspx
http://blogs.msdn.com/b/sql_protocols/archive/2006/02/21/536201.aspx
Post #1523413
Posted Wednesday, December 18, 2013 6:11 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, February 18, 2016 7:52 AM
Points: 31, Visits: 145
Hi Lowell,

You were right on the money. It was the linked server remote userd on the other side (in Europe) that did not have the right access. That user was mapped as "public". After I called the DBA in Europe to map that remote linked server user with read access to the proper database, all was fine.

Thanks very much for your help, it was very much appreciated. Kudos to you.

Regards,
Reynold
Post #1524085
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse