October 7, 2017 at 8:12 am
Hello,
Package has several tasks connected to each other...
I am introducing a failure precedence so I set the task1 to fail so on failure task2 gets called.
When task1 fails then task2 (execute sql task - select 1) fails also.
do you know why task2 fails? the error seems to be referring to connection whereas all tasks have the same connection and everything is fine until I introduce the failure task.
Thank you
October 7, 2017 at 8:25 am
arkiboys - Saturday, October 7, 2017 8:12 AMHello,
Package has several tasks connected to each other...
I am introducing a failure precedence so I set the task1 to fail so on failure task2 gets called.
When task1 fails then task2 (execute sql task - select 1) fails also.
do you know why task2 fails? the error seems to be referring to connection whereas all tasks have the same connection and everything is fine until I introduce the failure task.Thank you
That is not the behaviour I see:
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
October 7, 2017 at 8:32 am
Phil Parkin - Saturday, October 7, 2017 8:25 AMarkiboys - Saturday, October 7, 2017 8:12 AMHello,
Package has several tasks connected to each other...
I am introducing a failure precedence so I set the task1 to fail so on failure task2 gets called.
When task1 fails then task2 (execute sql task - select 1) fails also.
do you know why task2 fails? the error seems to be referring to connection whereas all tasks have the same connection and everything is fine until I introduce the failure task.Thank you
That is not the behaviour I see:
Hello, in my case, according to your example, sql 3 fails also. I can not figure out why.
October 9, 2017 at 7:30 am
arkiboys - Saturday, October 7, 2017 8:32 AMPhil Parkin - Saturday, October 7, 2017 8:25 AMarkiboys - Saturday, October 7, 2017 8:12 AMHello,
Package has several tasks connected to each other...
I am introducing a failure precedence so I set the task1 to fail so on failure task2 gets called.
When task1 fails then task2 (execute sql task - select 1) fails also.
do you know why task2 fails? the error seems to be referring to connection whereas all tasks have the same connection and everything is fine until I introduce the failure task.Thank you
That is not the behaviour I see:
Hello, in my case, according to your example, sql 3 fails also. I can not figure out why.
Without any details on what task 1 and task3 actually do, there's no conceivable way we're going to be able to do more than make ridiculously wild guesses. Exactly what do these two tasks do, and don't spare the details.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply