SSIS: DataFlow never touched during execution

[SSIS 2013]

I have a dataflow inside a FOREACH that never gets touched during test execution.  I have all kinds of breakpoints set on it, I have a script task immediately before it for debugging purposes, that ALL IT DOES is to messagebox() the same element that the dataflow uses--and it (the script task with the messagebox) works just fine.

Execution marches right past this dataflow.  No errors thrown, nothing.  I've also seeded it with calls to messagebox()...nothing.

This is so weird that I'm not going to start off with the code of the dataflow itself, just because at this point, I think what it actually contains is immaterial.  I think the whole damn thing is being ignored, for some reason I cannot understand.

How else would you explain that its OnPreExecute() and OnPostExecute() breakpoints, plus, several others, are never touched?  Bear in mind that these are not custom breakpoints that are inline, in the code.  I'm talking about the general ones that SSIS allows you to set.

Weird.  What is happening?  Why is my dataflow so thoroughly ignored?


Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ValentinoVBI ConsultantCommented:
As far as I can tell from here it looks like it is disabled (the text appears lighter than on the other controls).  So right-click it and choose Enable, then try again...

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Mark WillsTopic AdvisorCommented:

1st step when everything else appears to be OK, but no breakpoints, no messages (et al) then it usually means it is not enabled. Unfortunately all too easy to happen and has caught out some highly capable people (with ensuing sheepish grins).
bamapieAuthor Commented:
HAHAHAHA!  And I totally remember doing that during some testing earlier!

Sheepish grin?  I want to stab myself.

Thanks to both of you.
ValentinoVBI ConsultantCommented:
You're welcome and don't worry, silly things happen to all of us now and then.  The simplest things get overlooked easily when the focus/attention is going too much in another direction, we're just humans after all... ;)
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.