You are currently offline, waiting for your internet to reconnect

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

SYMPTOMS
Consider one of the following scenarios:
  • You install Microsoft BizTalk Server 2004 and Microsoft BizTalk Accelerator for RosettaNet 3.0 on a server.
  • You install Microsoft BizTalk Server 2006 R2 and Microsoft BizTalk Accelerator for RosettaNet 3.5 on a server.
To notify a trade partner that a failure occurred, you use BizTalk Accelerator for RosettaNet 3.0 or BizTalk Accelerator for RosettaNet 3.5 to send a 0A1 message to the trade partner. In this scenario, the trade partner may reject the 0A1 message. Additionally, the following problems may occur:
  • The following nodes are always set to the GlobalSupplyChainCode_0 value:
    • Pip0A1FailureNotification/fromRole/PartnerRoleDescription/PartnerDescription/BusinessDescription/GlobalSupplyChainCode
    • Pip0A1FailureNotification/toRole/PartnerRoleDescription/PartnerDescription/BusinessDescription/GlobalSupplyChainCode
  • 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.
  • The following nodes are set to opposite values:
    • Pip0A1FailureNotification/fromRole/PartnerRoleDescription/GlobalPartnerRoleClassificationCode
    • Pip0A1FailureNotification/toRole/PartnerRoleDescription/GlobalPartnerRoleClassificationCode
RESOLUTION
This hotfix updates the components that Partner Interface Process (PIP) processing uses. Before you apply this hotfix on the server that is running BizTalk Server 2004 or BizTalk Server 2006 R2, make sure that all PIP processing is finished. Additionally, make sure that all orchestrations in BizTalk Accelerator for RosettaNet 3.0 or in BizTalk Accelerator for RosettaNet 3.5 are finished or are stopped.

Hotfix information

There are two versions of this hotfix:
  • BizTalk Accelerator for RosettaNet 3.0
  • 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.

Prerequisites

You must have Microsoft BizTalk Server 2004 and BizTalk Accelerator for RosettaNet 3.0 installed to apply the RosettaNet 3.0 hotfix. You must have Microsoft BizTalk Server 2006 R2 and BizTalk Accelerator for RosettaNet 3.5 installed to apply the RosettaNet 3.5 hotfix.

Restart requirement

You must restart the 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.
RosettaNet 3.0
File nameFile versionFile sizeDateTimePlatform
Microsoft.solutions.btarn.configurationmanager.dll3.0.750.0275,88027-Jul-200711:24x86
RosettaNet 3.5
File nameFile versionFile sizeDateTimePlatform
Microsoft.solutions.btarn.configurationmanager.dll3.5.304.0271,44023-Jan-200808:16x86
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For the RosettaNet 3.3 version of this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:
940950 FIX: A trade partner may reject a 0A1 PIP message when you use BizTalk Accelerator for RosettaNet 3.3 to send the 0A1 message to the trade partner
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Properties

Article ID: 939014 - Last Review: 11/15/2007 14:51:59 - Revision: 1.4

Microsoft BizTalk Accelerator for RosettaNet 3.5 Enterprise Edition, Microsoft BizTalk Accelerator for RosettaNet 3.5 Standard Edition, Microsoft BizTalk Accelerator for RosettaNet 3.0 Enterprise Edition, Microsoft BizTalk Accelerator for RosettaNet 3.0 Standard Edition, Microsoft BizTalk Server 2004 Developer Edition, Microsoft BizTalk Server 2004 Enterprise Edition, Microsoft BizTalk Server 2004 Partner Edition, Microsoft BizTalk Server 2004 Standard Edition, Microsoft BizTalk Server 2006 R2 Developer Edition, Microsoft BizTalk Server 2006 R2 Enterprise Edition, Microsoft BizTalk Server 2006 R2 Standard Edition

  • kbautohotfix kbexpertiseinter kbhotfixserver kbqfe KB939014
Feedback
me='ms.dqp0';m.content='true';document.getElementsByTagName('head')[0].appendChild(m);" onload="var m=document.createElement('meta');m.name='ms.dqp0';m.content='false';document.getElementsByTagName('head')[0].appendChild(m);" src="http://c1.microsoft.com/c.gif?"> ">&t=">