Microsoft KB Archive/938839

= FIX: A trade partner may reject an RNIF 1.1 document or an RNIF 2.0 document that you generate by using BizTalk Accelerator for RosettaNet 3.3 =

Article ID: 938839

Article Last Modified on 11/15/2007

-

APPLIES TO


 * Microsoft BizTalk Server 2006 Developer Edition
 * Microsoft BizTalk Server 2006 Enterprise Edition
 * Microsoft BizTalk Server 2006 Standard Edition

-



SYMPTOMS
Consider the following scenario. You install Microsoft BizTalk Server 2006 and BizTalk Accelerator for RosettaNet 3.3. You use BizTalk Accelerator for RosettaNet 3.3 to generate a RosettaNet Implementation Framework (RNIF) 1.1 document or an RNIF 2.0 document. You send the document to a trade partner.

In this scenario, the trade partner may reject the RNIF1.1 document or the RNIF 2.0 document because the document has invalid content in the GlobalTransactionCode or GlobalProcessCode fields. When this problem occurs, you notice that the values for the GlobalProcessCode field and the GlobalTransactionCode field that are in the following two paths are identical:
 * /ServiceHeader/ProcessControl/ProcessIdentity/GlobalProcessCode
 * /ServiceHeader/ProcessControl/TransactionControl/TransactionIdentity/GlobalTransactionCode



CAUSE
This problem occurs because of how BizTalk Accelerator for RosettaNet 3.3 generates RNIF documents. When BizTalk Server 2006 generates RNIF 1.1 documents, BizTalk Accelerator for RosettaNet 3.3 uses the value from the Process Name field in the configuration process to populate both the GlobalProcessCode field and the GlobalTransactionCode field for the Service Header elements. However, these two fields must be populated independently. In this case, some Partner Interchange Processes (PIPs) require that these fields contain different values. However, BizTalk Accelerator for RosettaNet 3.3 always uses the same value to populate these fields. When this behavior, the trade partner rejects the RNIF 1.1 document or the RNIF 2.0 document.



RESOLUTION
This hotfix updates the components that BizTalk Accelerator for RosettaNet 3.3 uses to process PIP documents. Before you apply this hotfix on the BizTalk Server 2006 server, make sure that all PIP processing has finished and all RosettaNet orchestrations have finished.

After you run the Setup.exe file in this hotfix, you must manually run the SQL script Update_BTARNConfig_PIPConfig.sql on the server that is running SQL Server and hosting the BTARNCONFIG database. For more information, see the Readme.txt file that is included in the hotfix package.

Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that this article describes. Apply this hotfix only to systems that are experiencing this specific problem.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
You must have BizTalk Server 2006 and BizTalk Accelerator for RosettaNet 3.3 installed to apply this hotfix.

Restart requirement
You must restart BizTalk services after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information about the GlobalProcessCode and GlobalTransactionCode fields in RNIF 1.1, visit the following Web site:

http://portal.rosettanet.org/cms/sites/RosettaNet/Standards/RStandards/rnif/

Keywords: kbexpertiseinter kbhotfixserver kbqfe KB938839

-

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

© Microsoft Corporation. All rights reserved.