SSIS flatfile source false behavior on redirect row on error - by Christian Terhart

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 778823 Comments
Status Closed Workarounds
Type Bug Repros 4
Opened 2/8/2013 4:24:34 AM
Access Restriction Public


Hi there,

I have defined a flatfile connection in SSIS. (e.g. 4 columns, row delimiter <tab>, quote-ident ", row delimiter <lf>)
In the flatfile source I created an error redirect output for error and truncation.

If the flatfile has a row that does not fit the definied columns the package is failing.
If you run this in debug mode, the flatfile-source will start but not go any further when coming to error row.
The redirect of the row is not working but the tasks does not go further.
If you change the error behavior to "ignore failure" the "broken" row is ignored and the flow is working correctly.

Sign in to post a comment.
Posted by Microsoft on 9/8/2015 at 7:01 PM
Thanks for the problem report. We have been unable to reproduce the problem behavior you're reporting. By following the repro steps you provided(Create a flatfile that has one row that does not fit the defined connection above. (e.g. just 1 column, ending with <lf>) ), there is no error in this case since SSIS set other columns as empty instead of throw error. I also tried to create a file that has error rows and row delimiter is <lf>, the error rows are redirected to error output correctly in debug mode.
We hope that with more information we can get to the bottom of the issue. Can you please provide a sample source file to help us identify the problem?
Posted by Calico Eric on 8/16/2013 at 11:53 AM
I have a similar problem where my input is about 3.2 million rows out of which 200 rows are not making it through the flat file source. However, those erroneous rows are not going to the flat file destination set up for error output either.

I have set up explicit OnError handlers for all possibly relevant steps and they are not getting hit (each sends me an email if invoked).

In my case I have set the truncation action to fail and the error action to redirect row. That configuration is repeated for *all* input columns (as is the default).

I have confirmed that my file destination for the error output does not have any permission issues for writing to it.

This is looking more and more like an SSIS bug. We need to be able to inform users importing data which rows are in error and the current SSIS behavior is preventing that and thus this is significantly affecting our data import functionality.