Comments posted to this topic are about the item Resolution for SSIS Package Catastrophic Failure
Interesting, thanks for posting this: I'm sure that it will help others.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
Thank you so much for this. I had this issue developing over time. I could mitigate it by falling back on older versions.
I know I have a legacy server where a couple packages are in this state, I was just hoping I would never have to change nothing to these packages since they are legacy.
Your solution is a real life saver.
In my case I guess the problem was somewhat caused by using a third party monitoring and notification application and somehow sometimes, the code got lost in the continuum.
Very rarely but still when it happens, you end-up with a package you cannot trust anymore and it is always a package you really do not want to rewrite from scratch.
Glad that I was able to help developer community.
Viewing 5 posts - 1 through 4 (of 4 total)