Microsoft KB Archive/842258

= Daylight-savings time adjustment may cause unexpected problems in Microsoft Office Live Communications Server 2003 =

PSS ID Number: 842258

Article Last Modified on 5/24/2004

-

The information in this article applies to:


 * Microsoft Office Live Communications Server 2003

-





SYMPTOMS
During April 4, 2004 daylight-saving time implementation, you may experience the following unexpected problems:
 * All endpoints expire.
 * The subscriptions and endpoints may expire sooner or later than they should.
 * The presence fidelity is maintained, but the connection is lost when sending notifies.
 * The routing logic in the Routing.am application is affected because it is based on the LastSetPresence value on the endpoints.



CAUSE
These problems occur because the getdate functions used in the stored procedures do not take daylight-saving time into account. This affects all the logic that is based on getdate.



RESOLUTION
These problems resolve themselves over several hours. However, to resolve these problems immediately, and to prevent these problems the next time that the time changes, replace all instances of getdate function with the getutcdate function in your Microsoft SQL Server stored procedures. Then, update them by using the Dbsetup.wsf script.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
These problems occur during non-business hours (2:00 A.M. on Sunday, April 4). These problems resolve themselves over several hours and affect non-business hours (2:00 A.M. - 9:00 A.M. on Sunday).

Keywords: kbprb KB842258

Technology: kbOfficeLiveCommServ2003

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.