Article ID: 938839 - View products that this article applies to.
Consider the following scenarios:
In these scenarios, 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:
This problem occurs because of how BizTalk Accelerator for RosettaNet 3.3 and BizTalk Accelerator for RosettaNet 3.5 generate RNIF documents. When BizTalk Server 2006 and BizTalk Server 2006 R2 generate RNIF 1.1 documents, BizTalk Accelerator for RosettaNet 3.3 and BizTalk Accelerator for RosettaNet 3.5 use 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 and BizTalk Accelerator for RosettaNet 3.5 always use always uses the same value to populate these fields. When this behavior occurs, the trade partner rejects the RNIF 1.1 document or the RNIF 2.0 document.
This hotfix updates the components that BizTalk Accelerator for RosettaNet 3.3 and BizTalk Accelerator for RosettaNet 3.5 use to process PIP documents. Before you apply this hotfix on the BizTalk Server 2006 server or on the BizTalk Server 2006 R2 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 informationThere are two versions of this hotfix:
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesYou must have BizTalk Server 2006 and BizTalk Accelerator for RosettaNet 3.3 installed to apply the RosettaNet 3.3 hotfix. You must have BizTalk Server 2006 R2 and BizTalk Accelerator for RosettaNet 3.5 installed to apply the RosettaNet 3.5 hotfix.
Restart requirementYou must restart the BizTalk services after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe 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.
Collapse this tableExpand this table
Collapse this tableExpand this table
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 938839 - Last Review: January 31, 2008 - Revision: 2.3