Execute package in SSISDB catalog with UNC path

• sqlfriend

  SSC Guru

  Points: 52794

  More actions

  August 3, 2016 at 4:12 pm

  #315944

  We recently start using the SSIS project deploy mode which utilize SSISCatalog database SSISDB.

  I found there is an issue if we run a package in SSISDB by right click the package in SSISDB Catalog,

  if the package has a connection that uses a UNC path or shared directory on network, it will fail with access denied. I am running the package using my account and I have all permissions to the path.

  Later I understand this is a double hop issue, not very sure what caused that, but it seems the solution is to create SPN and allow kerobos authentication, then it should work when executing in SSISDB.

  My question is when setting up SPN, what SPNs needed to be added in order for above to work.

  I know it is definitely need creating for SQL service account, but for this case it is running under my account, so how SPN can be related with my account?

  I am not the person who is going to create SPN, it will be passed to our network manager.

  But I am trying to understand this.

  An earlier posted question related with this is here:

  http://www.sqlservercentral.com/Forums/Topic1794324-3411-1.aspx

• Phil Parkin

  SSC Guru

  Points: 247180

  More actions

  August 3, 2016 at 4:46 pm

  #1893650

  Does running the package as a SQL Agent job work?

  ---

• sqlfriend

  SSC Guru

  Points: 52794

  More actions

  August 3, 2016 at 4:54 pm

  #1893652

  The SQL agent job works, but not in SSISDB Catalog execution.

  So my question for this post is how to setup SPN related with this issue.

  I not only need SQL agent job to work, also want to make the execute package in SSISDB catalog to work too.

  Thanks!