Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 295255 - Last Review: November 14, 2007 - Revision: 5.2
Error message when you try to link a table in an Access project: "Login Failed for User 'NT AUTHORITY\ANONYMOUS LOGON'."
This article was previously published under Q295255
Advanced: Requires expert coding, interoperability, and multiuser
skills.
This article applies only to a Microsoft Access project (.adp).
On This Page
SYMPTOMS
When you try to link a table in a Microsoft Access project
(.adp), you may receive the following error message:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
CAUSE
You are not using a Windows 2000-based computer with
Security Account Delegation enabled; therefore, Windows 2000 Security is not supported
between servers. Without
Security Account Delegation enabled, SQL Server tries to log on to the Linked Server
anonymously.
RESOLUTION
To avoid this behavior, use one of the following
workarounds:
- Specify a SQL Server logon and password that is valid on
the linked server.
- Enable Security Account Delegation between the SQL Servers. To support this option, both SQL Servers
must be running on Windows 2000.
For more information, see the
"Security Account Delegation" topic in SQL Server 2000 Books Online, which is available for download at the following Microsoft Web
site:
MORE INFORMATION
Steps to reproduce the behavior in Access 2003 and in earlier versions of Access
- On a Windows 2000-based computer that does not have Security Account Delegation enabled, create a new Access project, and then connect to SQL
Server data using Windows NT Integrated Security.
- On the File menu, point to Get External Data, and then click Linked Tables.
- In the Link Table Wizard dialog box, click Linked Server, and then click Next.
- In the Select Data Source dialog box, click New Source.
- In the Data Connection Wizard dialog box, click Microsoft SQL Server, and then click Next.
- In the Server Name box, enter a different server name from the one that you
connected to in step 1.
- Click Use Windows 2000 Security, and then click Next.
- Select a database to connect to, click Next, and then click Finish.
- Select your new Office Database Connection (.ODC) file in the Select Data Source dialog box, and then click Open.
- Select one of the tables, and move it to the Link to Project box. Click Next.
- Click Finish.
Note that you receive the error message that is
mentioned in the "Symptoms" section of this article.
APPLIES TO
- Microsoft Office Access 2007
- Microsoft Office Access 2003
- Microsoft Access 2002 Standard Edition, when used with:
- the operating system: Microsoft Windows 2000
| kbtshoot kbexpertiseinter kbadp kbclientserver kberrmsg kbprb KB295255 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please