Why does a script task not execute unless the whole project is deployed?

Question

I have an SSIS package which contains a C# script task. Sometimes after making changes to this package and deploying it in isolation, I find that the package runs without error but doesn't actually execute the script task. This is something I've seen reported elsewhere.

However, if I deploy the project as a whole - without making any further changes to the package - it runs correctly including all of the activities within the script task.

Does anyone know why this would occur and how it can be resolved? There are occasions when deploying the project is not possible (if multiple changes are occurring, for example) so this workaround isn't always available. Identifying the root cause would be very helpful.

SQL version - 2016 SP2 CU14

Answer 1

Hi @Peter Bishop ,

Please follow the following process after you finished modifying any SSIS Script Task:

1. Go to the Build menu, and select 2nd option from the top Build ST_<GUID> (Ctrl+B).
2. Observe that build is successful in the VS Output pane. Along the following lines:
   Build started: Project: ST_6ed65bbae4654154b980936109095fa4
   Build succeeded
3. Select File => Exit

This process will make sure that the Script Task was compiled successfully and it is ready to be executed, deployed, etc.

Answer 2

This is a known problem with package deployments which has existed for a long time. The solution is to deploy the entire project.

Answer 3

Hi @Peter Bishop ,

We should deploy the whole project if we use the project connection manager or project parameter in Script Task.

Best Regards,
Mona

----------

If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.