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

Error in Receive port using EDI

BizTalk 2006 R2

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

Error in Receive port using EDI

Answered (Verified) This question is answered

Hi gurus,

    Here's a good problem for anyone out there to solve. I have configured a receive port with a location that uses default EDI receive pipeline to process a 271 message (X12). I drop the file in the folder and it gets picked up, I check the event log and it shows two error entries:

First error:

Error encountered during parsing. The X12 transaction set with id '' contained in functional group with id '1', in interchange with id '000195946', with sender id 'PC-WEB         ', receiver id '1803484        ' is being suspended with following errors:

Error: 1 (Miscellaneous error)
 6: Missing or invalid or duplicate Transaction set identifier 'http://schemas.microsoft.com/BizTalk/EDI/X12/2006/Revs#X12_00401_271'

 

Second error:

A message received by adapter "FILE" on receive location "Revs_Rcv271File.FILE" with URI "C:\Depository\Revs_Check\In\inquiry.rcv" 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:  {1763948C-F1C8-4765-9730-DEBF351B30DC}
 InstanceID: {67B33E55-7A5F-4FC1-B161-07AA779E73F3}

Now, in the BizTalk Administration Console, I check the message details associated with the suspended service instance and see the following message body:

<UnrecognizedSchema><UnrecognizedSegment>ST*271*000195946</UnrecognizedSegment><UnrecognizedSegment>BHT*0022*11*REPW*20081103*105819</UnrecognizedSegment><UnrecognizedSegment>HL*1**20*1</UnrecognizedSegment><UnrecognizedSegment>NM1*PR*2*MASSACHUSETTS MEDICAID*****PI*MASS XIX DMA</UnrecognizedSegment><UnrecognizedSegment>PER*IC*HELP DESK*TE*8004627738</UnrecognizedSegment><UnrecognizedSegment>HL*2*1*21*1</UnrecognizedSegment><UnrecognizedSegment>NM1*1P*2******SV*1803484</UnrecognizedSegment><UnrecognizedSegment>REF*JD*EZELLIS</UnrecognizedSegment><UnrecognizedSegment>REF*EL*PCX020120022P</UnrecognizedSegment><UnrecognizedSegment>HL*3*2*22*0</UnrecognizedSegment><UnrecognizedSegment>NM1*IL*1*FRANKLIN*TANYA****MI*0016819549</UnrecognizedSegment><UnrecognizedSegment>REF*GH*662506109902</UnrecognizedSegment><UnrecognizedSegment>REF*SY*001681954</UnrecognizedSegment><UnrecognizedSegment>N3*15 KANE STREET</UnrecognizedSegment><UnrecognizedSegment>N4*FAIRHAVEN*MA*02719</UnrecognizedSegment><UnrecognizedSegment>DMG*D8*19821006*F</UnrecognizedSegment><UnrecognizedSegment>DTP*307*D8*20081016</UnrecognizedSegment><UnrecognizedSegment>EB*1**30*MC*STANDARD</UnrecognizedSegment><UnrecognizedSegment>EB*U</UnrecognizedSegment><UnrecognizedSegment>LS*2120</UnrecognizedSegment><UnrecognizedSegment>NM1*FA*2*LWO/MEC*****FA*570</UnrecognizedSegment><UnrecognizedSegment>LE*2120</UnrecognizedSegment><UnrecognizedSegment>EB*L</UnrecognizedSegment><UnrecognizedSegment>LS*2120</UnrecognizedSegment><UnrecognizedSegment>NM1*P3*1*DARTMOUTH PRIMARY MEDICINE*DARTMOUTH PRIMARY MEDICIN</UnrecognizedSegment><UnrecognizedSegment>N3*49 STATE RD. WATUPPA BL*SUITE 101-A</UnrecognizedSegment><UnrecognizedSegment>N4*DARTMOUTH*MA*02747</UnrecognizedSegment><UnrecognizedSegment>PER*IC**TE*5089945300</UnrecognizedSegment><UnrecognizedSegment>LE*2120</UnrecognizedSegment><UnrecognizedSegment>EB*F</UnrecognizedSegment><UnrecognizedSegment>MSG*PCC MEMBER. CALL DARTMOUTH PRIMARY MEDICIN-DARTMOUTH PRIMARY MEDICI 5089945300 FOR APPROVAL. FOR EXCEPTIONS SEE 130 CMR 450.118(J)</UnrecognizedSegment><UnrecognizedSegment>EB*F</UnrecognizedSegment><UnrecognizedSegment>MSG*NEW MMIS MEMBER ID - 100030507402</UnrecognizedSegment><UnrecognizedSegment>EB*F</UnrecognizedSegment><UnrecognizedSegment>MSG*FOR MENTAL HEALTH OR SUBSTANCE ABUSE SERVICE AUTHORIZATION CALL THE PARTNERSHIP AT 1-800-495-0086.</UnrecognizedSegment><UnrecognizedSegment>SE*36*000195946</UnrecognizedSegment></UnrecognizedSchema>

Here are a few notes:

1) I have deployed a separate X12_00401_271 schema to the application instance, with different namespace and root node name, so there is not conflict in schemas with the default  271 schema.

2) I have configured the EDI Properties settings for a Global Party so that the Party as Interchange Sender property (under the X12 Properties area) is modified with the X12 Interchange Processing Properties having the Check for Duplicates checkboxes unchecked for all levels (Interchange, Group, Transaction).

3) I have tried using a custom Receive pipeline for the Receive location, but I still get the same errors.

4) The 271 message that I use to drop into the folder has the following contents:

ISA*03*          *01*          *ZZ*PC-WEB         *ZZ*1803484        *081103*1058*U*00401*000195946*0*P*:~GS*HB*MASS XIX DMA*EZELLIS*20081103*1058*1*X*004010X092A1~ST*271*000195946~BHT*0022*11*REPW*20081103*105819~HL*1**20*1~NM1*PR*2*MASSACHUSETTS MEDICAID*****PI*MASS XIX DMA~PER*IC*HELP DESK*TE*8004627738~HL*2*1*21*1~NM1*1P*2******SV*1803484~REF*JD*EZELLIS~REF*EL*PCX020120022P~HL*3*2*22*0~NM1*IL*1*FRANKLIN*TANYA****MI*0016819549~REF*GH*662506109902~REF*SY*001681954~N3*15 KANE STREET~N4*FAIRHAVEN*MA*02719~DMG*D8*19821006*F~DTP*307*D8*20081016~EB*1**30*MC*STANDARD~EB*U~LS*2120~NM1*FA*2*LWO/MEC*****FA*570~LE*2120~EB*L~LS*2120~NM1*P3*1*DARTMOUTH PRIMARY MEDICINE*DARTMOUTH PRIMARY MEDICIN~N3*49 STATE RD. WATUPPA BL*SUITE 101-A~N4*DARTMOUTH*MA*02747~PER*IC**TE*5089945300~LE*2120~EB*F~MSG*PCC MEMBER. CALL DARTMOUTH PRIMARY MEDICIN-DARTMOUTH PRIMARY MEDICI 5089945300 FOR APPROVAL. FOR EXCEPTIONS SEE 130 CMR 450.118(J)~EB*F~MSG*NEW MMIS MEMBER ID - 100030507402~EB*F~MSG*FOR MENTAL HEALTH OR SUBSTANCE ABUSE SERVICE AUTHORIZATION CALL THE PARTNERSHIP AT 1-800-495-0086.~SE*36*000195946~GE*1*1~IEA*1*000195946~

