none
Fallback Settings Not working for Non-Agreement Senders RRS feed

  • Question

  • I am trying to test the fallback settings for X12 in Biztalk 2010.  I am processing an 837P and have one agreement in place that is processing files correctly when file is from the 'from' party of the agreement.  I am trying to use fallback to process files that are from a sender that is not part of the agreement.  I have enabled fallback and configured correctly as far as I can see.  When I send this type of file thru, I get these warning/errors in the event viewer - any thoughts?


    Error encountered during parsing. The X12 transaction set with id '' contained in functional group with id '125482', in interchange with id '000125482', with sender id '      382674344', receiver id '38-6004862     ' is being suspended with following errors:
    Error: 1 (Miscellaneous error)
     6: Finding the document specification by message type "http://schemas.microsoft.com/BizTalk/EDI/X12/2006#X12_00401_837" failed. Verify the schema deployed properly.
     
     
     
     
     A message received by adapter "FILE" on receive location "837_Receive_Location" with URI "c:\837\*.txt" 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:
         Error encountered during parsing. The X12 transaction set with id '' contained in functional group with id '125482', in interchange with id '000125482', with sender id '      382674344', receiver id '38-6004862     ' is being suspended with following errors:
    Error: 1 (Miscellaneous error)
     6: Finding the document specification by message type "http://schemas.microsoft.com/BizTalk/EDI/X12/2006#X12_00401_837" failed. Verify the schema deployed properly.

    .
     The sequence number of the suspended message is 1. 
     MessageId:  {D2CC89CA-5080-48E6-A9BF-7ABF6F37E9F2}
     InstanceID: {E2416749-D653-461B-9B7D-54AA47F75D00}
     
     
     
     Agreement Resolution for x12 Protocol based on the context properties DestinationPartySenderQualifier with value "ZZ", DestinationPartySenderIdentifier with value "38-6004862", DestinationPartyReceiverQualifier with value "ZZ" and DestinationPartyReceiverIdentifier with value "382674344" has failed.
     
     
     
     There was a failure executing the send pipeline: "Microsoft.BizTalk.Edi.DefaultPipelines.EdiSend, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "EDI Assembler" Send Port: "837 Send 997" URI: "C:\837\ack\997_%SourceFileName%_%MessageID%.txt" Reason: Agreement Resolution based on the context properties for x12 Protocol has failed.
     
     
     
     Agreement Resolution for x12 Protocol based on the context properties DestinationPartySenderQualifier with value "ZZ", DestinationPartySenderIdentifier with value "38-6004862", DestinationPartyReceiverQualifier with value "ZZ" and DestinationPartyReceiverIdentifier with value "382674344" has failed.
     
     
     
     There was a failure executing the send pipeline: "Microsoft.BizTalk.Edi.DefaultPipelines.EdiSend, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "EDI Assembler" Send Port: "837 Send TA1" URI: "c:\837\ack\TA1_%SourceFileName%_%MessageID%.txt" Reason: Agreement Resolution based on the context properties for x12 Protocol has failed.
     
     
     
     A message sent to adapter "FILE" on send port "837 Send 997" with URI "C:\837\ack\997_%SourceFileName%_%MessageID%.txt" is suspended.
     Error details: There was a failure executing the send pipeline: "Microsoft.BizTalk.Edi.DefaultPipelines.EdiSend, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "EDI Assembler" Send Port: "837 Send 997" URI: "C:\837\ack\997_%SourceFileName%_%MessageID%.txt" Reason: Agreement Resolution based on the context properties for x12 Protocol has failed. 
     MessageId:  {D053BF43-B315-48C9-9024-842FE53B9906}
     InstanceID: {0732CFD5-A997-4704-9D29-B273E104486A}
     
     
     
     A message sent to adapter "FILE" on send port "837 Send TA1" with URI "c:\837\ack\TA1_%SourceFileName%_%MessageID%.txt" is suspended.
     Error details: There was a failure executing the send pipeline: "Microsoft.BizTalk.Edi.DefaultPipelines.EdiSend, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "EDI Assembler" Send Port: "837 Send TA1" URI: "c:\837\ack\TA1_%SourceFileName%_%MessageID%.txt" Reason: Agreement Resolution based on the context properties for x12 Protocol has failed. 
     MessageId:  {A5BD0F9D-8AEC-4C33-A194-59EF0C619F87}
     InstanceID: {877126CD-1630-4FC9-9D30-F2EAA4AB09E7}


    Mike Dugan
    Thursday, March 31, 2011 6:28 PM

