Bamboo Nation
Your SharePoint Community - Powered by Bamboo Solutions

Getting Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'

rated by 0 users
Not Answered This post has 0 verified answers | 2 Replies | 1 Follower

Not Ranked
2 Posts
Points 27
Jensterd posted on Fri, Jun 1 2012 4:58 PM

Help!

We're using the DVWP to display information contained in a SQL table on a SharePoint page.    It's a simple farm - SharePoint 2007 web/app on a single server, and SQL 2008 on another server.  We use Windows authentication in the webpart.  For most of our users, things work fine.  But for some users, the web part does not render but displays the following message:

Bamboo Error - Message :SetWorkOn Data; : GetKeyFieldsName::

On the SQL side, the following error appears:

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors.

Any help would be greatly appreciated - thanks!

All Replies

Top 25 Contributor
103 Posts
Points 1,729
Reply
Huyen Ly replied on Mon, Jun 4 2012 7:08 AM

Hello Jensterd,

Per our online documentation:
Select the Windows Authentication option if you always want to use the current user to access the SQL database. You must have enabled Windows Authentication as the Authentication Mode in SQL Server to use this option, and SQL Server must be installed on the same server as the Web front-end server (such as in a standalone SharePoint installation).
For additional details:
http://store.bamboosolutions.com/onlinedoc/#appid=3903&anchor=sql

Unfortunately this means we do not fully support "Windows Authentication" in your environment because of a problem called "round robin" where credentials become "Lost" between servers communication. 

I'm not entirely clear why it works some users and not others tough, that is a puzzle. Bamboo recommends that you use the SQL Login credentials instead of using "Windows Authentication" option.

If you have any further questions or problems, please let us know.

Regards,
Huyen Ly

  • | Post Points: 22
Not Ranked
2 Posts
Points 27
Reply
Jensterd replied on Wed, Jun 13 2012 10:38 AM

Hi Huyen:

I appreciate your answer. What's interesting is that this has been working great in our SharePoint installation for the last 3 years - and only started to come up with issues when we migrated from Windows Server 2003 to Windows Server 2008 R2 DCs.

I'd like to do more troubleshooting - can you give me more insight on why the messages "SetWorkOnData" and 'GetKeyFieldsName" are apperaing.

Thanks,

Jen

  • | Post Points: 5
Page 1 of 1 (3 items) | RSS
Bamboo Solutions Corporation, 2002-2013