The following symptoms occur only during the fall standard time change in Microsoft BizTalk Server 2006.

If an orchestration has a delay shape that causes the orchestration to end after the 2:00 A.M. daylight saving time (DST) change, the orchestration skips the shape and is completed. However, if the orchestration finishes before 2:00 A.M, the orchestration proceeds as expected.

If an orchestration has a long-running transaction, and the time-out delay lands beyond the DST change, the transaction times out as soon as it is started. If the transaction lands before 2:00 A.M., the transaction proceeds as expected.

If an orchestration has an atomic transaction with retries enabled, and the transaction is being retried during the DST change, the orchestration will be suspended. If this hotfix is not applied and this issue occurs, the orchestration is suspended and can be resumed manually. To manually resume service instances in BizTalk Server 2006, follow the steps in the "Workaround" section.

The following symptom occurs only during the spring DST time change in BizTalk Server 2006.

If an orchestration contains a delay shape, and an orchestration instance is dehydrated at the delay shape during a DST time change, the rehydration of the orchestration will be delayed. If this hotfix is not applied and this issue occurs, the dehydrated orchestrations will remain dehydrated for an additional hour after the expected rehydration time. After the additional hour, the orchestration will rehydrate and continue.

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft BizTalk Server 2006 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone 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.

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.

Uninstallation

This hotfix can be uninstalled.

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.

File name	File version	File size	Date	Time
Btsmessageagent.dll	3.5.1657.0	694,120	15-Feb-2007	03:13
Microsoft.biztalk.interop.agent.dll	3.5.1657.0	58,760	15-Feb-2007	03:13
Microsoft.xlangs.biztalk.engine.dll	3.5.1657.0	238,984	15-Feb-2007	03:13
Microsoft.xlangs.engine.dll	3.5.1657.0	255,352	15-Feb-2007	03:13
Microsoft.xlangs.runtimetypes.dll	3.5.1657.0	120,200	15-Feb-2007	03:13

To manually resume service instances in BizTalk Server 2006, follow these steps:

1.	Click Start, click Programs, click Microsoft BizTalk Server 2006, and then click BizTalk Server Administration.
2.	In the console tree, expand BizTalk Server 2006 Administration, and then click the BizTalk group.
3.	In the details pane, click the New Query tab.
4.	In the Query Expression group, click the following in the Field Name column: Instance Status Operator Equals Value Suspended Resumable
5.	Do one of the following: To resume a single instance, next to the asterisk (*) in the Field Name column, click the Service Name filter. Then, in the Value column, specify the service name. To resume instances in bulk, next to the asterisk (*) in the Field Name column, click Group Results By. Then, in the Value column, specify the service name.
6.	Click Run Query.
7.	In the query results list, right-click the orchestration instance that you want to resume, and then click Resume Instance or Resume Instances.

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

For more information about support for DST changes in the Microsoft Windows operating systems, visit the following Microsoft Web site: For more information, click the following article number to view the article in the Microsoft Knowledge Base: