Home   |   Asp.Net 2.0   |   .Net Framework 2.0   |   IIS 6.0   |   Sql Server 2005   |   Visual Basic 2005   |   c# 2005   |   VS 2005   |   Visual Source Safe 2005

MS Dynamics CRM 3.0

SharePoint Portal Server 2003
SharePoint Server 2007
Dynamics NAV
Dynamics CRM
SharePoint Designer 2007
SharePoint Portal Server 2001
Windows SharePoint Services
Windows SharePoint Services 3.0
Project Server 2003
Project Server 2007
Dynamics – Point of Sale
Dynamics AX
Dynamics GP
Dynamics Retail Management System (RMS)
Dynamics SL
SQL Server 2000
Visual Basic .NET 2003
Visual C# .NET 2003
Visual C++ .NET 2003
Visual C++ 2005
Visual SourceSafe 6.0
Windows Server 2003
Windows Server 2003
Outlook 2003
ADO.NET 1.1
ASP.NET 1.0
Visual Studio Team Foundation Server
Visual Studio 2005 Team Edition
Windows Internet Explorer 7
BizTalk Server 2000
BizTalk Server 2002
BizTalk Server 2004
BizTalk Server 2006
Visual Studio 6.0
Access 2000
Access 2002
Access 2003
Access 2007
Access 97
Collaboration Data Objects 2.0
Commerce Server 2002
Content Management Server 2001
Commerce Server 2007
Content Management Server 2002
Data Access Components 2.7
Data Access Components 2.8
DirectX 9.0b
Office Small Business Accounting 2006
Accounting 2007
ActiveSync 4.1
Class Server 2.0
Groove 2007
Windows Vista
Outlook 2007
OneNote 2003
OneNote 2007
Office X for Mac
Zune software
Zune Live
Zoo Tycoon 2
Flight Simulator 2002
Dungeon Siege II

Cervo Technologies
The Right Source to Outsource

Oracle Database FAQS

Sharepoint Portal Server KB

Outlook 2007 Knowledge Base Articles

BizTalk Server 2004 Knowledge Base Articles

Changes to daylight saving time in 2007 for BizTalk Server 2004


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

If an orchestration has a delay shape that causes the orchestration to end after the 2:00 A.M. standard time 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 standard time 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 standard time 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 2004, follow the steps in the "Workaround" section.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
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 2004 Service Pack 2 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.

Uninstall information

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 nameFile versionFile sizeDateTime
Btsmessageagent.dll3.0.7417.0604,00820-Feb-200703:30
Microsoft.biztalk.interop.agent.dll3.0.7417.054,66420-Feb-200703:30
Microsoft.xlangs.biztalk.crossprocess.dll3.0.7417.083,35220-Feb-200703:30
Microsoft.xlangs.biztalk.engine.dll3.0.7417.0243,08020-Feb-200703:30
Microsoft.xlangs.biztalk.process.dll3.0.7417.071,05620-Feb-200703:30
Microsoft.xlangs.engine.dll3.0.7417.0243,06420-Feb-200703:30
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

STATUS

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

WORKAROUND

To manually resume service instances in BizTalk Server 2004, follow these steps:
1.Start Health and Activity Tracking.
2.Click Operations, and then click Service Instances.
3.In the Status box, click Suspended.
4.Click Run Query.
5.Right-click the suspended service instance that you want, and then click Resume.

Note You can resume any service instance that has a status of Suspended (resumable).

MORE INFORMATION

For more information about DST changes in Microsoft Windows operating systems, visit the following Microsoft Web site:
http://support.microsoft.com/gp/cp_dst (http://support.microsoft.com/gp/cp_dst)
For more information, click the following article number to view the article in the Microsoft Knowledge Base:


APPLIES TO
Microsoft BizTalk Server 2004 Standard Edition
Microsoft BizTalk Server 2004 Enterprise Edition
Microsoft BizTalk Server 2004 Developer Edition
Microsoft BizTalk Server 2004 Partner Edition

Keywords: 
kbbug kbpubtypekc kbhotfixserver kbqfe kbbts kbfix kbinfo KB931960

Copyright © 2004 - 2007 Gridview.org, Inc. All rights reserved. Powered by Smart Web Content Management System