Delimiter issue in SSIS package

I run an SSIS package to create a .txt file on to an FTP server and the delimiter I use is a pipe delimeter:

I have to import this file into a third party too and I get this error message: invalid field count

196      196      Invalid field count: expected 17 fields but found 10      [203822][1][903510001][Accessories][331000][0][Uncertified][5000][1/8/8/0/9/18809622][  Edition Red, White & Blue Crystal Minaudiere]
197      197      Invalid field count: expected 17 fields but found 1      [<BR> Condition: 1]
198      198      Invalid field count: expected 17 fields but found 8      [<][][1][][0][0][37][collection]

I can't use any other delimiter because of the nature of the file. Can you provide any suggestions please
Who is Participating?
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.

lcohanDatabase AnalystCommented:
There must be some chars in the output in my opinion that "breaks" the record by fake EOL pointer so when you say that  
I have to import this file into a third party
In my opinion you must find out from the "third party" if:
- are they accepting UNICODE or not and if yes on the "Flat File Destination" you must check the "Unicode" bos and provide the appropriate Code Page the third party needs.
- what is the "Text Qualifier" accepted by third party? Some they have double quotes so set that on the "Flat File Destination" dialog under the "Format"
- what is the "Row delimiter" that third party accepts and set it on the "Row delimiter" dialog if it is different that default CR/LF
- obviously set the "Column delimiter to "Vertical Bar" or pipe as you need it.
sqlcuriousAuthor Commented:
I figured there were some carriage returns that was causing the issue, so removed them and it worked, thanks for your inputs lcohan

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
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

From novice to tech pro — start learning today.