I’ve recently faced an issue when setting up BCS connection from SQL Server with error message Login failed for user ‘NT AUTHORITY\ANONYMOUS LOGON’. Quick googling determine that this is a Double Hop issue when the SQL Server box is not the same server as the BCS Service Application running.
My Solution is to create new key in Secure Store Service Application (ensure user has access to the SQL Database) and update BCS connection to use the key ID along with Impersonate Windows Identity.
Reference
- http://www.spdoctor.net/Pages/article.aspx?name=searching-external-data-using-bcs
- http://blogs.technet.com/b/harmeetw/archive/2011/08/28/getting-login-failed-for-user-nt-authority-anonymous-logon-when-browsing-external-list-on-a-claims-kerberos-web-application.aspx
- http://blogs.msdn.com/b/sql_protocols/archive/2006/08/10/694657.aspx
No comments:
Post a Comment