Fix: Orchestration Stops Responding When You Correlate Messages to Existing XLANG Schedules (320527)



The information in this article applies to:

  • Microsoft BizTalk Server 2002

This article was previously published under Q320527

SYMPTOMS

When you correlate messages to running BizTalk schedule instances, and some of the instances have been dehydrated, some of the schedules may not complete.

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 that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem immediately, download the fix by clicking the download link later in this article or 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: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 should have the following file attributes or later:
   Date          Time  Version     Size      File name
   ------------------------------------------------------
   02-Apr-2002  18:38  3.0.1500.0  3,195,152 Skedcore.dll
				

STATUS

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

MORE INFORMATION

This problem occurs when you run multiple instances of an XLANG schedule that depends on the completion of two separate transactions. When one or more of the instances of the scheduler dehydrate while the instance or instances wait for one of the transactions to complete, the XLANG Scheduler stops responding (hangs).

Modification Type:MinorLast Reviewed:9/27/2005
Keywords:kbHotfixServer kbQFE kbBizTalk2002SP1fix kbbug kbfix KB320527