Fallback Settings Not working for Non-Agreement Senders

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

Answer 1

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