The following symptoms occur only at the end time of a daylight saving period in Microsoft BizTalk Server 2006.
If an orchestration has a delay shape that causes the orchestration to end after the end time, the orchestration skips the shape and is completed. However, if the orchestration finishes before the end time, the orchestration proceeds as expected.
If an orchestration has a long-running transaction, and the time-out delay lands beyond the end time, the transaction times out as soon as it is started. If the transaction lands before the end time, the transaction proceeds as expected.
If an orchestration has an atomic transaction with retries enabled, and the transaction is being retried at the end time, 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 at the end time of a daylight saving period in BizTalk Server 2006.
If an orchestration contains a delay shape, and an orchestration instance is dehydrated at the delay shape at the end time, 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.
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.