An error message is logged in the BizTalk Application log when you use the BizTalk Accelerator for RosettaNet version 3.0 to receive RNIF documents (905731)
The information in this article applies to:
- Microsoft BizTalk Accelerator for RosettaNet 3.0 Standard Edition
- Microsoft BizTalk Accelerator for RosettaNet 3.0 Enterprise Edition
SYMPTOMSWhen you use the Microsoft BizTalk Accelerator for RosettaNet version 3.0 to receive RosettaNet Implementation Framework (RNIF) documents, an error message that is similar to the following is logged in the BizTalk Server Application log: Event Type: Error Event Source: BizTalk Accelerator for RosettaNet Event Category: None Event ID: 0 Source module: PublicResponderProcess
Correlation information:
PIP Code : 3A2 PIP Version : R02.00A PIP InstanceID: 5DDC5EBEX79D2X4550X9817X1DCC9B8A78C2 SourcePartnerName : PARTNER DestinationPartnerName : HOME
Description:
Failed to read XPath for document named 'DeliveryHeader' at path: /dfns:DeliveryHeader/dfns:messageReceiverIdentification/dfns:PartnerIdentification/dfns:domain/dfns:FreeFormText
For more information, see Help and Support Center at http://support.microsoft.com. CAUSEThis error message is logged if the incoming RNIF document is missing a field that the PrivateResponder Orchestration expects.
For example, you will receive this error message if the DeliveryHeader element in the incoming RNIF document is missing the <messageReceiverIdentification><domain><FreeForm> element. This element is declared as an optional component in the schema in the PrivateResponder Orchestration. However, the PrivateResponder Orchestration verifies that the <messageReceiverIdentification><domain><FreeForm> element exists and that its value is DUNS.RESOLUTIONTo resolve this issue, use the Microsoft BizTalk Accelerator for RosettaNet Optional Fields Pipeline Component to add the missing field to the incoming RNIF document. After you do this, use the sample BizTalk Accelerator for RosettaNet receive pipeline to create a custom pipeline.
Note You must set the RNIF_Receive_async receive location and the RNIF_Receive_sync receive location to use the custom pipeline that you create.STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Major | Last Reviewed: | 9/22/2006 |
---|
Keywords: | kbtshoot kbBug kbprb KB905731 kbAudDeveloper kbAudITPRO |
---|
|