E72 Celandar- Daylight saving bug in US version

I have a major issue with repeating events and a potential DST conflict on the calendar
The US went into Daylight savings mode last week. After that switch, all my repeating events seem to have moved forward 2+ hours.
For example, I have a repeating event created for 11:30am-1:20pm on Mondays, now that entry shows 1:30-3:20pm for every Monday.
Non repeating events seem to be fine. An appointment set for 4m the day after the switch to Daylight Time, is displaying correctly - it is the repeating events that are messed up.
Repeating events on the days before the switch are still showing the correct time.
Anyone else have this issue?

The only solution I found was to delete and reenter the repeating events. That seems to have fixed the problem atleast for the moment.
I don't know how to disable Daylight Savings - maybe by changing the clock setting(s) so that its no longer updated by your operator?

Similar Messages

  • BO-XI R2 daylight saving time

    The time in infoview has not changed to accommodate the daylight saving time change.
    Version:  11.5.8.8265
    Tried to install xir2 edst patch (CHF15_DST), when doing so I get a message stating "MHF1 is needed as prerequisite"...when I try to install MHF1, receive message "No supported XIR2 products detected"
    Please advice, thank you.

    Symptom
    The Integration Kit for Baan driver displays incorrect time data in reports. The time is off by an hour between the dates marking the old Daylight Saving Time (DST) and the new DST change.
    Cause
    DST has been changed to occur earlier in the year. The Integration Kit for Baan does not pick the new settings up.
    Resolution
    There are files called ZONEFILES on the BAAN Server. These files must be already updated on the Baan server side.
    The Integration Kit for Baan installs our own version of these files in the following folder:
    \Baan\Native\lib\ZONEINFO
    on the hard drive where the Integration Kit is installed.
    Back up these files on the Crystal Reports/Business Objects XI computer, then put a copy of the ZONEFILES from the Baan Server to the computer where the Integration Kit for Baan is installed.

  • Conversion mapping is losing time zone data during daylight saving time

    We have a problem with conversion of Calendars to timestamp with timezone for the last hour of Daylight Saving Time (e.g. 01:00 EDT - 01:59 EDT) where it is being interpreted as Standard Time which is in reality 60 minutes later.
    We've written a JUnit test case that runs directly against TopLink to avoid any issues with WAS and its connection pooling.
    The Calendar theDateTime comes from an object called TimeEntry which is mapped to a TIMESTAMP WITH TIMEZONE field using conversion mapping with Data Type TIMESTAMPTZ (oracle.sql) and Attribute Type Calendar (java.util).
    We are using:
    Oracle TopLink - 10g Release 3 (10.1.3.0.0) (Build Patch for Bugs 5145690 and 5156075)
    Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production
    Oracle JDBC driver Version: 10.2.0.1.0
    platform=>Oracle9Platform
    Execute this Java:
    SimpleDateFormat format = new SimpleDateFormat("MM/dd/yyyy HH:mm z");
    TimeZone tzEasternRegion = TimeZone.getTimeZone("US/Eastern");
    Calendar theDateTime = Calendar.getInstance(tzEasternRegion);
    theDateTime.setTime(format.parse("10/29/2006 01:00 EDT"));
    Persist to the database and execute this SQL:
    SELECT the_date_time, EXTRACT(TIMEZONE_REGION FROM the_date_time), EXTRACT(TIMEZONE_ABBR FROM the_date_time), EXTRACT(TIMEZONE_HOUR FROM the_date_time)
    FROM time_table WHERE time_table_id=1
    This provides the following results:
    THE_DATE_TIME EXTRACT(TIMEZONE_REGION FROM the_date_time) EXTRACT(TIMEZONE_ABBR FROM the_date_time) EXTRACT(TIMEZONE_HOUR FROM the_date_time)
    29-OCT-06 01.00.00.000000 AM US/EASTERN US/Eastern EST -5
    The wrong time zone is in the database. It should be EDT -4. Let's test the SQL that should be generated by TopLink. It should look like the following.
    Execute this SQL:
    UPDATE time_table SET the_date_time = TO_TIMESTAMP_TZ('10/29/2006 01:00 US/Eastern','mm/dd/yyyy HH24:MI TZR') WHERE (time_table_id=1)
    SELECT the_date_time, EXTRACT(TIMEZONE_REGION FROM the_date_time), EXTRACT(TIMEZONE_ABBR FROM the_date_time), EXTRACT(TIMEZONE_HOUR FROM the_date_time)
    FROM time_table WHERE time_table_id=1
    This provides the same results:
    THE_DATE_TIME EXTRACT(TIMEZONE_REGION FROM the_date_time) EXTRACT(TIMEZONE_ABBR FROM the_date_time) EXTRACT(TIMEZONE_HOUR FROM the_date_time)
    29-OCT-06 01.00.00.000000 AM US/EASTERN US/Eastern EST -5
    Now, execute this SQL:
    UPDATE time_table SET the_date_time = TO_TIMESTAMP_TZ('10/29/2006 01:00 EDT US/Eastern','mm/dd/yyyy HH24:MI TZD TZR') WHERE (time_table_id=1)
    SELECT the_date_time, EXTRACT(TIMEZONE_REGION FROM the_date_time), EXTRACT(TIMEZONE_ABBR FROM the_date_time), EXTRACT(TIMEZONE_HOUR FROM the_date_time)
    FROM time_table WHERE time_table_id=1
    This provides better results:
    THE_DATE_TIME EXTRACT(TIMEZONE_REGION FROM the_date_time) EXTRACT(TIMEZONE_ABBR FROM the_date_time) EXTRACT(TIMEZONE_HOUR FROM the_date_time)
    29-OCT-06 01.00.00.000000 AM US/EASTERN US/Eastern EDT -4
    The correct time zone is now in the database. Let's test reading this with the following Java:
    System.out.println("cal= " + theDateTime);
    System.out.println("date= " + theDateTime.getTime());
    System.out.println("millis= " + theDateTime.getTimeInMillis());
    System.out.println("zone= " + theDateTime.getTimeZone());
    This provides the following results:
    cal= java.util.GregorianCalendar[...]
    date= Sun Oct 29 01:00:00 EST 2006
    millis= 1162101600000
    zone= sun.util.calendar.ZoneInfo[id="US/Eastern",...]
    The TimeZone object is correct since we are using the US/Eastern regional time zone, but the millis are wrong which makes the time EST instead of EDT. The millis should be 1162098000000.
    The conversion from java.util.Calendar to TIMESTAMPTZ loses the actual offset when setting to a regional time zone. It can maintain this info by specifying it explicitly.
    The conversion from TIMSTAMPTZ to java.util.Calendar also loses the actual offset even if the correct offset is in the database.
    Has anyone else encountered this conversion problem? It appears to be a conversion problem in both directions. I know that the Calendar is lenient by default and will assume Standard Time if time is entered during the repeated 1 o'clock hour at the end of Daylight Saving Time, but the Calendars we are using are explicit in their time, so this would be classified as data corruption.
    Nik

    Opened an SR. Looks like there is a problem with conversion either in TopLink or in JDBC.

  • Daylight saving in the NOkia 6233 ?

    Does the Nokia 6233 support Daylight Saving ? If yes, how can I set it in my phone ?

    It doesn't do it automatically, like a PC...it isn't that clever. You need to change it yourself. Be sure to set the time zone rather than change the clock, otherwise the phone may display incorrect times for SMS messages etc.
    Chris
    6230i (the last bug-free Nokia?)
    Vodafone UK contract since 1992

  • Date Time in Coldfusion at Daylight Saving

    Hi
    In coldfusion, I have problem creating Date Time using CreateDateTime when the daylight saving switch. For example
    CreateDateTime(2011,3,13,2,0,0) gives error.
    Also if you do like this
    DateAdd('h',1,CreateDateTime(2011,3,13,1,0,0)) gives "2011,3,13,3,0,0" ie instead of 2AM it returns 3AM. This is happening every daylight saving switch time.
    This is a bug in coldfusion?
    It should be fixed by Coldfusion.
    Thanks

    On 3/17/2011 12:39 AM, Paresh_Patel said:
    >
    When we loop through the 24 hours on daylight saving day e.g
    >
    <cfset startDate = CreateDateTime(2011,3,13,0,0,0)>
    >
    <cfoutput>
    <cfloop from="1" to="22" index="dayNo">
          <cfset startDate = dateAdd('h', 1, startDate)>
          #hour(startDate)#<br>
    </cfloop>
    </cfoutput>
    >
    This will show wrong hours (2 is missing)
    and that means you've fallen into timezone hell.

  • Oracle 11 driver causes problem in the day when the daylight saving starts

    Hi everybody,
    I'm facing a really weird problem with daylight saving stuff. So, let me explain:
    I have a table where stores some personal data, which one of the columns is a birth date.
    On this column there is a constraint like: TRUNC(BIRTHDATE) == BIRTHDATE to ensure that the is the same always.
    Now the problem starts:
    When a person is born when the daylight saving starts (+1 hour) (e.g: Belgium 22/04/1930) in our Java application
    that date is described like: Sun Apr 22 00:00:00 CEST 1923
    When the application tries to insert data into the table, it gets a constraint violation exception.
    The configuration I'm using:
    - JDK 6_0_21
    - Oracle driver: 11.2.0.1.0 (ojdbc6.jar)
    - Oracle database: 10.2.0.4.0
    Now the weird part: When I change back to the previous Oracle driver version (10.X), it works perfectly. I've seen this FAQ:
    http://www.oracle.com/technetwork/database/enterprise-edition/jdbc-faq-090281.html#08_01
    and tried both solutions: Set the mapDateToTimestamp property and change from DATE to TIMESTAMP type in the table. Unfortunately, both don't
    work.
    Anybody has an idea how to solve that? (Change back to the previous version is not an option for us, since we had transactional problems with it)
    Cheers,
    Bruno

    You might want to post on ODBC

  • Switch to standard time from daylight saving causes error - iOS 7

    Hi there,
    Today (27-Oct-2013) the time was switched back from daylight saving to standard. When looking my iPhone, I noticed that although the clock correctly displays the current time, the standard weather app still uses the time according to daylight saving (i.e. showing one hour ahead) and what is more interesting, the calendar acts weirdly, showing the correct time, but placing it in the old daylight saving time, i.e. 7:46 AM is shown as a line between 8:00 AM and 9:00 AM! It is really ridiculous and it seems I cannot change these. I restarted my iphone, turned off and on again using carrier provided time, but nothing changed. Any clues?
    Using iPhone 5 and iOS 7.0.2.
    Any help is appreciated.

    Problems with time, time zones have been quite common. Clearly, my brand new, the most forward thinking smartphone has the same bug. Sometimes I wonder why Apple is unable to get basic things work? they simply don't care, that's all.
    Issue with the line materializes itself on my iCal on iMac as well
    I hope, at least alarm will go off at the right time Monday morning
    BTW:  last year when I was on trip to Chile, at one night - suddenly - out of the blue - time changed on all our apple devices.. it's bad when you've got your flight next day and don't know when to wake up weeks later I have found out information Apple did not update their list of timezone changing dates.. for couple of years...

  • IPhone + Outlook, recurring meetings not adjusted for Daylight Saving (Arizona)

    Anybody else out there living in Phoenix and syncing with Outlook?
    I have an iPhone 4 running iOS 5.0.1 and I sync my calendar with Outlook 2007 running on Windows XP.  Recurring meetings that were sent from another timezone are not showing the correct time following the Daylight Saving Time (DST) change on Nov. 6.
    For example, I have a recurring meeting for Tuesdays that was originally sent to me July 26, 2011 (during DST, that is) by my customer in California.  In Outlook the time is shown as 8:00 AM Pacific Time.  During DST this meeting was shown correctly in Calendar as 8:00AM.  Today it still shows as 8:00 but should show as 9:00 (8:00 PST = 9:00 MST).
    Phone Settings:  My iPhone's time zone was originally set this morning to "Set Automatically ON" and it had selected Denver although I'm in Phoenix.  I understand that Denver and Phoenix now share the same time.  I turned "Set Automatically" off and selected "Phoenix, U.S.A." then resynced, but the appoinment above still shows 8:00.
    So how do I fix this?  I really don't want my customer to have to resend the invite just to fix an iOS bug. 

    Not sure if people are still looking at this post, but we did finally find a fix for the issue.
    In the end we figured out that one of our exchange mail box users had something faulty in their profile. By "faulty", our exchange admins attempted to move the user's mail profile from one mail store to another, but exchange returned errors when attempting to do so.
    In order to "fix" the issue we ended up deleting the mail profile completely from exchange and then recreating it from scratch - scary prospect when having to do this with someone high up the food chain... (prior export and reimport essential otherwise all data is lost)
    (the user dealt with many meetings for multiple staff, and was a common factor between all users getting the issue)
    I wouldn't call this specifically a MS issue as prior to ipad/iphones, these issues did not occur, and even while it was occuring, turning off mail on ipad/iphones meant the issue did not occur and other email clients had no issues at all
    - so it looks like something in the iphone is not quite robust enough to be able to handle a few errors
    (alternative theory: perhaps it is the iphone that created the issue in the first place??? We don't know when the issue with the actual mail account started and not enough resources to trowel through log files looking for a needle in a haystack)
    Anyway, not sure if this will help everyone with the same issue, but thought I'd share our experience

  • Daylight Saving Time Changes in 2007 for USA

    Can anyone give me solution how to handle Daylight saving Time changes in 2007 in USA for JDK 1.3.x releases? We are using this due to some vendor dependency. We can�t upgrade to higher versions up to middle of the 2007. I would be thankful if somebody gets back to me.

    I have a similar issue where we cannot upgrade the jdk 1.1 without involving a lot of effort. If we keep the same old jdk, can someone tell me if use of Date and Calendar api will be impacted by the Daylight saving change.....provided the timezone is default and not explicitly set to EST. Also there isnt any timezone related buss logic.

  • Java 1.4 and Daylight Saving Time 2007

    The current version of Java 1.4.2 for Tiger, 'Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-244)' does not handle the new 2007 Daylight Saving Time rules correctly. Will Apple be updating Java 1.4.2 to the version that does support 2007 DST correctly? (at least 1.4.2_11 is required per Sun, http://java.sun.com/developer/technicalArticles/Intl/USDST/).
    If so, when? Thanks!

    Since you didn't list your computer, here's a link to Java 5.0 release 4 for both PPC and Intel-based Macs, which came out in April: http://search.info.apple.com/?q=J2SE50Release4.dmg&type=kbdload&search=Search&lr =lang_en&search=Go. That should solve your problem.

  • Clock UI control and daylight saving time.

    Hi,
    We have a customer that has several sites around the world.
    In a VC-model I like to use the Clock UI control to display the times of the different sites.
    This can be done by setting the ‘time zone’ in the control properties.
    A long ago we have introduced ‘daylight saving time’.
    It seems that the clock control does not do anything with this ?
    How can I change the time zone when the model is running ?
    Can it be done by an expression and how ?
    There is also a problem of the country, some have DST, others don’t.
    See http://en.wikipedia.org/wiki/Daylight_saving_time_around_the_world
    Example:
    I have 2 clocks and the end-user lives in Amsterdam:
    Amsterdam, time zone = GMT + 1
    Santiago, time zone = GMT – 4
    During the winter in Amsterdam it is summer in Santiago and has ‘daylight saving’ so the time in Santiago should be GMT – 3 in stead of GMT -4.

    With the current version of VC / flash, it is not possible to display the correct time all the year 'round.
    If you only want to show the (user) current time then you can use this VC clock object.
    If you need to show clocks from different cities around the world, than its better NOT to use the VC clock.
    Because you can not define the country and city in the clock properties, that determine the use of DST, it will not always show the correct (default / DST) time.
    Solution:
    Add a HTLM-view to your model with a links to a web clock.
    Nice (free !) clocks can be found (and customized) on <a href="http://www.worldtimeserver.com/clocks/wtsclock001.aspx">worldtimeserver.com</a> or <a href="http://www.timeanddate.com/clocks/free.html">timeanddate.com</a> .
    Example:
    For the city Santiago (Chile) the URL =
    http://free.timeanddate.com/clock/ielrw91/n232/tluk/fn13/fs16/fc009/tt0/tw1/td2/th1/ts1/tb4

  • Background saving bug CS6 (stalls)

    Background saving bug CS6
    Problem:
    1. Was Editing a rather large and complex file, 16bit, 1,6GB
    2. Pressed ctr+s to save the progress
    3. Immediately launched a 3rd party plugin, Niksoft Define 2 (I mean with two keyboard shortcuts in a row, within seconds of each other)
    4. Plugin started
    5. Background saving got stuck at 0% and went nowehere as the plugin launched.
    6. No progress on the background saving after the plugin exited, and not able to save as a new file because PS said it was already saving the file. After 20 minutes still no progress. Taskmanager showed PS using 0% CPU and no disk i/o activity even though it stated it was saving.
    Workaround
    1. Duplicated the entire psb to a new file inside photoshop.
    2. Saved and it worked fine.
    3. Had to terminate photoshop via the task manager as it wouldnt let me exit "before file saving was complete".
    My workflow here was probably a bit quick and "incosiderate", but I would still consider this behaviour  a PS bug - I mean whats the use of background saving if it stalls when you are doing other tasks. Anyone else experienced this?
    (OS W7 x64+PS CS6 EXT)

    I have experienced this bug many times and it is very frustrating. There is no pattern to when it will happen it just happens out of the blue, I work full time commercially in 8, 16 and 32 bit regularly, file sizes averaging 5gb sometimes much larger and the bug has occurred in all these instances. I have however made these observations:
    The original PS version with bg save had this fault and to my knowledge there was no easy work around apart from a very laborious process of Scripts/Export layers to files. Any duplication and resave of the document did not work as it was held in a queue behind the first file stuck on 0%
    The next version of PS, CC and possibly first release of 2014, had a work around as suggested by someone else, by simply duplicating the file and saving. This would then jump the queue of the first file which was stuck on 0%.
    The latest version of CC 2014 updated a couple of days ago has resorted to the first patten, i.e. duplicate and save but stuck in the queue, thus no work around.
    This is a very serious problem which has gone on a bit too long. I am prompted to write this because it happened to me again last night whilst working on a 6gb 32bit render layer file, costing me a fair bit of time and effort on a commercial job.
    I always use bg save and 10mins recovery, when the problem occurs I am able to use PS as if nothing has happened but unfortunately cannot save, I am thus forced to force quit the application. Unfortunately in this instance the force quit is not seen by PS as a crash and therefore offers no file recovery. What I think we need is the following:
    The ability to force abort a save of the stuck file so that we can save another.
    The ability to access background saved files even if PS has not actually crashed, this would have saved me last night.
    In addition, a 5-10gb file takes a while to background save, during this save I cannot make a smart object. I would like to be able to pause a save so that I can make the smart object and then carry on my work whilst the save continues. This applies to recovery save also.
    Adobe please help us out and address the problem.
    Many thanks, Mark.

  • Daylight Saving Time Changes for 2007

    Hello Friends
    Sun's J2SE 1.4.2_11 has taekn care of the new Daylight Saving Time changes in accordance with The Energy Policy Act of 2005. Does anyone know if bea has incorporated same changes to their Jrockit, if so then starting which version.
    http://java.sun.com/developer/technicalArticles/Intl/USDST/
    Thanks for the answers in advance.
    Regards
    Rajeev Bhogal

    Hello All
    We currently compile and run our application with Jrockit 1.4.2_04 (build 1.4.2_04-b05), if we change to minor version 11 for 1.4.2 should we recompile the application. I would think that DST related binaries would only be called at run time not compile time, however I am far from being a compiler expert. Can any learned friend shed some light.
    Henrik what do you think.
    Regards and Thanks
    Rajeev Bhogal

  • C6 Calendar issue with daylight saving

    Hi, my C6-00 works fine until daylight saving switches. I am using outlook 2007 and ovi suit to sync between cellphone and PC, both are up to date and both set on China timezone. I started to see some recurrance meetings(those created prior to March by US colleague in outlook) are still showing the old time (I expect them to show up 1 hr earlier in China time because of Daylight Saving in US, just like what I see on outlook), however new meetings created after Mar are fine. Is this a bug?

    I'm guessing it's the Time Server you're using ...

  • Support for US Daylight Saving Time changes in 2007

    The Start and Stop dates for Daylight Savings Time in US will change from 2007.
    From Sun's bug database, it looks like Sun has handled this Daylight Saving Time changes in JDK 1.5.0_06.
    http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6317178
    Does anyone know if they have handled this in earlier JDK releases (1.3.x, 1.4.x)? If not, do they have any plan to handle these changes?

    1.3.1_18 had a timezone change.
    http://java.sun.com/j2se/1.3/ReleaseNotes.html
    1.4.2_11 had some timezone changes (but now there is a 1.4.2_12, so use that).
    http://java.sun.com/j2se/1.4.2/ReleaseNotes.html
    Not sure exactly what the timezone changes were, but check the release notes or give those JDKs a try.

Maybe you are looking for