A: 

Ok, we've got this one figured out. What happened is the final column in each row expects a CR/LF ColumnDelimiter.

So when the first row is processed and comes up short, SSIS doesn't acknowledge the CR/LF simply because it comes too soon. It instead continues on and processes the second row as part of the first. In this case the second row is all that's left and we get the truncation message referred to above, because a CR/LF is never encountered at character 80.

In the case of the other SSIS package that does fail, a number of rows are close enough to the expected line width that when the package tries stuffing them into a single field a truncation error on that field is triggered.

larryq
A: 

I have the same issue with my csv file. It skips some rows between and process the file without any errors. Could you please let me know what you did to fix this. Thanks a ton!!

Figured it out. Rename the csv file to xls!!

kala1234