Microsoft KB Archive/914589

= An event ID 0 error message is logged in the BizTalk Server Application log when you receive RNIF documents from a trading partner in BizTalk Accelerator for RosettaNet 3.0 =

Article ID: 914589

Article Last Modified on 3/8/2006

-

APPLIES TO


 * Microsoft BizTalk Accelerator for RosettaNet 3.0 Standard Edition
 * Microsoft BizTalk Accelerator for RosettaNet 3.0 Enterprise Edition

-





SYMPTOMS
When you receive a RosettaNet Implementation Framework (RNIF) document from your trading partner in Microsoft BizTalk Accelerator for RosettaNet 3.0, an error message that is similar to one of 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

Description:

Source module:

PublicResponderProcess

Correlation information:

PIP Code : 0C1

PIP Version : T01.02

PIP InstanceID: 1ca34f2d-7c04-4417-b1c7-ac103ef33791x

SourcePartnerName : HOME

DestinationPartnerName : PARTNER

Description:

Public Responder could not send an Async exception signal due to internal errors below:

RNIF Exception detail:-

Error code:UNP.SHDR.VALERR

Error Number:2005

Description: A PIP name that is not valid was specified.

Event Type: Error

Event Source: BizTalk Accelerator for RosettaNet

Event Category: None

Event ID: 0

Description:

Source module:

PublicResponderProcess

Correlation information:

PIP Code : 0C1

PIP Version : T01.02

PIP InstanceID: 25397620-88f2-479c-8e56-3f0a3229d2ez

SourcePartnerName : HOME

DestinationPartnerName : PARTNER

Description: Public Responder could not send an Async exception signal due to internal errors below:

RNIF Exception detail:-

Error code:UNP.SHDR.VALERR

Error Number:2005

Description: PIP name specified does not match the PIP specification.



CAUSE
This problem occurs when the value in the Process Name field in the Partner Interface Process (PIP) does not match the Process Name value in the incoming document.



RESOLUTION
To resolve this problem, use one of the following methods.

Method 1
To resolve this problem for RNIF 1.1 documents, make sure that the value in the Process Name field in the PIP matches the value in the  element of the incoming document.

Method 2
To resolve this problem for RNIF 2.0 documents, make sure that the value in the Process Name field in the PIP matches the value in the  element of the incoming document.



Steps to reproduce the problem

 * 1) Use the Partner Agreement Wizard to create a trade agreement between two organizations by using the 0C1 PIP process.
 * 2) Modify the 0C1 process so that the organizations use a different value for the Process Name field.
 * 3) Use the Lobapplication.exe application in the Microsoft BizTalk Accelerator for RosettaNet 3.0\SDK folder to submit a 0C1 data instance.

Keywords: kbtshoot kbprb kbbtsrosetta kbbtsaccelerators KB914589

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.