Execute package from SQL client SSIS catalog menu Error

• sqlfriend

  SSC Guru

  Points: 52794

  More actions

  March 15, 2018 at 3:10 pm

  #336568

  I'm using SSIS catalog to test executing a package that get data from a remote SQL server B into another server A in the same domain . The SSIS package is located on server A.

  I run SSMS from my workstation, connect to Server A and go to menu Integration service catalogs- right click the  package and execute, then it failed with error:  login failed for user "NT AUTHORITY\ANONYMOUS logon .

  I did some research online and found this is a double hop issue and needs to setup Kerberos.
  Then we setup the SPN and also allowed the delegation of the server A to any service, also allowed delegation of the SQL service on Server A.

  But we still get the same error from executing the package from SSIS catalog menu.

  We don't have this problem if we execute the package from Data tools, SQL agent job. or from the Server A itself from SSIS catalog.

  How to fix this issue?

  Thanks,

• Phil Parkin

  SSC Guru

  Points: 247158

  More actions

  March 15, 2018 at 3:24 pm

  #1983474

  sqlfriends - Thursday, March 15, 2018 3:10 PM

  I'm using SSIS catalog to test executing a package that get data from a remote SQL server B into another server A in the same domain . The SSIS package is located on server A.

  I run SSMS from my workstation, connect to Server A and go to menu Integration service catalogs- right click the  package and execute, then it failed with error:  login failed for user "NT AUTHORITY\ANONYMOUS logon .

  I did some research online and found this is a double hop issue and needs to setup Kerberos.
  Then we setup the SPN and also allowed the delegation of the server A to any service, also allowed delegation of the SQL service on Server A.

  But we still get the same error from executing the package from SSIS catalog menu.

  We don't have this problem if we execute the package from Data tools, SQL agent job. or from the Server A itself from SSIS catalog.

  How to fix this issue?

  Thanks,

  If you find out, please post back. This issue is a real pain in the neck. In the past, I've given up and relied on the SQL Agent job.

  ---