I have a package that consists of three sequence containers with success connectors. Each holds a number of tasks.
For debugging and testing, I disabled every taskbut one in the first container. This is an SQL task that connects to an SQL server and truncates a table in preparation for the next task, which is a dataflow task to put new data into the table.
When I debug, the container and the task both go yellow and then red. The progress report says that there was a problem making a connection to the database.
After much testing to no avail, I just right-clicked on the task itself and did an "execute task." Now it works fine. I have exactly the same experience with another task within the same container, this one connecting to an Oracle database. If I debug and let the sequence container in on the action, both sql tasks fail to connect. If I just execute each task individually, each works as expected.
So instead of hitting F5 and watching about 18 tasks fire off in proper sequence, I executed each individually with success.
What would be the reason that the task cannot run when fired by the sequence container, but it does run fine when executed directly?
SSIS 2008 R2 Standard Edition ...
Thanks for any ideas regarding this!