I built a custom SSIS Pipeline component in VS2010. It works perfectly in BIDS locally and on the server. I can't run it using DTExec on either. I set up VS to debug\start external program (32-bit version in x86 dir) and the only methods that it will break on are AcquireConnection, Validate and ReleaseConnections. I have put trace and FireInformation statements in the other methods and never see output from them. At this point, I have commented out all of my code and am basically running a minimum class with just the default method override definitions for AcquireConnections, ReleaseConnections, PrepareForExecute, PreExecute, PrimeOutput, ProcessInput and PostExecute. I have Validate returning VS_ISVALID. This component is connected to a olebd Destination error output (with redirect rows on error). The package executes and when the destination component redirects error rows, because I created a pk insert collision, the custom component blows up with a processInput failure. When I run in debug mode as configure above, I can verify that the connection is valid (also evidenced by the fact that the dataflow retrieved 10k rows). Every single method contains a try/catch block, so even if it ran and did nothing, I would understand, but throws an exception almost as if I had the component set to fail on error. Suggestions, starting points? Thanks, Patrick
↧