Microsoft KB Archive Search

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.

  1. Home
  2. FIX: Multiple Transaction Groups Submitted Directly to Channel Do Not Generate Receipts

FIX: Multiple Transaction Groups Submitted Directly to Channel Do Not Generate Receipts

View products that this article applies to.

This article was previously published under Q303532

↑ Back to the top

Symptoms

When a document with multiple transaction groups is submitted directly to a channel, the parser generates a receipt, which is sent back to the sender for the first transaction group only. Subsequent transaction groups may fail to generate receipts. The Suspended Queue shows the original document instead of the canonical receipt. In addition, the BizTalk Server Application log may contain the following error:
An error occurred in BizTalk Server

Details:
The XML document could not be translated. The map specified by reference "http://SERVERNAME/BizTalkServerRepository/Maps/Microsoft/MAP_NAME.xml" failed. Verify that the map is up to date.

The following channel configuration setting is not valid: "receipt_channel"

The server could not finish processing the document.

Suspended Queue ID: "{5502FC3B-BC0A-40C2-9EDF-207C977DCD95}"

The server could not finish processing the document.

↑ Back to the top

Cause

After the first transaction, every parsed transaction ends up in the wrong channel (in this case, the receipt channel) and the actual receipts are lost.

↑ Back to the top

Resolution

To resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
299664 INFO: How to Obtain the Latest BizTalk Server 2000 Service Pack

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in BizTalk Server 2000. This problem was first corrected in Microsoft BizTalk Server 2000 Service Pack 1a.

↑ Back to the top

Keywords: KB303532, kbbiztalk2000sp1afix, kbfix, kbbug

↑ Back to the top

Article Info
Article ID : 303532
Revision : 3
Created on : 10/22/2003
Published on : 10/22/2003
Exists online : False
Views : 396