Documents Are Not Moved to the Suspended Queue After a Custom Pre-Processing Component Failure (815478)


The information in this article applies to:

  • Microsoft BizTalk Server 2002

SYMPTOMS

When you use a non-transactional queue name in a Message Queueing receive function, documents are not moved to the suspended queue after a custom pre-processing component failure occurs. That is, when a failure occurs in a pre-processing component, the Message Queueing message is removed from the polling Message Queueing queue name, and no items appear in the suspended queue. Even though you see the following event ID message, and the description says that the document will be put in the suspended queue, no item is put in the BizTalk Server suspended queue: Event ID: 324
Category: Document Processing
Description: An error occurred in BizTalk Server.
Details: [0x1724] The custom preprocessing component used by the receive function "BENKEN - MSMQ Non-txn RF" failed. This document will be moved to the Suspended queue.
[0x80004005]
[0x1916] There was a serious failure in the receive function "BENKEN - MSMQ Non-txn RF". This receive service will be shut down, please check the event log for additional error messages.
[0x1916] There was a serious failure in the receive function "(null)". This receive service will be shut down, please check the event log for additional error messages. On the other hand, when you use a file receive function type, the document is dropped to the suspended queue if a pre-processing component failure occurs.

CAUSE

In the Message Queueing receive path, if the preprocessor component fails, the design incorrectly overrides the logic of the code that the handle returns. Because of this, the data is not dropped to the suspended queue correctly.

RESOLUTION

Service Pack Information

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

815781 How to Obtain the Latest BizTalk Server 2002 Service Pack

Hotfix Information

A supported fix is now available from Microsoft, but it is only intended to correct the problem described in this article. Only apply it to systems that are experiencing this specific problem. This fix may receive additional testing to further ensure product quality. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) 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 
------------------------------------------------------
28-Feb-2003  06:25  3.0.1562.0  131,344  Cisapi.dll
28-Feb-2003  06:25  3.0.1562.0  528,656  Ciscore.dll
28-Feb-2003  06:25  3.0.1562.0  409,872  Cisengine.dll
28-Feb-2003  06:25  3.0.1562.0  352,528  Mscis.exe

STATUS

This problem was first corrected in Microsoft BizTalk Server 2002 Service Pack 1.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION


For additional information about the latest service pack for BizTalk Server 2002, click the following article number to view the article in the Microsoft Knowledge Base:

815781 How to Obtain the Latest BizTalk Server 2002 Service Pack


Implementing the hotfix or installing the service pack will also changes the behavior of the transactional Message Queueing queues if a pre-processing component failure occurs. Previously, the messages would stay in the Message Queueing queue name if a failure occurs. With the new functionality, messages are removed from the original queue and are put in the suspended queue of the Biztalk Server computer. This means that consistent behavior occurs for all file and non-transactional and transactional Message Queueing receive functions.
Modification Type:MinorLast Reviewed:10/6/2005
Keywords:kbBizTalk2002SP1fix KB815478 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.