Additionally, you may receive some Application event logs that resemble the following:
Log Name: Application Source: BizTalk Server 2006 EDI Event ID: 8114 Description: Error encountered during parsing. The X12 transaction set with id '<id>' contained in functional group with id '<id>', in interchange with id '<id>', with sender id '<id> ', receiver id '<id> ' is being suspended with following errors: Error: 1 (Miscellaneous error) 4: Invalid Segment Terminator Error: 2 (Segment level error) SegmentID: Position in TS: <number> 7: Segment Not In Proper Sequence Error: 3 (Segment level error) SegmentID: Position in TS: <number> 2: Unexpected segment Error: <n>. . .
Log Name: Application Source: BizTalk Server 2006 Event ID: 5753 Task Category: BizTalk Server 2006 Level: Error Keywords: Classic User: N/A Computer: <server> Description: A message received by adapter "FILE" on receive location "<Location_Name> " with URI "<File_Path>" is suspended. Error details: An output message of the component "Unknown " in receive pipeline "Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" is suspended due to the following error: Unknown . The sequence number of the suspended message is 1. MessageId: {D374E531-4ED6-4D25-BB5D-3A48526DFC3A} InstanceID: {9FFDB69E-FB2F-4332-A1DC-116A97FD9120}
Log Name: Application Source: BizTalk Server 2006 EDI Event ID: 8116 Description: Error: 1 (Field level error) SegmentID: AK3 Position in TS: <number> Data Element ID: AK301 Position in Segment: <number> Data Value: 6: Leading or trailing space found ...