All replies

  • Please try changing the party setting

    in ISA Segement Defination at ISA5-6 and ISA 7-8 to sender id '38-6004862', receiver id   '      382674344'  

    If any furthur Question to answered about party setting .Please reply to this.............

     

    Thanks,

    Rajesh

    Friday, April 1, 2011 8:50 AM
  • This would make this specific file process, but what about other ones with different ISA6 values?  Again, my situation is I will get files from many different sources with different ISA 6 values.  I am trying to see if fallback settings will let me process files with any value in the ISA 6 and ISA8 fields...

     


    Mike Dugan
    Friday, April 1, 2011 12:54 PM
  • Hi Mike,

    You should always be knowing your partners and their SCAC and DUNS id. So you need to configure those many agreements.

    In case if you are fallback settings you need to enable this explicitly. Have you done that.

    In the Fallback Settings General Pages tab, on the General page, do the following:

    1. Click Enable Fallback Settings to enable BizTalk Server to use the fallback agreement settings if no agreement is resolved for incoming or outgoing messages.

      Bb226355.Important(en-us,BTS.70).gifImportant
      If this option is not checked, BizTalk Server will not use the properties set in the fallback agreement.


    Best Regards, Vishnu
    Wednesday, April 6, 2011 5:09 AM
  • Over the last several years we allowed our partners to fill in different values in the ISA6/8 values.  Our old hipaa/edi system did not deal with agreements, and we were able to identify sender by file name.  We are now moving to biztalk and I know that I can set up agreements and require each partner to use correct values.  Because they all send the same files and are subject to the same schemas (837P and I), I wanted to see if I could avoid setting up 50-100 agreements and going thru the hassle of getting them all to provide correct ISA 6/8 values.  This is why I am interested in the fallback settings.  I do have the enable fallback settings flag turned on, and am getting the errors described above.

     

     


    Mike Dugan
    Wednesday, April 6, 2011 2:36 PM
  • Hi Mike,

    I think a workable approach for you should be to write a custom pipeline component to set dummy ISA values. Then configure the custom pipeline run before EdiReceive.

    Thanks.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, April 11, 2011 10:29 AM
    Moderator
  • thanks for reply.  I can do this, but still am curious about using fallback settings.  My assumption (which may be wrong) is that fallback settings, if used, are suppose to help process interchanges without party agreements.  I would have thought (again, assuming...)  that fallback settings being active would allow messages to continue through, using whatever values are present in the ISA Envelope (specifically 5,6,7,8). 

    If fallback settings don't pass through messages, how can it be effectively used - could you give me an example?


    Mike Dugan
    Monday, April 11, 2011 12:12 PM
  • Mike,

    I would suggest you to run a SQL trace on BizTalkMgmtDb and look for the parameters passed to the following SP's

    dbo.bt_GetDocSpecInfoByID
    dbo.bt_GetDocSpecInfoByMsgType
    dbo.bt_GetDocSpecInfoByName

    Recently i had a similar issue with processing 5010 files on Biztalk 2009, i was receiving error messages like "parameter null" and "Generate ack"  issues,

    EDI Disassembler was looking for message type as "http://schemas.microsoft.com/BizTalk/EDI/X12/2006#X12_00501_837"

    But the message type deployed is "http://schemas.microsoft.com/BizTalk/EDI/X12/2006#X12_00501_837_P"

    It turned out that i did not install the patch properly. i moved the 837 schema's to BizTalkEDIApplication and deployed the patch. it worked properly.

     


    Sathish - http://blog.tsathish.com - Please Indicate "Mark as Answer" if this Post has Answered the Question
    Monday, April 11, 2011 2:36 PM
  • Sathish

    here is what I found in trace after processing file with no party agreement:

    exec bt_GetDocSpecInfoByID @id=N'{18739932-A782-4F55-B3C6-65901963A4D3}'
    exec bt_GetDocSpecInfoByID @id=N'{243482A2-79A4-4C17-96BF-CD33C0AF128D}'
    exec bt_GetDocSpecInfoByMsgType @nvcMsgtype=N'http://schemas.microsoft.com/BizTalk/EDI/X12/2006#X12_ServiceSchemaExtension',@iPipelineAssemblyId=112,@iFlag=@p3 output
    exec bt_GetDocSpecInfoByID @id=N'{304E0342-7496-4B9C-BEEB-E4AB16A1A120}'

     

    how do I make use of thid data?  thanks, and again, I am on BT2010

     

     


    Mike Dugan
    Monday, April 11, 2011 5:52 PM
  • Mike,

    For all the bt_GetDocSpecInfoByID try executing in query analyzer to find out it's returning the message type as "http://schemas.microsoft.com/BizTalk/EDI/X12/2006#X12_00401_837_P"


    Sathish - http://blog.tsathish.com - Please Indicate "Mark as Answer" if this Post has Answered the Question
    Monday, April 11, 2011 7:34 PM
  • I get the following response for the 3 instances of GetDocSpec:

     

    http://schemas.microsoft.com/Edi/X12ServiceSchema#X12_ServiceSchema
    no record
    http://schemas.microsoft.com/BizTalk/EDI/X12/2006#X12_00401_837_P

    does this look correct?

     

     


    Mike Dugan
    Monday, April 11, 2011 7:38 PM
  • Yes, it's correct.. in the initial post you have specified the error as

    6: Finding the document specification by message type "http://schemas.microsoft.com/BizTalk/EDI/X12/2006#X12_00401_837" failed. Verify the schema deployed properly.

    It's kind of misleading as it was looking for schema without "_P" at the end


    Sathish - http://blog.tsathish.com - Please Indicate "Mark as Answer" if this Post has Answered the Question
    Tuesday, April 12, 2011 2:15 PM
  • not sure if I undertstand: that is what #6 says - I copied/pasted from event viewer. 


    Mike Dugan
    Tuesday, April 12, 2011 2:52 PM
  • Let me try setting up the party similar to your scenario, and will let you know the outcome.
    Sathish - http://blog.tsathish.com - Please Indicate "Mark as Answer" if this Post has Answered the Question
    Tuesday, April 12, 2011 3:37 PM
  • Mike,

    I tried processing a 837P file without having an agreement setup, i was able to disassemble the file and convert into XML. However i am getting the same error as you mentioned for 997 and TA1 (Agreement Resolution based on the context properties for x12 Protocol has failed.)

     


    Sathish - http://blog.tsathish.com - Please Indicate "Mark as Answer" if this Post has Answered the Question
    Wednesday, April 13, 2011 1:27 PM
  • OK, good to know it wasn't just me - any other steps we can take to resolve?

    Mike Dugan
    Wednesday, April 13, 2011 4:22 PM
  • Just trying to summarize issue again and see if anyone has any thoughts on this:  last update is:

    I tried processing a 837P file without having an agreement setup, i was able to disassemble the file and convert into XML. However i am getting the same error as you mentioned for 997 and TA1 (Agreement Resolution based on the context properties for x12 Protocol has failed.)

     

    Anyone using default agreements successfully in bt2010?


    Mike Dugan
    Tuesday, April 19, 2011 8:51 PM
  • Hi Mike,

    For the error " Finding the document specification by message type "http://schemas.microsoft.com/BizTalk/EDI/X12/2006#X12_00401_837" failed." Can you check out the section for X12 Schema Discovery in the following link http://msdn.microsoft.com/en-us/library/bb246089(v=bts.70).aspx. As you are using 4010A1 837_P, your incoming document should have 004010X098A1 at GS08. Or if providing  004010X098A1 at GS08 is not a requirement for your other partners, then I would recommend you to deploy 837_P schema by removing `_P` extension at the root node, such that the schema that you have deployed would be "http://schemas.microsoft.com/BizTalk/EDI/X12/2006#X12_00401_837" and that is what EDI Receive pipeline would look for.

    Regarding the other error for the 997 and TA1 documents failing with "Agreement Resolution based on the context properties for x12 Protocol has failed.". It is a new constraint that we have imposed on the EDI users in BizTalk 2010 that the 997/TA1 that gets generated in EDI Receive Pipeline for an incoming document should resolve to an agreement with Sender and Receiver Identities which are the reverse of the Sender and Receiver Identities (ISA 5 6 7 8) in the incoming document. EDI Receive Pipeline would promote the following context properties DestinationPartyReceiverIdentifier, DestinationPartyReceiverQualifier, DestinationPartySenderIdentifier, DestinationPartySenderQualifier and EDI Send Pipeline has to do Agreement resolution based on them. Hence, there has to be an agreement with those particular identities otherwise the acknowledgements would fail. For your scenario I dont see any other way for you other than writing a custom pipeline component to remove those context properties by nullifying the values of the above mentioned context properties for all the messages with MessageType is http://schemas.microsoft.com/Edi/X12#X12_TA1_Root or http://schemas.microsoft.com/Edi/X12#X12_997_Root such that the messages would resolve to fallback settings. For more details on Agreement Resolution in EDI Send Pipeline please go through the link http://msdn.microsoft.com/en-us/library/bb259945(v=BTS.70).aspx

     

    Thanks,

    Kowshik Palivela

    Wednesday, April 20, 2011 11:08 AM
  • Thank you for your reply.  Regarding the first problem,  " Finding the document specification by message type "http://schemas.microsoft.com/BizTalk/EDI/X12/2006#X12_00401_837" failed."  Our files do come in with either 004010X098A1 or 004010X096A1 in the GS08 element.  I am using the schemas provided by Biztalk without modification and still am getting the error.  I reviewed the link for Schema Discovery and we are using a port that does not have either of the drop/keep messages if authentication fails checked.  So I believe I have this set correctly.

     

    I am reviewing the detail you provided for my second problem, but can you give me any more insight on the first issue?


    Mike Dugan
    Wednesday, April 20, 2011 12:39 PM
  • Hi Mike,

     

    If the GS08 value in the incoming document has the right value then EDI Receive Pipeline would try to resolve to the right variation (837_P/ 837_I in your case) of 837 if ST01 value is 837. But if the variation of the schema is not deployed in BizTalk then we fallback to regular 837 with the version from ISA12 and try to resolve to that schema. The error message as you are seeing wouldnt include the failure to resolve to the schema variation from GS08.

    Can you copy paste the ISA, GS and ST segments from your inbound message and make sure that there are no custom targetnamespaces that are set in the fallback settings?

    Please open a RFC if you want more details regarding the fix/work around that is suitable for your scenario.

     

    Thanks,

    Kowshik Palivela

    Monday, April 25, 2011 9:53 AM
  • kowshik

    I am not sure what a RFC is - can you explain? 

    I now have my default agreement working now: a file that is not part of an agreement will be processed by my orchestration correctly. 

     I believe the only thing not working is the TA1 and 997 creation when file is not part of agreement.  Based on your prior post, this is by design and is something I cannot change.  Is that correct?

     


    Mike Dugan
    Monday, April 25, 2011 1:22 PM
  • Hi Mike,

     

    As I explained TA1 and 997 in BizTalk 2010 require an agreement to be present with sender and receiver identities which are a swap of the sender and receiver identities of the incoming document. This is by design and this design ensures that the 997 and TA1 that are generated by EDI Receive Pipeline would go back to the sender party according to the settings which are required by the sender party.

     

    You can override this working by placing a custom pipeline component after EDI Disassembler or before EDI Assembler by nullifying/removing the following DestinationPartyReceiverIdentifier, DestinationPartyReceiverQualifier, DestinationPartySenderIdentifier, DestinationPartySenderQualifier context properties on 997 and TA1. In which case the 997 and TA1 would resolve to the fallback settings (if there are no other agreement resolution related context properties are present on the message).

     

    RFC is Request for Collaboration.  You can go through the following link for filing one.

    Support incident on BizTalk Server 2010.

    https://support.microsoft.com/oas/default.aspx?gprid=15637&st=1&wfxredirect=1&sd=gn

    Thanks,

    Kowshik Palivela

    Tuesday, April 26, 2011 6:52 AM
  • Hi Satish,

    You have mentioned following issue:

    "EDI Disassembler was looking for message type as "http://schemas.microsoft.com/BizTalk/EDI/X12/2006#X12_00501_837"

    But the message type deployed is "http://schemas.microsoft.com/BizTalk/EDI/X12/2006#X12_00501_837_P"

    It turned out that i did not install the patch properly. i moved the 837 schema's to BizTalkEDIApplication and deployed the patch. it worked properly."

    I have same issue as above, but i don't understand what patch you are talking about.

    Besides i'm working on BizTalk Server 2009.

    Please reply ASAP

    Thanks in Advance.

    Monday, October 29, 2012 5:09 PM
  • Hi Mike,

    I came across similar issue related to EDIFACT schema D96A Order. I gone through many articles of MSDN and tried to deploy "EDI D96A" schema from EDI schema extension folder from BizTalk installed folder, which resolved my disassembler issue. Later, the issues i came across related to segments values are not correct. To resolve this issue and which works in my environment is, I realized my EDI D96A schema has custom target namespace and due to which message box / EDI Receive pipeline could not parse the incoming messages. I follow the MSDN link  custom target namespace step and configured my custom target namespace in Fallback settings and all the issues has been resolved.

    could you please check your environment fallback setting and also validate your X12 schema namespace part of solution?

    Thursday, December 19, 2013 8:02 PM