Re: 6.3 Patch 20 - Issues with years prior to 2007
http://www.jnbridge.com/blog/?p=23 > > "There's a very interesting problem with Microsoft's DST patch for Windows > that you should be aware of, since it can impact date conversion results > when mapped date proxies are used. The patch applies the new rules for > whether date and time are daylight savings time without regard to year. > This means that if you ask .NET whether a given DateTime in the past is DST, > it will apply the new rules even if the date would have been standard time > under the old rules." > > and > http://blogs.msdn.com/michkap/archive/2007/02/05/1606868.aspx > > "Apparently we were naïve, as now historic times are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: 6.3 Patch 20 - Issues with years prior to 2007
YES this is a known problem from Microsoft's Windows Update for DST. Naturally, I can't find the KB article at this time. However, the updates have been applied and the 1 hour time difference exists in years prior to 2007. When I look at my calendar from 2006 between the first week of March and a reoccuring meeting after the second week of March, the meetings are different by one hour. This is OK during the month of April (when the original DST) was applied. Clear as mud - right?!?! Nick Havin' Fun in Sacramento. On Thu, 22 Feb 2007 09:53:31 -0500, Lammey, Peter A. <[EMAIL PROTECTED]> wrote: >I didnt patch our client but we did patch our Mid Tier to 20 (our dev >Mid Tier not our prod Mid Tier box). >I just checked a ticket using our prod Mid Tier and dev Mid Tier and the >Create Date was the same for both. > >I am wondering if this is a Windows client issue since our Mid Tier is >on Linux and I dont experience the problem there. > > >Thanks >Peter Lammey >ESPN MIT Technical Services & Applications Management >860-766-4761 > > > > > >From: Action Request System discussion list(ARSList) >[mailto:[EMAIL PROTECTED] On Behalf Of David Sanders >Sent: Thursday, February 22, 2007 6:35 AM >To: arslist@ARSLIST.ORG >Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007 > > >** > >Hi Peter > > > >I am sure that applying the DST patches to your server does not alter >any historical data stored in your database. The issue is with how the >epoch time in secs is converted and displayed by the client. So, was >the client you were running this test through patched for DST changes?? > > > >Regards > > > >David Sanders > >Remedy Solution Architect > >Enterprise Service Suite @ Work > >== > >ARS List Award Winner 2005 > >Best 3rd party Remedy Application > > > >tel +44 1494 468980 > >mobile +44 7710 377761 > >email [EMAIL PROTECTED] > > > >web http://www.westoverconsulting.co.uk ><http://www.westoverconsulting.co.uk/> > > > >________________ > >From: Action Request System discussion list(ARSList) >[mailto:[EMAIL PROTECTED] On Behalf Of Lammey, Peter A. >Sent: Wednesday, February 21, 2007 9:41 PM >To: arslist@ARSLIST.ORG >Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007 > > > >I checked our ARS 6.3 development system which has been patched to 20 >and looked up some tickets that were a copies of what we have on our >production environment (which has not been patched yet). > >The Create dates on the tickets on our development and production were >the same. > >I also verified that the OS of our development server was patched. > > > >Our platforms are the following: > > > >AR Server - Windows 2003 > >Mid Tier - Linux Java 1.5.04 > > > > > >Thanks >Peter Lammey >ESPN MIT Technical Services & Applications Management >860-766-4761 > > > > > > > >From: Action Request System discussion list(ARSList) >[mailto:[EMAIL PROTECTED] On Behalf Of Eric Cleereman (IT) >Sent: Wednesday, February 21, 2007 4:07 PM >To: arslist@ARSLIST.ORG >Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007 > >** > >Peter, > > > >Tickets from March 12th - April 2nd 2006 and from October 29th - >November 5th of 2006 all seem to be off by an hour. All other tickets >outside of those ranges seem to be accurate. > > > >Frederick, > > > >Each of the patches you asked about was applied prior to the Remedy >patches being applied. > > > >Eric > > -Original Message- > From: Action Request System discussion list(ARSList) >[mailto:[EMAIL PROTECTED] Behalf Of Grooms, Frederick W > Sent: Wednesday, February 21, 2007 3:38 PM > To: arslist@ARSLIST.ORG > Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007 > > ** > > Just to check ... > > > > On the AIX box you have > > - The AIX DST patches applied > > - The updated Java > > - The ARS server patch > > > > On the Windows box you have > > - The Microsoft DST patches applied > > - The updated Java > > - The ARS Mid-Tier patch > > > > > > > > -Original Message- > From: Action Request System discussion list(ARSList) >[mailto:[EMAIL PROTECTED] Behalf Of Lammey, Peter A. > Sent: Wednesday, February 21, 2007 3:26 PM > To: arslist@ARSLIST.ORG > Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007 > > ** > > Does this mea
Re: 6.3 Patch 20 - Issues with years prior to 2007
I didnt patch our client but we did patch our Mid Tier to 20 (our dev
Mid Tier not our prod Mid Tier box).
I just checked a ticket using our prod Mid Tier and dev Mid Tier and the
Create Date was the same for both.
I am wondering if this is a Windows client issue since our Mid Tier is
on Linux and I dont experience the problem there.
Thanks
Peter Lammey
ESPN MIT Technical Services & Applications Management
860-766-4761
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of David Sanders
Sent: Thursday, February 22, 2007 6:35 AM
To: arslist@ARSLIST.ORG
Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007
**
Hi Peter
I am sure that applying the DST patches to your server does not alter
any historical data stored in your database. The issue is with how the
epoch time in secs is converted and displayed by the client. So, was
the client you were running this test through patched for DST changes??
Regards
David Sanders
Remedy Solution Architect
Enterprise Service Suite @ Work
==
ARS List Award Winner 2005
Best 3rd party Remedy Application
tel +44 1494 468980
mobile +44 7710 377761
email [EMAIL PROTECTED]
web http://www.westoverconsulting.co.uk
<http://www.westoverconsulting.co.uk/>
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Lammey, Peter A.
Sent: Wednesday, February 21, 2007 9:41 PM
To: arslist@ARSLIST.ORG
Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007
I checked our ARS 6.3 development system which has been patched to 20
and looked up some tickets that were a copies of what we have on our
production environment (which has not been patched yet).
The Create dates on the tickets on our development and production were
the same.
I also verified that the OS of our development server was patched.
Our platforms are the following:
AR Server - Windows 2003
Mid Tier - Linux Java 1.5.04
Thanks
Peter Lammey
ESPN MIT Technical Services & Applications Management
860-766-4761
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Eric Cleereman (IT)
Sent: Wednesday, February 21, 2007 4:07 PM
To: arslist@ARSLIST.ORG
Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007
**
Peter,
Tickets from March 12th - April 2nd 2006 and from October 29th -
November 5th of 2006 all seem to be off by an hour. All other tickets
outside of those ranges seem to be accurate.
Frederick,
Each of the patches you asked about was applied prior to the Remedy
patches being applied.
Eric
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Grooms, Frederick W
Sent: Wednesday, February 21, 2007 3:38 PM
To: arslist@ARSLIST.ORG
Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007
**
Just to check ...
On the AIX box you have
- The AIX DST patches applied
- The updated Java
- The ARS server patch
On the Windows box you have
- The Microsoft DST patches applied
- The updated Java
- The ARS Mid-Tier patch
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Lammey, Peter A.
Sent: Wednesday, February 21, 2007 3:26 PM
To: arslist@ARSLIST.ORG
Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007
**
Does this mean that for your saved tickets that were created
between March 11th 2006 and April 2nd 2006 that the Create Time for the
tickets are now off by one hour after you installed Patch 20?
Thanks
Peter Lammey
ESPN MIT Technical Services & Applications Management
860-766-4761
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Eric Cleereman (IT)
Sent: Wednesday, February 21, 2007 3:17 PM
To: arslist@ARSLIST.ORG
Subject: 6.3 Patch 20 - Issues with years prior to 2007
**
Hi All,
I'm running version 6.3 of ARServer under Oracle 9 on AIX, and
version 6.3 of Mid-Tier on Windows 2000 in my development environment.
I've just installed Patch 20 for both, and am in the process of doing
some preliminary testing.
Remedy seems to be applying the revised schedule for 2007 for
earlier years as well. For example, it seems to be seeing March 20th
2007 as Eastern Daylight Time (EDT), which is correct. But it seems to
see March 20th 2006 as EDT as well. In 2006 EDT did not go into e
Re: 6.3 Patch 20 - Issues with years prior to 2007
Hi Peter I am sure that applying the DST patches to your server does not alter any historical data stored in your database. The issue is with how the epoch time in secs is converted and displayed by the client. So, was the client you were running this test through patched for DST changes?? Regards David Sanders Remedy Solution Architect Enterprise Service Suite @ Work == ARS List Award Winner 2005 Best 3rd party Remedy Application tel +44 1494 468980 mobile +44 7710 377761 email [EMAIL PROTECTED] web http://www.westoverconsulting.co.uk <http://www.westoverconsulting.co.uk/> _ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Lammey, Peter A. Sent: Wednesday, February 21, 2007 9:41 PM To: arslist@ARSLIST.ORG Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007 I checked our ARS 6.3 development system which has been patched to 20 and looked up some tickets that were a copies of what we have on our production environment (which has not been patched yet). The Create dates on the tickets on our development and production were the same. I also verified that the OS of our development server was patched. Our platforms are the following: AR Server - Windows 2003 Mid Tier - Linux Java 1.5.04 Thanks Peter Lammey ESPN MIT Technical Services & Applications Management 860-766-4761 _ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Eric Cleereman (IT) Sent: Wednesday, February 21, 2007 4:07 PM To: arslist@ARSLIST.ORG Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007 ** Peter, Tickets from March 12th - April 2nd 2006 and from October 29th - November 5th of 2006 all seem to be off by an hour. All other tickets outside of those ranges seem to be accurate. Frederick, Each of the patches you asked about was applied prior to the Remedy patches being applied. Eric -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Grooms, Frederick W Sent: Wednesday, February 21, 2007 3:38 PM To: arslist@ARSLIST.ORG Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007 ** Just to check ... On the AIX box you have - The AIX DST patches applied - The updated Java - The ARS server patch On the Windows box you have - The Microsoft DST patches applied - The updated Java - The ARS Mid-Tier patch -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Lammey, Peter A. Sent: Wednesday, February 21, 2007 3:26 PM To: arslist@ARSLIST.ORG Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007 ** Does this mean that for your saved tickets that were created between March 11th 2006 and April 2nd 2006 that the Create Time for the tickets are now off by one hour after you installed Patch 20? Thanks Peter Lammey ESPN MIT Technical Services & Applications Management 860-766-4761 _ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Eric Cleereman (IT) Sent: Wednesday, February 21, 2007 3:17 PM To: arslist@ARSLIST.ORG Subject: 6.3 Patch 20 - Issues with years prior to 2007 ** Hi All, I'm running version 6.3 of ARServer under Oracle 9 on AIX, and version 6.3 of Mid-Tier on Windows 2000 in my development environment. I've just installed Patch 20 for both, and am in the process of doing some preliminary testing. Remedy seems to be applying the revised schedule for 2007 for earlier years as well. For example, it seems to be seeing March 20th 2007 as Eastern Daylight Time (EDT), which is correct. But it seems to see March 20th 2006 as EDT as well. In 2006 EDT did not go into effect until April 2nd, so it should see that date as Eastern Standard Time (EDT). This is an issue for us, as we do a lot of historical reporting. Has anyone else running 6.3 Patch 20 (or 7.1 Patch 1) noticed any problems with Daylight Saving time calculations for 2006 or prior years? Eric Cleereman __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: 6.3 Patch 20 - Issues with years prior to 2007
But you can't migrate to a non-MS OS and use Remedy. That is the only OS that supports the Remedy clients (user, alert, admin). Good news is that MS's black Tuesday falls on the 8th, giving you several days to address the issue, assuming a patch is relesed. Sorry, couldn't resist. Axton On 2/21/07, Eric Cleereman (IT) <[EMAIL PROTECTED]> wrote: ** David, Thank you for pointing me in the right direction. This does seem to happen with other (non-Remedy) apps as well. So at this point, it seems we have the following options: 1) Live with it until MS or a third party offers a solution 2) Utilize Windows Vista as an enterprise server (tongue very much in cheek) 3) Migrate to a non Microsoft OS 4) Live with it indefinitely Option 1 doesn't look promising, as it appears that Microsoft is side stepping ownership of this. Here's an excerpt from http://msdn2.microsoft.com/en-us/vstudio/bb264729.aspx: Applications that deal with historical time zone data may also need to be updated. Microsoft advises all developers who make use of time zone data to test their applications against this update to ensure that their applications function correctly. We'll evaluate options 3 and 4. Thanks again. Eric -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Easter, David Sent: Wednesday, February 21, 2007 3:56 PM To: arslist@ARSLIST.ORG Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007 ** Also, please check if other applications are behaving in this manner. Hopefully this will not sound like I'm pointing fingers, but I have seen several comments within Microsoft blogs that indicate that the DST patch for Windows encounters this issue - namely that the DST "fix" is not year dependant, so that data from previous years picks up the DST schedule for 2007. See: http://www.jnbridge.com/blog/?p=23 "There's a very interesting problem with Microsoft's DST patch for Windows that you should be aware of, since it can impact date conversion results when mapped date proxies are used. The patch applies the new rules for whether date and time are daylight savings time without regard to year. This means that if you ask .NET whether a given DateTime in the past is DST, it will apply the new rules even if the date would have been standard time under the old rules." and http://blogs.msdn.com/michkap/archive/2007/02/05/1606868.aspx "Apparently we were naïve, as now historic times are calculated incorrectly due to Windows inability to calculate the correct DST times from previous years, including 2006! You can try it for yourself, by changing the system clock to March 13th 2006 on a Windows XP machine (or 2000 machine with manual registry patch as suggested in KB914387). Vista gets it right, but as that represents < 0.1% of our install base it's not much consolation at the moment." Again, I'm not saying that this is the case, but it's something to test for - namely whether the issue you are seeing was caused by the AR System patch or happened when you loaded the OS and/or Java patches. Since AR System in general uses the Operating System for DST information except for the Mid-Tier, web services and import/export; DST 2007 issues seen in other parts of AR System are potentially linked to the DST changes in the Operating System itself. Thanks, -David J. Easter Sr. Product Manager, Service Management Business Unit BMC Software, Inc. From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Grooms, Frederick W Sent: Wednesday, February 21, 2007 12:38 PM To: arslist@ARSLIST.ORG Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007 ** Just to check ... On the AIX box you have - The AIX DST patches applied - The updated Java - The ARS server patch On the Windows box you have - The Microsoft DST patches applied - The updated Java - The ARS Mid-Tier patch From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Eric Cleereman (IT) Sent: Wednesday, February 21, 2007 2:17 PM To: arslist@ARSLIST.ORG Subject: 6.3 Patch 20 - Issues with years prior to 2007 ** Hi All, I'm running version 6.3 of ARServer under Oracle 9 on AIX, and version 6.3 of Mid-Tier on Windows 2000 in my development environment. I've just installed Patch 20 for both, and am in the process of doing some preliminary testing. Remedy seems to be applying the revised schedule for 2007 for earlier years as well. For example, it seems to be seeing March 20th 2007 as Eastern Daylight Time (EDT), which is correct. But it seems to see March 20th 2006 as EDT as well. In 2006 EDT did not go into effect until April 2nd, so it should see that date as Eastern Standard Time (EDT). This is an issue for us, as we do a
Re: 6.3 Patch 20 - Issues with years prior to 2007
6.3 Patch 20 - Issues with years prior to 2007Eric,
If you are using SQL server, the attached SQL script may help to resolve some
of the issues with historical reporting.
It will create a function to convert epoch time values to local datetime, using
the "old" rules for dates prior to 2007 (DST ranges from 1st Sunday in April to
Last Sunday in October) and the "new" rules for dates after 2007 (DST ranges
from 2nd Sunday in March to 1st Sunday in November).
The function was written for the U.S. Central time zone, using a 5 hour (18,000
second) offset from GMT during DST, and a 6-hour (21,600 second) offset during
standard time. For other U.S. time zones, simply modify the offset seconds
values in the last section of the script.
HTH,
Thomas
- Original Message -
From: Eric Cleereman (IT)
Newsgroups: gmane.comp.crm.arsystem.general
To: arslist@ARSLIST.ORG
Sent: Wednesday, February 21, 2007 15:06
Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007
**
Peter,
Tickets from March 12th - April 2nd 2006 and from October 29th - November 5th
of 2006 all seem to be off by an hour. All other tickets outside of those
ranges seem to be accurate.
Frederick,
Each of the patches you asked about was applied prior to the Remedy patches
being applied.
Eric
-Original Message-
From: Action Request System discussion list(ARSList) [mailto:[EMAIL
PROTECTED] Behalf Of Grooms, Frederick W
Sent: Wednesday, February 21, 2007 3:38 PM
To: arslist@ARSLIST.ORG
Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007
**
Just to check ...
On the AIX box you have
- The AIX DST patches applied
- The updated Java
- The ARS server patch
On the Windows box you have
- The Microsoft DST patches applied
- The updated Java
- The ARS Mid-Tier patch
-Original Message-
From: Action Request System discussion list(ARSList) [mailto:[EMAIL
PROTECTED] Behalf Of Lammey, Peter A.
Sent: Wednesday, February 21, 2007 3:26 PM
To: arslist@ARSLIST.ORG
Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007
**
Does this mean that for your saved tickets that were created between March
11th 2006 and April 2nd 2006 that the Create Time for the tickets are now off
by one hour after you installed Patch 20?
Thanks
Peter Lammey
ESPN MIT Technical Services & Applications Management
860-766-4761
From: Action Request System discussion list(ARSList) [mailto:[EMAIL
PROTECTED] On Behalf Of Eric Cleereman (IT)
Sent: Wednesday, February 21, 2007 3:17 PM
To: arslist@ARSLIST.ORG
Subject: 6.3 Patch 20 - Issues with years prior to 2007
**
Hi All,
I'm running version 6.3 of ARServer under Oracle 9 on AIX, and version 6.3
of Mid-Tier on Windows 2000 in my development environment. I've just installed
Patch 20 for both, and am in the process of doing some preliminary testing.
Remedy seems to be applying the revised schedule for 2007 for earlier years
as well. For example, it seems to be seeing March 20th 2007 as Eastern
Daylight Time (EDT), which is correct. But it seems to see March 20th 2006 as
EDT as well. In 2006 EDT did not go into effect until April 2nd, so it should
see that date as Eastern Standard Time (EDT).
This is an issue for us, as we do a lot of historical reporting.
Has anyone else running 6.3 Patch 20 (or 7.1 Patch 1) noticed any problems
with Daylight Saving time calculations for 2006 or prior years?
Eric Cleereman
__20060125___This posting was submitted with HTML in it___
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
convert_epoch_to_date.sql
Description: Binary data
Re: 6.3 Patch 20 - Issues with years prior to 2007
I checked our ARS 6.3 development system which has been patched to 20 and looked up some tickets that were a copies of what we have on our production environment (which has not been patched yet). The Create dates on the tickets on our development and production were the same. I also verified that the OS of our development server was patched. Our platforms are the following: AR Server - Windows 2003 Mid Tier - Linux Java 1.5.04 Thanks Peter Lammey ESPN MIT Technical Services & Applications Management 860-766-4761 From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Eric Cleereman (IT) Sent: Wednesday, February 21, 2007 4:07 PM To: arslist@ARSLIST.ORG Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007 ** Peter, Tickets from March 12th - April 2nd 2006 and from October 29th - November 5th of 2006 all seem to be off by an hour. All other tickets outside of those ranges seem to be accurate. Frederick, Each of the patches you asked about was applied prior to the Remedy patches being applied. Eric -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Grooms, Frederick W Sent: Wednesday, February 21, 2007 3:38 PM To: arslist@ARSLIST.ORG Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007 ** Just to check ... On the AIX box you have - The AIX DST patches applied - The updated Java - The ARS server patch On the Windows box you have - The Microsoft DST patches applied - The updated Java - The ARS Mid-Tier patch -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Lammey, Peter A. Sent: Wednesday, February 21, 2007 3:26 PM To: arslist@ARSLIST.ORG Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007 ** Does this mean that for your saved tickets that were created between March 11th 2006 and April 2nd 2006 that the Create Time for the tickets are now off by one hour after you installed Patch 20? Thanks Peter Lammey ESPN MIT Technical Services & Applications Management 860-766-4761 From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Eric Cleereman (IT) Sent: Wednesday, February 21, 2007 3:17 PM To: arslist@ARSLIST.ORG Subject: 6.3 Patch 20 - Issues with years prior to 2007 ** Hi All, I'm running version 6.3 of ARServer under Oracle 9 on AIX, and version 6.3 of Mid-Tier on Windows 2000 in my development environment. I've just installed Patch 20 for both, and am in the process of doing some preliminary testing. Remedy seems to be applying the revised schedule for 2007 for earlier years as well. For example, it seems to be seeing March 20th 2007 as Eastern Daylight Time (EDT), which is correct. But it seems to see March 20th 2006 as EDT as well. In 2006 EDT did not go into effect until April 2nd, so it should see that date as Eastern Standard Time (EDT). This is an issue for us, as we do a lot of historical reporting. Has anyone else running 6.3 Patch 20 (or 7.1 Patch 1) noticed any problems with Daylight Saving time calculations for 2006 or prior years? Eric Cleereman __20060125___This posting was submitted with HTML in it___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: 6.3 Patch 20 - Issues with years prior to 2007
David, Thank you for pointing me in the right direction. This does seem to happen with other (non-Remedy) apps as well. So at this point, it seems we have the following options: 1) Live with it until MS or a third party offers a solution 2) Utilize Windows Vista as an enterprise server (tongue very much in cheek) 3) Migrate to a non Microsoft OS 4) Live with it indefinitely Option 1 doesn't look promising, as it appears that Microsoft is side stepping ownership of this. Here's an excerpt from <http://msdn2.microsoft.com/en-us/vstudio/bb264729.aspx> http://msdn2.microsoft.com/en-us/vstudio/bb264729.aspx: Applications that deal with historical time zone data may also need to be updated. Microsoft advises all developers who make use of time zone data to test their applications against this update to ensure that their applications function correctly. We'll evaluate options 3 and 4. Thanks again. Eric -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Easter, David Sent: Wednesday, February 21, 2007 3:56 PM To: arslist@ARSLIST.ORG Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007 ** Also, please check if other applications are behaving in this manner. Hopefully this will not sound like I'm pointing fingers, but I have seen several comments within Microsoft blogs that indicate that the DST patch for Windows encounters this issue - namely that the DST "fix" is not year dependant, so that data from previous years picks up the DST schedule for 2007. See: http://www.jnbridge.com/blog/?p=23 "There's a very interesting problem with Microsoft's DST patch for Windows that you should be aware of, since it can impact date conversion results when mapped date proxies are used. The patch applies the new rules for whether date and time are daylight savings time without regard to year. This means that if you ask .NET whether a given DateTime in the past is DST, it will apply the new rules even if the date would have been standard time under the old rules." and http://blogs.msdn.com/michkap/archive/2007/02/05/1606868.aspx "Apparently we were naïve, as now historic times are calculated incorrectly due to Windows inability to calculate the correct DST times from previous years, including 2006! You can try it for yourself, by changing the system clock to March 13th 2006 on a Windows XP machine (or 2000 machine with manual registry patch as suggested in KB914387). Vista gets it right, but as that represents < 0.1% of our install base it's not much consolation at the moment." Again, I'm not saying that this is the case, but it's something to test for - namely whether the issue you are seeing was caused by the AR System patch or happened when you loaded the OS and/or Java patches. Since AR System in general uses the Operating System for DST information except for the Mid-Tier, web services and import/export; DST 2007 issues seen in other parts of AR System are potentially linked to the DST changes in the Operating System itself. Thanks, -David J. Easter Sr. Product Manager, Service Management Business Unit BMC Software, Inc. _ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Grooms, Frederick W Sent: Wednesday, February 21, 2007 12:38 PM To: arslist@ARSLIST.ORG Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007 ** Just to check ... On the AIX box you have - The AIX DST patches applied - The updated Java - The ARS server patch On the Windows box you have - The Microsoft DST patches applied - The updated Java - The ARS Mid-Tier patch _ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Eric Cleereman (IT) Sent: Wednesday, February 21, 2007 2:17 PM To: arslist@ARSLIST.ORG Subject: 6.3 Patch 20 - Issues with years prior to 2007 ** Hi All, I'm running version 6.3 of ARServer under Oracle 9 on AIX, and version 6.3 of Mid-Tier on Windows 2000 in my development environment. I've just installed Patch 20 for both, and am in the process of doing some preliminary testing. Remedy seems to be applying the revised schedule for 2007 for earlier years as well. For example, it seems to be seeing March 20th 2007 as Eastern Daylight Time (EDT), which is correct. But it seems to see March 20th 2006 as EDT as well. In 2006 EDT did not go into effect until April 2nd, so it should see that date as Eastern Standard Time (EDT). This is an issue for us, as we do a lot of historical reporting. Has anyone else running 6.3 Patch 20 (or 7.1 Patch 1) noticed any problems with Daylight Saving time calculations for 2006 or prior years? Eric Cleereman __20060125___This posting was submitted with HTML in it___ __20060125_
Re: 6.3 Patch 20 - Issues with years prior to 2007
Peter, Tickets from March 12th - April 2nd 2006 and from October 29th - November 5th of 2006 all seem to be off by an hour. All other tickets outside of those ranges seem to be accurate. Frederick, Each of the patches you asked about was applied prior to the Remedy patches being applied. Eric -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Grooms, Frederick W Sent: Wednesday, February 21, 2007 3:38 PM To: arslist@ARSLIST.ORG Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007 ** Just to check ... On the AIX box you have - The AIX DST patches applied - The updated Java - The ARS server patch On the Windows box you have - The Microsoft DST patches applied - The updated Java - The ARS Mid-Tier patch -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Lammey, Peter A. Sent: Wednesday, February 21, 2007 3:26 PM To: arslist@ARSLIST.ORG Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007 ** Does this mean that for your saved tickets that were created between March 11th 2006 and April 2nd 2006 that the Create Time for the tickets are now off by one hour after you installed Patch 20? Thanks Peter Lammey ESPN MIT Technical Services & Applications Management 860-766-4761 _ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Eric Cleereman (IT) Sent: Wednesday, February 21, 2007 3:17 PM To: arslist@ARSLIST.ORG Subject: 6.3 Patch 20 - Issues with years prior to 2007 ** Hi All, I'm running version 6.3 of ARServer under Oracle 9 on AIX, and version 6.3 of Mid-Tier on Windows 2000 in my development environment. I've just installed Patch 20 for both, and am in the process of doing some preliminary testing. Remedy seems to be applying the revised schedule for 2007 for earlier years as well. For example, it seems to be seeing March 20th 2007 as Eastern Daylight Time (EDT), which is correct. But it seems to see March 20th 2006 as EDT as well. In 2006 EDT did not go into effect until April 2nd, so it should see that date as Eastern Standard Time (EDT). This is an issue for us, as we do a lot of historical reporting. Has anyone else running 6.3 Patch 20 (or 7.1 Patch 1) noticed any problems with Daylight Saving time calculations for 2006 or prior years? Eric Cleereman ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: 6.3 Patch 20 - Issues with years prior to 2007
I think you will find that this is because the XP Operating System patch (which was supposed to be year aware to not cause this to happen) is not year aware. You will find that any Calendar items, emails, etc... all have dates that are off by an hour for previous years. At least that's what I have seen here. -Scott Remedy Systems Architect Business Systems Phone : (519) 888-7465 ext. 5750 Cell : (519) 498-4996 Fax : (519) 888-7884 [EMAIL PROTECTED] "The single biggest problem in communication is the illusion that it has taken place." From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Lammey, Peter A. Sent: Wednesday, February 21, 2007 3:26 PM To: arslist@ARSLIST.ORG Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007 Does this mean that for your saved tickets that were created between March 11th 2006 and April 2nd 2006 that the Create Time for the tickets are now off by one hour after you installed Patch 20? Thanks Peter Lammey ESPN MIT Technical Services & Applications Management 860-766-4761 From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Eric Cleereman (IT) Sent: Wednesday, February 21, 2007 3:17 PM To: arslist@ARSLIST.ORG Subject: 6.3 Patch 20 - Issues with years prior to 2007 ** Hi All, I'm running version 6.3 of ARServer under Oracle 9 on AIX, and version 6.3 of Mid-Tier on Windows 2000 in my development environment. I've just installed Patch 20 for both, and am in the process of doing some preliminary testing. Remedy seems to be applying the revised schedule for 2007 for earlier years as well. For example, it seems to be seeing March 20th 2007 as Eastern Daylight Time (EDT), which is correct. But it seems to see March 20th 2006 as EDT as well. In 2006 EDT did not go into effect until April 2nd, so it should see that date as Eastern Standard Time (EDT). This is an issue for us, as we do a lot of historical reporting. Has anyone else running 6.3 Patch 20 (or 7.1 Patch 1) noticed any problems with Daylight Saving time calculations for 2006 or prior years? Eric Cleereman __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___ - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: 6.3 Patch 20 - Issues with years prior to 2007
Also, please check if other applications are behaving in this manner. Hopefully this will not sound like I'm pointing fingers, but I have seen several comments within Microsoft blogs that indicate that the DST patch for Windows encounters this issue - namely that the DST "fix" is not year dependant, so that data from previous years picks up the DST schedule for 2007. See: http://www.jnbridge.com/blog/?p=23 "There's a very interesting problem with Microsoft's DST patch for Windows that you should be aware of, since it can impact date conversion results when mapped date proxies are used. The patch applies the new rules for whether date and time are daylight savings time without regard to year. This means that if you ask .NET whether a given DateTime in the past is DST, it will apply the new rules even if the date would have been standard time under the old rules." and http://blogs.msdn.com/michkap/archive/2007/02/05/1606868.aspx "Apparently we were naïve, as now historic times are calculated incorrectly due to Windows inability to calculate the correct DST times from previous years, including 2006! You can try it for yourself, by changing the system clock to March 13th 2006 on a Windows XP machine (or 2000 machine with manual registry patch as suggested in KB914387). Vista gets it right, but as that represents < 0.1% of our install base it's not much consolation at the moment." Again, I'm not saying that this is the case, but it's something to test for - namely whether the issue you are seeing was caused by the AR System patch or happened when you loaded the OS and/or Java patches. Since AR System in general uses the Operating System for DST information except for the Mid-Tier, web services and import/export; DST 2007 issues seen in other parts of AR System are potentially linked to the DST changes in the Operating System itself. Thanks, -David J. Easter Sr. Product Manager, Service Management Business Unit BMC Software, Inc. From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Grooms, Frederick W Sent: Wednesday, February 21, 2007 12:38 PM To: arslist@ARSLIST.ORG Subject: Re: 6.3 Patch 20 - Issues with years prior to 2007 ** Just to check ... On the AIX box you have - The AIX DST patches applied - The updated Java - The ARS server patch On the Windows box you have - The Microsoft DST patches applied - The updated Java - The ARS Mid-Tier patch From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Eric Cleereman (IT) Sent: Wednesday, February 21, 2007 2:17 PM To: arslist@ARSLIST.ORG Subject: 6.3 Patch 20 - Issues with years prior to 2007 ** Hi All, I'm running version 6.3 of ARServer under Oracle 9 on AIX, and version 6.3 of Mid-Tier on Windows 2000 in my development environment. I've just installed Patch 20 for both, and am in the process of doing some preliminary testing. Remedy seems to be applying the revised schedule for 2007 for earlier years as well. For example, it seems to be seeing March 20th 2007 as Eastern Daylight Time (EDT), which is correct. But it seems to see March 20th 2006 as EDT as well. In 2006 EDT did not go into effect until April 2nd, so it should see that date as Eastern Standard Time (EDT). This is an issue for us, as we do a lot of historical reporting. Has anyone else running 6.3 Patch 20 (or 7.1 Patch 1) noticed any problems with Daylight Saving time calculations for 2006 or prior years? Eric Cleereman __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: 6.3 Patch 20 - Issues with years prior to 2007
You know, it seems with all the problems with how DST is administered around the world, and the difficulty companies have in dealing with it, that a very low-tech answer may be more appropriate for 95% of the shops. 1) Don't worry about the DST-specific patches, which will always be problematic, due to the complexity of the problem. 2) Don't schedule escalations or allow client/server activity to occur during the hour (0200 - 0300) affected by DST changes. 3) If you can't avoid that, take the server down for "maintenance" during that hour. I know it seems like a cop-out, and in some shops that have 24 x 7 uptime requirements it may not be an option, but sometimes walking around a wall is preferable to trying to break it down. Rick _ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Eric Cleereman (IT) Sent: Wednesday, February 21, 2007 12:17 PM To: arslist@ARSLIST.ORG Subject: 6.3 Patch 20 - Issues with years prior to 2007 ** Hi All, I'm running version 6.3 of ARServer under Oracle 9 on AIX, and version 6.3 of Mid-Tier on Windows 2000 in my development environment. I've just installed Patch 20 for both, and am in the process of doing some preliminary testing. Remedy seems to be applying the revised schedule for 2007 for earlier years as well. For example, it seems to be seeing March 20th 2007 as Eastern Daylight Time (EDT), which is correct. But it seems to see March 20th 2006 as EDT as well. In 2006 EDT did not go into effect until April 2nd, so it should see that date as Eastern Standard Time (EDT). This is an issue for us, as we do a lot of historical reporting. Has anyone else running 6.3 Patch 20 (or 7.1 Patch 1) noticed any problems with Daylight Saving time calculations for 2006 or prior years? Eric Cleereman __20060125___This posting was submitted with HTML in it___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: 6.3 Patch 20 - Issues with years prior to 2007
Just to check ... On the AIX box you have - The AIX DST patches applied - The updated Java - The ARS server patch On the Windows box you have - The Microsoft DST patches applied - The updated Java - The ARS Mid-Tier patch From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Eric Cleereman (IT) Sent: Wednesday, February 21, 2007 2:17 PM To: arslist@ARSLIST.ORG Subject: 6.3 Patch 20 - Issues with years prior to 2007 ** Hi All, I'm running version 6.3 of ARServer under Oracle 9 on AIX, and version 6.3 of Mid-Tier on Windows 2000 in my development environment. I've just installed Patch 20 for both, and am in the process of doing some preliminary testing. Remedy seems to be applying the revised schedule for 2007 for earlier years as well. For example, it seems to be seeing March 20th 2007 as Eastern Daylight Time (EDT), which is correct. But it seems to see March 20th 2006 as EDT as well. In 2006 EDT did not go into effect until April 2nd, so it should see that date as Eastern Standard Time (EDT). This is an issue for us, as we do a lot of historical reporting. Has anyone else running 6.3 Patch 20 (or 7.1 Patch 1) noticed any problems with Daylight Saving time calculations for 2006 or prior years? Eric Cleereman __20060125___This posting was submitted with HTML in it___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: 6.3 Patch 20 - Issues with years prior to 2007
Does this mean that for your saved tickets that were created between March 11th 2006 and April 2nd 2006 that the Create Time for the tickets are now off by one hour after you installed Patch 20? Thanks Peter Lammey ESPN MIT Technical Services & Applications Management 860-766-4761 From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Eric Cleereman (IT) Sent: Wednesday, February 21, 2007 3:17 PM To: arslist@ARSLIST.ORG Subject: 6.3 Patch 20 - Issues with years prior to 2007 ** Hi All, I'm running version 6.3 of ARServer under Oracle 9 on AIX, and version 6.3 of Mid-Tier on Windows 2000 in my development environment. I've just installed Patch 20 for both, and am in the process of doing some preliminary testing. Remedy seems to be applying the revised schedule for 2007 for earlier years as well. For example, it seems to be seeing March 20th 2007 as Eastern Daylight Time (EDT), which is correct. But it seems to see March 20th 2006 as EDT as well. In 2006 EDT did not go into effect until April 2nd, so it should see that date as Eastern Standard Time (EDT). This is an issue for us, as we do a lot of historical reporting. Has anyone else running 6.3 Patch 20 (or 7.1 Patch 1) noticed any problems with Daylight Saving time calculations for 2006 or prior years? Eric Cleereman __20060125___This posting was submitted with HTML in it___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
6.3 Patch 20 - Issues with years prior to 2007
Hi All, I'm running version 6.3 of ARServer under Oracle 9 on AIX, and version 6.3 of Mid-Tier on Windows 2000 in my development environment. I've just installed Patch 20 for both, and am in the process of doing some preliminary testing. Remedy seems to be applying the revised schedule for 2007 for earlier years as well. For example, it seems to be seeing March 20th 2007 as Eastern Daylight Time (EDT), which is correct. But it seems to see March 20th 2006 as EDT as well. In 2006 EDT did not go into effect until April 2nd, so it should see that date as Eastern Standard Time (EDT). This is an issue for us, as we do a lot of historical reporting. Has anyone else running 6.3 Patch 20 (or 7.1 Patch 1) noticed any problems with Daylight Saving time calculations for 2006 or prior years? Eric Cleereman ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
