You receive a "Completed with discarded message" message in the HAT tool when you use a sequential convoy in BizTalk Server 2004 (914588)



The information in this article applies to:

  • Microsoft BizTalk Server 2004 Standard Edition
  • Microsoft BizTalk Server 2004 Developer Edition
  • Microsoft BizTalk Server 2004 Enterprise Edition
  • Microsoft BizTalk Server 2004 Partner Edition

SYMPTOMS

When you use a sequential convoy in Microsoft BizTalk Server 2004, you may receive a message that is similar to the following in the Health and Activity Tracking (HAT) tool for an orchestration instance:Completed with discarded messageThis issue occurs when the convoy uses a long-running transactional scope that has a time-out setting.

Additionally, you may notice that you receive fewer output and "Completed with discarded messages" messages than input messages.

CAUSE

This issue occurs when the following conditions are true:
  • A time-out exception occurs.
  • An exception handler does not handle the message.

RESOLUTION

To resolve this issue, use one of the following methods.

Method 1: Use a send port in an exception handler

To resolve this issue, use a send port in an exception handler to send the unconsumed message to another destination for processing.

Method 2: Use a WMI script

To resolve this issue, use a Windows Management Instrumentation (WMI) script to save the message to a file. Then, submit the file again for processing.

STATUS

This behavior is by design.

MORE INFORMATION

When a time-out exception occurs, BizTalk Server 2004 calls an exception handler. The exception handler should also handle the message. If the exception handler does not handle the message, the message may be lost.

REFERENCES

For more information about convoy message processing, visit the following Microsoft Developer Network (MSDN) Web site:

Modification Type:MajorLast Reviewed:3/7/2006
Keywords:kbBTSOrchestration kbBTSHat kbtshoot kbprb KB914588 kbAudDeveloper kbAudITPRO