If anyone can help me resolve this issue (and I've been at it for a few days now), I will make sure you get extra brownie points and will advertise your troubleshooting skills up and down this forum and site! :-)

Thanks,

Daniel.

 

"Google skills are more important than your coding skills."

Verified Answer
  • xman71

    Hi gurus,

        Here's a good problem for anyone out there to solve. I have configured a receive port with a location that uses default EDI receive pipeline to process a 271 message (X12). I drop the file in the folder and it gets picked up, I check the event log and it shows two error entries:

    First error:

    Error encountered during parsing. The X12 transaction set with id '' contained in functional group with id '1', in interchange with id '000195946', with sender id 'PC-WEB         ', receiver id '1803484        ' is being suspended with following errors:

    Error: 1 (Miscellaneous error)
     6: Missing or invalid or duplicate Transaction set identifier 'http://schemas.microsoft.com/BizTalk/EDI/X12/2006/Revs#X12_00401_271'

     

    Second error:

    A message received by adapter "FILE" on receive location "Revs_Rcv271File.FILE" with URI "C:\Depository\Revs_Check\In\inquiry.rcv" 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:  {1763948C-F1C8-4765-9730-DEBF351B30DC}
     InstanceID: {67B33E55-7A5F-4FC1-B161-07AA779E73F3}

    Now, in the BizTalk Administration Console, I check the message details associated with the suspended service instance and see the following message body:

    <UnrecognizedSchema><UnrecognizedSegment>ST*271*000195946</UnrecognizedSegment><UnrecognizedSegment>BHT*0022*11*REPW*20081103*105819</UnrecognizedSegment><UnrecognizedSegment>HL*1**20*1</UnrecognizedSegment><UnrecognizedSegment>NM1*PR*2*MASSACHUSETTS MEDICAID*****PI*MASS XIX DMA</UnrecognizedSegment><UnrecognizedSegment>PER*IC*HELP DESK*TE*8004627738</UnrecognizedSegment><UnrecognizedSegment>HL*2*1*21*1</UnrecognizedSegment><UnrecognizedSegment>NM1*1P*2******SV*1803484</UnrecognizedSegment><UnrecognizedSegment>REF*JD*EZELLIS</UnrecognizedSegment><UnrecognizedSegment>REF*EL*PCX020120022P</UnrecognizedSegment><UnrecognizedSegment>HL*3*2*22*0</UnrecognizedSegment><UnrecognizedSegment>NM1*IL*1*FRANKLIN*TANYA****MI*0016819549</UnrecognizedSegment><UnrecognizedSegment>REF*GH*662506109902</UnrecognizedSegment><UnrecognizedSegment>REF*SY*001681954</UnrecognizedSegment><UnrecognizedSegment>N3*15 KANE STREET</UnrecognizedSegment><UnrecognizedSegment>N4*FAIRHAVEN*MA*02719</UnrecognizedSegment><UnrecognizedSegment>DMG*D8*19821006*F</UnrecognizedSegment><UnrecognizedSegment>DTP*307*D8*20081016</UnrecognizedSegment><UnrecognizedSegment>EB*1**30*MC*STANDARD</UnrecognizedSegment><UnrecognizedSegment>EB*U</UnrecognizedSegment><UnrecognizedSegment>LS*2120</UnrecognizedSegment><UnrecognizedSegment>NM1*FA*2*LWO/MEC*****FA*570</UnrecognizedSegment><UnrecognizedSegment>LE*2120</UnrecognizedSegment><UnrecognizedSegment>EB*L</UnrecognizedSegment><UnrecognizedSegment>LS*2120</UnrecognizedSegment><UnrecognizedSegment>NM1*P3*1*DARTMOUTH PRIMARY MEDICINE*DARTMOUTH PRIMARY MEDICIN</UnrecognizedSegment><UnrecognizedSegment>N3*49 STATE RD. WATUPPA BL*SUITE 101-A</UnrecognizedSegment><UnrecognizedSegment>N4*DARTMOUTH*MA*02747</UnrecognizedSegment><UnrecognizedSegment>PER*IC**TE*5089945300</UnrecognizedSegment><UnrecognizedSegment>LE*2120</UnrecognizedSegment><UnrecognizedSegment>EB*F</UnrecognizedSegment><UnrecognizedSegment>MSG*PCC MEMBER. CALL DARTMOUTH PRIMARY MEDICIN-DARTMOUTH PRIMARY MEDICI 5089945300 FOR APPROVAL. FOR EXCEPTIONS SEE 130 CMR 450.118(J)</UnrecognizedSegment><UnrecognizedSegment>EB*F</UnrecognizedSegment><UnrecognizedSegment>MSG*NEW MMIS MEMBER ID - 100030507402</UnrecognizedSegment><UnrecognizedSegment>EB*F</UnrecognizedSegment><UnrecognizedSegment>MSG*FOR MENTAL HEALTH OR SUBSTANCE ABUSE SERVICE AUTHORIZATION CALL THE PARTNERSHIP AT 1-800-495-0086.</UnrecognizedSegment><UnrecognizedSegment>SE*36*000195946</UnrecognizedSegment></UnrecognizedSchema>

    Here are a few notes:

    1) I have deployed a separate X12_00401_271 schema to the application instance, with different namespace and root node name, so there is not conflict in schemas with the default  271 schema.

    2) I have configured the EDI Properties settings for a Global Party so that the Party as Interchange Sender property (under the X12 Properties area) is modified with the X12 Interchange Processing Properties having the Check for Duplicates checkboxes unchecked for all levels (Interchange, Group, Transaction).

    3) I have tried using a custom Receive pipeline for the Receive location, but I still get the same errors.

    4) The 271 message that I use to drop into the folder has the following contents:

    ISA*03*          *01*          *ZZ*PC-WEB         *ZZ*1803484        *081103*1058*U*00401*000195946*0*P*:~GS*HB*MASS XIX DMA*EZELLIS*20081103*1058*1*X*004010X092A1~ST*271*000195946~BHT*0022*11*REPW*20081103*105819~HL*1**20*1~NM1*PR*2*MASSACHUSETTS MEDICAID*****PI*MASS XIX DMA~PER*IC*HELP DESK*TE*8004627738~HL*2*1*21*1~NM1*1P*2******SV*1803484~REF*JD*EZELLIS~REF*EL*PCX020120022P~HL*3*2*22*0~NM1*IL*1*FRANKLIN*TANYA****MI*0016819549~REF*GH*662506109902~REF*SY*001681954~N3*15 KANE STREET~N4*FAIRHAVEN*MA*02719~DMG*D8*19821006*F~DTP*307*D8*20081016~EB*1**30*MC*STANDARD~EB*U~LS*2120~NM1*FA*2*LWO/MEC*****FA*570~LE*2120~EB*L~LS*2120~NM1*P3*1*DARTMOUTH PRIMARY MEDICINE*DARTMOUTH PRIMARY MEDICIN~N3*49 STATE RD. WATUPPA BL*SUITE 101-A~N4*DARTMOUTH*MA*02747~PER*IC**TE*5089945300~LE*2120~EB*F~MSG*PCC MEMBER. CALL DARTMOUTH PRIMARY MEDICIN-DARTMOUTH PRIMARY MEDICI 5089945300 FOR APPROVAL. FOR EXCEPTIONS SEE 130 CMR 450.118(J)~EB*F~MSG*NEW MMIS MEMBER ID - 100030507402~EB*F~MSG*FOR MENTAL HEALTH OR SUBSTANCE ABUSE SERVICE AUTHORIZATION CALL THE PARTNERSHIP AT 1-800-495-0086.~SE*36*000195946~GE*1*1~IEA*1*000195946~

    If anyone can help me resolve this issue (and I've been at it for a few days now), I will make sure you get extra brownie points and will advertise your troubleshooting skills up and down this forum and site! :-)

    Thanks,

    Daniel.

     

     

    Here's an update on this issue: I ended up modifying the X12_00401_271 schema to change the target namespace property and redeploying it from my VS project, and it worked like a charm this time. I made sure that the new target namespace is selected in the Interchange Sender property area of my global party.

    Thanks for viewing this post, and I hope my answer will help anyone out there dealing with this issue.

     

    "Google skills are more important than your coding skills."

    • Top 10 Contributor
All Replies
  • I'm having the same issue. I tried the way what you said above but still no success. Do you know any other reason?

    Thanks,
    Raja Kumaravel

     

    Edit
  • Hi Raja,

     

       Are you getting the same errors that I was getting? Did you deploy the schema to a different Application (i.e. BizTalk Application 1) instead of EDI Application?

       Modifying the target namespace on that 271 schema and configuring the Interchange Sender property of a global party should have done the trick, unless there is something else going on in your environment...

     

       Daniel.

     

    "Google skills are more important than your coding skills."

    • Top 10 Contributor
  • I have the similar error for 270 tran. I have 2 versions (4010 & 5010) needs to be working.
    I set the schema namespace different for 4010 and 5010 versions and deployed the application. When I receive the EDI file from EDIRecive pipeline, the messages get suspended and the event log says -
    Finding the document specification by message type "http://schemas.microsoft.com/BizTalk/EDI/X12/2006#X12_00401_270" failed. Verify the schema deployed properly.
    Similar is the case for 5010.
    And interestingly the message type of these suspended message have the Global Party Default Namespace in it - http://schemas.microsoft.com/BizTalk/EDI/X12/2006
    The problem is that it just ignores the namespace I defined for the schema. I don't have any idea how to solve this. But my workaround is, I have set the schema namespace same as the Global Party Default Namespace in my BT solution and deployed the code. I am really waiting to see anyone is able to figure out what is wrong.

    Ritesh

    Edit
  • Thank you!  This worked for me :)

    Edit
Page 1 of 1 (6 items)