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.

FIX: A suspended orchestration instance is not resumed immediately in BizTalk Server 2006 if the orchestration contains a Delay shape


View products that this article applies to.

Symptoms

Consider the following scenario:
  • In Microsoft BizTalk Server 2006, you have a BizTalk orchestration that contains a Delay shape.
  • You restart the BizTalk host instance, and then you immediately restart the orchestration.
  • You enable the corresponding receive location.
  • You start the orchestration's corresponding send port.
  • You drop a message to the receive location of the orchestration.
  • The output file is displayed, and the orchestration instance is suspended.
  • You try to resume the suspended orchestration instance
In this scenario, the resume attempt fails immediately, and the orchestration instance enters a dehydrated state. The orchestration instance is not resumed until the delay timer has expired.

↑ Back to the top


Cause

When you try to resume an orchestration instance, a restart message is inserted into that instance. However, BizTalk Server does not do this if the orchestration instance has messages in the queue. In the scenario that is described in the "Symptoms" section, the existing messages in the queue are timer messages that will be delivered in the future. Therefore, when you try to resume a suspended orchestration instance, the instance is not resumed immediately.

↑ Back to the top


Resolution

Hotfix information

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 BizTalk Server 2006 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer 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.
Microsoft BizTalk Server 2006
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Btshttpreceive.dll3.5.1763.0183,82429-May-200821:17x86
Btsmessageagent.dll3.5.1763.0693,77629-May-200821:17x86
Btsmsg.dll3.5.1763.0195,07229-May-200821:17x86
Btsmsgcore.dll3.5.1763.01,225,73629-May-200821:17x86
Microsoft.biztalk.adapter.runtime.dll3.5.1763.083,00029-May-200821:16x86
Microsoft.biztalk.epmtransform.dll3.5.1763.019,50429-May-200821:16x86
Microsoft.biztalk.globalpropertyschemas.dll3.5.1763.0848,96029-May-200821:16x86
Microsoft.biztalk.interop.agent.dll3.5.1763.058,41629-May-200821:16x86
Microsoft.biztalk.streaming.dll3.5.1763.054,31229-May-200821:16x86
Microsoft.xlangs.basetypes.dll3.5.1763.099,36829-May-200821:16x86
Microsoft.xlangs.biztalk.crossprocess.dll3.5.1763.087,10429-May-200821:16x86
Microsoft.xlangs.biztalk.engine.dll3.5.1763.0238,64029-May-200821:16x86
Microsoft.xlangs.biztalk.process.dll3.5.1763.066,60829-May-200821:16x86
Microsoft.xlangs.bpel.bpelom.dll3.5.1763.0123,94429-May-200821:16x86
Microsoft.xlangs.bpel.bpeltranslator.dll3.5.1763.0488,50429-May-200821:16x86
microsoft.xlangs.engine.dll3.5.1763.0255,00829-May-200821:16x86
Microsoft.xlangs.runtimetypes.dll3.5.1763.0119,85629-May-200821:16x86
Msgbox_application_logic.sqlNot Applicable506,97014-Apr-200820:47Not Applicable
Xlangscompiler.dll3.5.1763.01,128,44829-May-200817:24x86


Note This hotfix inserts the restart message in the suspended queue when the instance is in a suspended state. When the instance that is in the suspended state is resumed, the messages that belong to this instance are moved from the suspended queue to the application queue. Additionally, the orchestration instance is started.

↑ Back to the top


Status

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

↑ Back to the top


More information

For more information about service instance states, visit the following Microsoft Developer Network (MSDN) Web site: For more information about how to resume suspended orchestration instances, visit the following Microsoft Developer Network (MSDN) Web site: For more information about the Delay shape, visit the following Microsoft Developer Network (MSDN) Web site:

↑ Back to the top


Keywords: KB951762, kbqfe, kbsurveynew, kbexpertiseinter, kbautohotfix, kbbiztalk2006presp1fix, kbbtsorchestration

↑ Back to the top

Article Info
Article ID : 951762
Revision : 2
Created on : 10/8/2011
Published on : 10/8/2011
Exists online : False
Views : 447