locked
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON' ... Invalid connection string attribute RRS feed

  • Question

  • Hi,

    We are running the SSIS package from another server with Window Authentication and hit the below error. But we have no issue running this SSIS package on the same DB server. 

    SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 11.0"  Hresult: 0x80040E4D  Description: "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.". An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 11.0"  Hresult: 0x80040E4D  Description: "Invalid connection string attribute". 

    Below are some steps we have done:

    1. We configure to use Kerberos authentication with the below link

    http://blogs.technet.com/b/askds/archive/2008/06/13/understanding-kerberos-double-hop.aspx

    2. We use linked server in the SSIS package and ensure it is configured properly

    We query this sys.dm_exec_connections, auth_scheme column, but we are still seeing it is still using NTLM.

    Is there any steps to configure that it is using Kerberos ?

    Warmest Regards

    Tau Wan


    Tuesday, February 7, 2017 1:52 PM

All replies

  • It looks like this package is running under the SQL Server Agent Service account on the remote machine and this is running under the local system (NT Authority account). If you schedule it on the remote machine does it work successfully? If not you will need to use a job proxy.
    • Proposed as answer by Albert_ Zhang Wednesday, February 8, 2017 2:30 AM
    Tuesday, February 7, 2017 2:03 PM
  • Hi Tau,

    It seems that something propagates the account rights that runs the package to a connection in question.

    Typically this would be the SQL Server Agent that by default runs under the 'NT AUTHORITY\ANONYMOUS LOGON' account

    The remedy is thus to run it under a proxy to which you gave the proper login rights, or revise how the connection is designed in terms of authentication (e.g. not using the Windows Auth.).

    Arthur

    MyBlog


    Twitter

    • Proposed as answer by Albert_ Zhang Wednesday, February 8, 2017 2:30 AM
    Tuesday, February 7, 2017 2:19 PM
  • We are running this SSIS package from file (.ispac) in another server and using a Windows service account.
    Tuesday, February 7, 2017 2:25 PM
  • .ispack is a file archive to deploy a package or project only


    Arthur

    MyBlog


    Twitter

    Tuesday, February 7, 2017 3:02 PM