FIX: BizTalk Server 2002 rejects reliable receipts over HTTP from BizTalk Server 2006 or from BizTalk Server 2004 (839336)


The information in this article applies to:

  • Microsoft BizTalk Server 2006 Enterprise Edition
  • Microsoft BizTalk Server 2006 Developer Edition
  • Microsoft BizTalk Server 2006 Standard Edition
  • Microsoft BizTalk Server 2004 Enterprise Edition
  • Microsoft BizTalk Server 2004 Developer Edition
  • Microsoft BizTalk Server 2004 Partner Edition
  • Microsoft BizTalk Server 2004 Standard Edition
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry

SYMPTOMS

When you exchange reliable messages between Microsoft BizTalk Server 2002 and either Microsoft BizTalk Server 2006 or Microsoft BizTalk Server 2004, your BizTalk Server 2002-based server may reject the reliable receipts from the BizTalk Server 2006-based server or from the BizTalk Server 2004-based server. When this problem occurs, you receive two error messages that are similar to the following:

Message 1
An error occurred in BizTalk Server.

Details:
------------------------------
[0x1439] No parser component recognizes the data. This might be caused by an interchange
specification that is missing or not valid, or it might be caused by data that is not
valid. Verify that both the interchange specification (if one is specified) and the data match.

[0x1730] Suspended Queue ID: "{862C654C-41BC-49D0-8E62-9FD8687EF7AF}"
Message 2
An error occurred in BizTalk Server.

Details:
------------------------------
[0x012a] All retry transmissions failed.

[0x172f] The server has not received a receipt for the reliable message.

[0x0156] The server could not finish processing messaging port

RESOLUTION

BizTalk Server 2006

To resolve this problem, you must modify the registry. To do this, follow the steps in the "More Information" section.

BizTalk Server 2004

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2004. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

888751 How to obtain the latest BizTalk Server 2004 service pack

Important After you install the service pack, you must modify the registry. To do this, follow the steps in the "More Information" section.

Hotfix 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 tool in Control Panel.
   Date        Time    Version     Size     File name
   ----------------------------------------------------------------------------------
   01-Apr-2004  18:56  3.0.5268.0  266,240  Microsoft.biztalk.pipeline.components.dll
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

STATUS

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

BizTalk Server 2004

This problem was corrected in BizTalk Server 2004 Service Pack 1.

MORE INFORMATION

For more information, 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

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

This problem occurs because BizTalk Server 2006 and BizTalk Server 2004 automatically add an XML declaration that includes the encoding type of UTF-8 to the reliable receipt. When this receipt is received by BizTalk Server 2002 through the HTTP transport, the document is converted to a string and the encoding type is no longer valid. To enable this fix, create a DWORD value in the registry. To do this, follow these steps:
  1. Click Start, click Run, type regedit in the Open box, and then click OK to start Registry Editor.
  2. In Registry Editor, locate and then click the following registry key:

    \HKey_Local_Machine\SYSTEM\CurrentControlSet\Services\BTSSvc.3.0\

  3. On the Edit menu, click New, and then click DWORD Value.
  4. For the Value name, type SkipReceiptXmlEncoding. For the Value data, type 0 or 1.

    Note By default, the value of the Value data property is 0. If you set this property value to 1, you enable this fix.
  5. Exit Registry Editor.
Modification Type:MinorLast Reviewed:6/1/2006
Keywords:kbBizTalk2004sp1fix kbfix kbbug kbHotfixServer kbQFE KB839336 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.