Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: A trade partner may reject a 0A1 PIP message when you use BizTalk Accelerator for RosettaNet 3.3 or 3.5 to send the 0A1 message to the trade partner


View products that this article applies to.

Symptoms

Consider the following scenario. You install Microsoft BizTalk Server 2006 and Microsoft BizTalk Accelerator for RosettaNet 3.3 or you install Microsoft BizTalk Server 2006 R2 and Microsoft BizTalk Accelerator for RosettaNet 3.5 on a server. You use BizTalk Accelerator for RosettaNet 3.3 or RosettaNet 3.5 to send a 0A1 Partner Interface Process (PIP) message to a trade partner. When a failure occurs during PIP processing and the agreement is configured to generate a 0A1 PIP message, the trade partner may reject the message.

This issue occurs because of the following problems:
  • If you use 0A1 PIP message version 1.0, you notice that the following node incorrectly contains the ContactInformation element:
    Pip0A1FailureNotification/toRole/PartnerRoleDescription/PartnerDescription/BusinessDescription/GlobalSupplyChainCode
  • If you use 0A1 PIP message version 2.0, the following nodes are set to the same value:
    • Pip0A1FailureNotification/fromRole/ContactInformation
    • Pip0A1FailureNotification/toRole/ContactInformation
    The value is the contact information for the home organization.

↑ Back to the top


Cause

When you use 0A1 PIP message version 1.0, the message is rejected because it does not follow the following file:
0A1FailureNotificationMessageGuideline.html
This file is published by RosettaNet.org. The Guideline.htm files are provided together with each PIP. These files contain validation information above and beyond what is contained in the .dtd schemas.

When you use 0A1 PIP message version 2.0, you experience the problem that is mentioned in the following article in the Microsoft Knowledge Base:
939014 FIX: A trade partner may reject a 0A1 message when you use BizTalk Accelerator for RosettaNet 3.0 or BizTalk Accelerator for RosettaNet 3.5 to send the 0A1 message to the trade partner

↑ Back to the top


Resolution

Hotfix information

There are two versions of this hotfix:
  • BizTalk Accelerator for RosettaNet 3.3
  • BizTalk Accelerator for RosettaNet 3.5
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

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: Note 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.

This hotfix updates the components that BizTalk Accelerator for RosettaNet 3.3 uses to process PIP messages. Before you apply this hotfix on the server that is running BizTalk Server 2006, make sure that all PIP processing is finished. Additionally, make sure that all orchestrations in BizTalk Accelerator for RosettaNet 3.3 are finished or are stopped.

Prerequisites

To install the BizTalk Accelerator for RosettaNet 3.3 version of this hotfix, you must have the following software installed:
  • BizTalk Server 2006
  • BizTalk Accelerator for RosettaNet 3.3
  • The hotfix that is mentioned in the following article in the Microsoft Knowledge Base:
    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 or for RosettaNet 3.5
To install the BizTalk Accelerator for RosettaNet 3.5 version of this hotfix, you must have BizTalk Server 2006 R2 installed.

Restart requirement

You must restart BizTalk Server 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.
BizTalk Accelerator for RosettaNet 3.3
File nameFile versionFile sizeDateTimePlatform
Btarnconfig.exe3.3.2014.019,29610-Aug-200712:12x86
Microsoft.solutions.btarn.adminsnapin.dll3.3.2014.0382,36010-Aug-200712:12x86
Microsoft.solutions.btarn.configurationmanager.dll3.3.2014.0271,78410-Aug-200712:12x86
Microsoft.solutions.btarn.shared.dll3.3.2014.0120,20810-Aug-200712:12x86
BizTalk Accelerator for RosettaNet 3.5
File nameFile versionFile sizeDateTime
Microsoft.Solutions.BTARN.ConfigurationManager.dll3.5.308.0271,44031-Jan-200800:35

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
939014 FIX: A trade partner may reject a 0A1 message when you use BizTalk Accelerator for RosettaNet 3.0 or BizTalk Accelerator for RosettaNet 3.5 to send the 0A1 message to the trade partner

↑ Back to the top


Keywords: kbautohotfix, kbhotfixserver, kbfix, kbbug, kbexpertiseinter, kbqfe, KB940950

↑ Back to the top

Article Info
Article ID : 940950
Revision : 5
Created on : 5/13/2008
Published on : 5/13/2008
Exists online : False
Views : 500