DTS package stops when more than one task runs
-
Has anyone had a DTS package finish on a task (that completes successfully) that has tasks after it that should execute based on the "On Success" precedence constraint ?
The package seems to have some strange behaviour that I think is related to threading but I cannot pin it down as yet. The task that stops seems to be a task that executes when two tasks can run (there are parts of the package where 2 tasks are allowed to run at the same time).
TIA
Stephen
-
Is the other step enabled?
There are lots of things that can cause this.
Remove tasks that you don't think are involved ib the workflow and then add them one by one until you find what is causing the problem.
Cursors never.
DTS - only when needed and never to control.
Cursors never.
DTS - only when needed and never to control. -
What type of task is it? You can always stabilize tasks that aren't free threaded by editting the workflow properties and setting the "Execute on Main Thread' prop to true.
Trey Johnson
------------------
Practice Director
Business Intelligence
Encore Development
------------------
VP of Marketing
PASS
------------------
Founder
Trey Johnson | Chief Business Intelligence Architect | Cizer Software (www.cizer.com)
Who? - Cizer - http://www.cizer.com/about.htm - Blog - http://www.sqlserverbi.com/
What? - Products enhancing Microsoft Business Intelligence - http://www.cizer.com/products.htm
Wow! - Empower your Developers.... NEW Drop In Reporting - http://www.cizer.com/cnr-drop-in-reporting.htm
How? - BI Training - http://www.cizer.com/training.htm - Cizer Solutions - http://www.cizer.com/solutions.htm -
What type of tasks are you using? If you're using an ActiveXScript task, are you setting the task result correctly? Do you have any Workflow scripts that determine if the second task executes or not?
Hope this helps
Phill Carter
--------------------
Colt 45 - the original point and click interface
--------------------
Colt 45 - the original point and click interface
-
There are various task types involved - it is commonly an execute SQL task. The tasks that fail are enabled - there is not logic in the package that changes this. The only thing that should be influencing whether the step runs is the precedence constraint (which is "On Success") which is being satisified.
There are steps that are programmatically enabling disabled/enabled during the execution of the package. This code is working as I expect it to.
I have not used "execute on main thread' for the tasks that are failing. I would be kinda disappointed if this is required because it does mean that the package becomes single threaded.
Having said that, I would not be too surprised if this corrects some of the problems because it seems that tasks such as the dynamic configuration task are prone to fail without this. The key difference though is that the dynamic config task actually failed whereas the symptom I am seeing is the package completes successfully, all tasks that run complete successfully but a number of tasks that should run do not.
There are active x tasks. These are quite simple tasks that are responsible for setting global variables or modifying the enabling/disabling a few key steps.
There are not workflow scripts.
-
For the tasks that don't execute, do you have single or multiple precedence constraints? If you have multiple constraints, bear in mind that these work as an AND not an OR.
Hope this helps
Phill Carter
--------------------
Colt 45 - the original point and click interface
--------------------
Colt 45 - the original point and click interface -
All steps have at most one precedence constraint. Having said that, there are tasks that have two tasks as the next task to run.
I have changed the package so that the max tasks to execute is 2 and the problem has stopped happening.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply