Reputation: 9
I have an SSIS package in which I am using script tasks. Sometimes after making changes to this package and deploying it as a single package, I find that the package runs without error but doesn't actually execute the script task. If I deploy the project as a whole - without making any changes to the package the script task perfectly.
In short, if I do a project deployment the script task work as expected but as a package deployment it doesn't work, there are occasions when deploying the project is not possible so this workaround isn't always available.
I am using Vs 2016 and my target deployment version is also SQL server 2016.
I am unable to identify the root cause for this kind of issue.
Upvotes: 0
Views: 797
Reputation: 1
You can try setting the logging option of the SQL Server Agent Job.
It can be also related to permissions. Executing the SSIS package will use your security context but running it from the agent impersonates the credentials defined in the proxy, and then runs the job step by using that security context.
Try also adding the event handlers to know better about the logs.
Upvotes: 0