Execute Package Task on a named instance (SQL Server 2008 R2)

• kyagi.jo

  SSCrazy

  Points: 2559

  More actions

  April 24, 2015 at 2:33 am

  #307335

  Hello,

  Has anyone had problems with using the execute package task when the packages are deployed on SQL Server, but they aren't deployed on the default instance?

  I have deployed my packages to the MSDB of a named instance, and I can create an OLE DB connection manager to the named instance MSDB and connect to the repository on the named instance, and view the packages I deployed in the execute package task editor. When I try to run any package in this repository through the execute package task, then the debug output just says the task is canceled, and it hangs in yellow status. I added logging, but there is no message I can see that tells me why it canceled. I can switch to an msdb on another server where the instance the packages are deployed to is the default one and can use the execute package task with no issues, so I suspect that this may be an issue with the fact it is a named instance, where it allows me to view the packages, but at runtime, it may be assuming the packages are in the default instance.

  If I try to execute the package on the instance from a job in the SQL Server agent instead of the execute package task, then it works with none of this cancelling issue, so I don't believe it is a problem with the package itself.

  I am using SSIS 2008.

  Any ideas appreciated!