Integrating Integrators – BizTalk, Windows Azure, Windows Workflow, and Beyond

Re: Problem in receive pipeline - Unexpected end of stream

BizTalk 2004

This group is for all content related to BizTalk Server 2004. This includes a forum, samples, videos, labs, whitepapers, and tools. Most of the content here also applies to other versions of BizTalk beyond 2004.

Problem in receive pipeline - Unexpected end of stream

  • rated by 0 users
  • This post has 2 Replies |
  • 0 Followers
  • Hi,

    I'm new in Biztalk and I try to process a flat file to create an IDOC in SAP.
    In my flat file structure , I've defined 3 child nodes in element type Record because I need to create 3 items segments in my IDOC in SAP.
    Each child nodes contains 4 data ( string ).

    In my mapping I've used a looping functoids to create a new segment for each Record.

    In my receive pipeline, I use a flat file dissasembler.

    But when I test, I have the following error:

    There was a failure executing the receive pipeline: \"Demande_de_chargement.RP_dpo_cics, Demande de chargement, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c77dc822841b7a10\" Source: \"Flat file disassembler\" Receive Port: \"RP-MVT-STOCK\" URI: \"D:\\Projet - Biztalk\\GOTA\\Demande de chargement\\File_in\\*.txt\" Reason: Unexpected end of stream while looking for:
    Positional data (length is 5)
    The current definition being parsed is Root. The stream offset where the error occured is 125. The line number where the error occured is 1.
    The column where the error occured is 125.

    Someone have already had this problem ?
    Thanks for your help
    Hugues
    Edit
  • It could be a number of items. Does your flat file validate against the schema? I’m guessing not.

    You might want to look at changing the parsing mode to Complexity (set on the <schema> node properties). Also make sure your default delimiter type (i.e. like Post Fixed, Per Fixed, or In Fixed) is set correctly.

    Typically I have to do a trial and error approach to fix these types of problems.

    Stephen W. Thomas
    http://www.BizTalkGurus.com

  • Set the parser complexity of your schema to 'Complexity'.

    Edit
Page 1 of 1 (3 items)