Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Login failure for user 'NT AUTHORITY\ANONYMOUS LOGON'


Login failure for user 'NT AUTHORITY\ANONYMOUS LOGON'

Author
Message
rjoseph
rjoseph
SSC Rookie
SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)

Group: General Forum Members
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
Lowell
Lowell
SSChampion
SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)

Group: General Forum Members
Points: 14955 Visits: 38949
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!

rjoseph
rjoseph
SSC Rookie
SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)

Group: General Forum Members
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.
Lowell
Lowell
SSChampion
SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)

Group: General Forum Members
Points: 14955 Visits: 38949
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!

suneel kamavaram
suneel kamavaram
SSChasing Mays
SSChasing Mays (651 reputation)SSChasing Mays (651 reputation)SSChasing Mays (651 reputation)SSChasing Mays (651 reputation)SSChasing Mays (651 reputation)SSChasing Mays (651 reputation)SSChasing Mays (651 reputation)SSChasing Mays (651 reputation)

Group: General Forum Members
Points: 651 Visits: 613
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
rjoseph
rjoseph
SSC Rookie
SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)

Group: General Forum Members
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
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search