Hi All,
I'm trying to figure out a scenario that was encountered with BizTalk 2004 SP2. The good thing is that I can recreate the exact scenario in test. Here's the details:
PROBLEM: Large file (22MB) received in a flatfile format that contains multiple docs. File is debatched into separate individual documents prior to processing via a custom pipeline. If there is a "special character" in a field within the file the debatching is stopped at that point and the rest is apparently discarded. No notification of the error is found. (HAT, Event Msg, MOM)
I found that I could recreate the error by setting up the following in a test environment.
RP -> CustomPipeline ->SP
Large file could contain thousands of docs. Depending on which doc contains the special character, debatching of file will occur at any point within. Remaining files do not get created.
Create small file containing 5 docs, 3rd one in containing special character, doc 1,2,4,5 appear in SP directory.
I can see that some of the scenario is related to how BizTalk processes large messages.
Maybe there is something that is not being monitored that would indicate this failure?
Any guidance is greatly appreciated.
Hi ChrisG,
I have a couple of suggestions for you to parse out this "special character" from your master file before you pass it through your custom pipeline:
1) Create a C# Helper class that you call from your orchestration (before your custom pipeline) passing in your message stream to do the parsing.
2) Or use XPath to replace any occurence of that special character in an Expression shape before hitting your custom pipeline.
I hope you find this information useful.
Daniel.
"Google skills are more important than your coding skills."