Daylight saving error in Calendar application

A notice for concerned users:
When an event is scheduled on iCal v. 3.0.1 (i.e. on a Leopard iMac) with a time zone of "UTC", it does not display with the proper event time when viewing the event on the iPhone Calendar application if the daylight saving setting of the day of the event is different from the current daylight saving setting for today.
Example: I am located in the Central time zone (i.e. Chicago). If I schedule an event for 10:00 p.m. UTC on March 10 (the day after daylight saving time begins), then review the event in Calender prior to March 9, the iPhone will display the event for 4:00 p.m. (which is it's time in CST) instead of correct time of 5:00 p.m. (which is it's time in CDT).
In other words, displayed times for future events are calculated using today's daylight saving setting instead of the daylight saving setting of the date of the event.

Given that the week is now over and your phone and PC should both have reverted to EST, not EDT, this problem should now have passed.
This problem should have been corrected with a firmware upgrade but the e61 hasn't had a firmware upgrade for over a year...
This year I just ignored it as the actual reminders were still happening at the right moment of the day! As it was synchronising via Mail for Exchange all was fine, as the PC was dominant.
The only other work around is to set the phone to another time zone that was correct for the week while this schemozzle lasted.
Hopeless, wasn't it? It is up to the Australian government to gazette calendars for Australia not Nokia! Nokia should have an appropriate mechanism in place to check for adjustments to time zone etc information.

Similar Messages

Daylight saving error ...

can anyone explian me what exactly is this erro
"daylight saving error "
regards
Snigdha

Hi Snigdha,
You can find the relevant info here:
Daylight Saving Patch for March
Hope this helps...

Daylight saving error on E61i in Australia

This year daylight saving in many parts of Australia finishes a week later than usual. My PC and Outlook understood, but my E61i went back an hour. I cannot find any settings in the phone or doco which can influence how the phone reacts to daylight saving.
The issue is not just the time. Most (curiously, not all) of my timed calendar entries in the intervening week have also gone an hour earlier. They are fine before the week, and after the proper changeover. If I manually change the phone's time, the calendar entries stay wrong.
What do I do? I see references to firmware (?!) changes for other models (including E61). My software level is 2.0633.65.01.

Given that the week is now over and your phone and PC should both have reverted to EST, not EDT, this problem should now have passed.
This problem should have been corrected with a firmware upgrade but the e61 hasn't had a firmware upgrade for over a year...
This year I just ignored it as the actual reminders were still happening at the right moment of the day! As it was synchronising via Mail for Exchange all was fine, as the PC was dominant.
The only other work around is to set the phone to another time zone that was correct for the week while this schemozzle lasted.
Hopeless, wasn't it? It is up to the Australian government to gazette calendars for Australia not Nokia! Nokia should have an appropriate mechanism in place to check for adjustments to time zone etc information.

Daylight saving time causes a date error on 01/APR

morning dears,
we are facing an issue related to Daylight saving time, as the following:
at any page on the system that contains a calendar if we choose the date 01/04/2012 it generate an error...
example on this error :
on Leave Request page --> when choosing 01/04/2012 then clicking on calculate duration-->
01/04/2012 is not a valid date. Please re-enter.
any suggestions??

dears any suggestions to solve the issue??
have anyone faced this before?

Rich: calendar problem when automatically adjust clock for daylight saving

Hello, I'm in trouble when the option to automatically adjust clock for daylight saving time is marked. My locale is pt_BR, and when I try to select the day it simply returns to 17.10.2010 on 16.10.2010 took the test in the following component and realized that the same problem occurs when the Windows clock option is selected .
http://livedemo.exadel.com/richfaces-demo/richfaces/calendar.jsf?tab=usage&cid=15374785
I also noticed that this problem occurs in all components of the JSF schedule, no matter what the distribution
http://www.primefaces.org:8080/prime-showcase/ui/calendarDisplay.jsf
Question is, how to make the jsf solve this problem without having to uncheck the Windows clock?
See below for the following attempts to try to fix the problem:
faces-config.xml file
    <locale-config>
         <default-locale> en </ default-locale>
         <supported-locale> en_US </ supported-locale>
         <supported-locale> of </ supported-locale>
         <supported-locale> fr </ supported-locale>
        <supported-locale> es </ supported-locale>
        <default-time-zone-id> Brazil / East </ default-time-zone-id>
    </locale-config>
{code}
Created file DateTimeZoneConverter
{code:java}
import java.util.SimpleTimeZone;
import javax.faces.convert.DateTimeConverter;
public class extends DateTimeZoneConverter DateTimeConverter {
     public DateTimeZoneConverter () {
        super ();
        SimpleTimeZone stz = new SimpleTimeZone (7200000, "Brazil/East");
        this.setTimeZone (stz);
{code}
In the example above I'm forcing the useDaylight is false.
In component:
{code:java}
<rich:calendar id = "periodoVigencia" enableManualInput = "true" datePattern = "dd / MM / yyyy" inputSize = "10"
           value = "# () contratoMBeanList.criteria.dataInicioVigencia"
           label = "# (msg ['contrato.consultarContrato.field.periodovigencia.label'])">
           <f:convertDateTime pattern="dd/MM/yyyy" type="date" dateStyle="short" timeZone="GMT-3"/>
</rich:calendar>
{code}
and in the web.xml file
{code:java}
<context-param>
     <param-name> timezone </ param-name>
      <param-value> GMT-3 </ param-value>
</context-param>
{code}
But nothing worked. And now what do I do? How to fix this problem, there are some more configuration to be done? Help, please!
P.S.:Apologize for my english, I'm Brazilian.

Like I said, were attempts to resolve the error.
OK, now how to solve this problem? Try the test in your area by selecting the day that DST occurs, you will see what will happen the same problem (to select the day that DST occurs on the screen will return one day less), do the test with the demos that I put in the first post, rich: calendar and prime: calendar.
I do not know if it helps, but I noticed the firebug firefox debugging, it does not matter the way you change the locale or timezone, as the current date from the calendar javascript will always be the standard of the machine running the component.

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...

ActiveSync Calendar and Daylight Saving

Israel moved to Daylight Saving time and now all meetings scheduled by someone on that timezone are one hour off.
- Meetings look okay on Outlook or OWA
- the iPhone clocks are adjusted to the time change.
In addition to my other post on meetings not synchronized (http://discussions.apple.com/thread.jspa?threadID=1715532&tstart=0) , my calendar is completely useless...
Any fix for that?
Should I switch back to Windows Mobile to get my productivity back up?

I'm having the same exact problem. I've tried disabling Calendar Sync, I've tried deleting the entire ActiveSync account profile and it's still not working. All of my meeting continue to arrive on my iPhone an hour later then the meeting actually takes place. Looking at Calendar within Outlook, everything appears fine. Definitely had this problem since DayLight Savings went into place.

When there is no daylight saving, i am facing an error

Hello , I have created an add in for outlook, we setup meeting rooms, we
opened mailbox for each meeting room. Users are using Outlook 2010. We can now see all meeting rooms in our calender. And we are able to set up meetings with corresponding meeting rooms. The only issue I need to fix is that : When someone organize a meeting
in with other countries; as Australia, France, Korea , China.. some of these countries don't have daylight saving and when changing my local machine time to korea for example, it gives me an error.
This is a part of the code where getting the timeZone , plz help me to know what to change for coutries that don't have daylight saving.
// Make the request.
GetUserAvailabilityRequestType request = new GetUserAvailabilityRequestType();
// Get the local time zone
TimeZoneInfo zone = TimeZoneInfo.Local;
TimeZoneInfo.AdjustmentRule[] adjustmentRules = zone.GetAdjustmentRules();
string str_offset = "";
TimeZoneInfo.ClearCachedData();
TimeSpan offset = TimeZoneInfo.Local.BaseUtcOffset;
if (offset.ToString().Substring(0, 1).Equals("-"))
str_offset = offset.ToString().Substring(0, 3);
else
str_offset = offset.ToString().Substring(0, 2);
// Set the time zone of the request.
request.TimeZone = new SerializableTimeZone();
//TimeZoneInfo.BaseUtcOffset Property
//Gets the time difference between the current time zone's standard time and Coordinated Universal Time (UTC).
request.TimeZone.Bias = (int)TimeZoneInfo.Local.BaseUtcOffset.Negate().TotalMinutes;
for (int iAdjustment = 0; iAdjustment < adjustmentRules.Length; iAdjustment++)
if (DateTime.Now >= adjustmentRules[iAdjustment].DateStart && DateTime.Now <= adjustmentRules[iAdjustment].DateEnd)
request.TimeZone.StandardTime = new SerializableTimeZoneTime();
request.TimeZone.StandardTime.Bias = 0;
request.TimeZone.StandardTime.DayOfWeek = adjustmentRules[iAdjustment].DaylightTransitionEnd.DayOfWeek.ToString();
request.TimeZone.StandardTime.DayOrder = (short)adjustmentRules[iAdjustment].DaylightTransitionEnd.Week;
request.TimeZone.StandardTime.Month = (short)adjustmentRules[iAdjustment].DaylightTransitionEnd.Month;
request.TimeZone.StandardTime.Time = adjustmentRules[iAdjustment].DaylightTransitionEnd.TimeOfDay.ToString("HH:mm:ss");
request.TimeZone.DaylightTime = new SerializableTimeZoneTime();
//TimeZoneInfo.AdjustmentRule.DaylightDelta Property
//Gets the amount of time that is required to form the time zone's daylight saving time. This amount of time is added to the time zone's offset from
Coordinated Universal Time (UTC).
request.TimeZone.DaylightTime.Bias = (int)adjustmentRules[iAdjustment].DaylightDelta.Negate().TotalMinutes;
request.TimeZone.DaylightTime.DayOfWeek = adjustmentRules[iAdjustment].DaylightTransitionStart.DayOfWeek.ToString();
request.TimeZone.DaylightTime.DayOrder = (short)adjustmentRules[iAdjustment].DaylightTransitionStart.Week;
request.TimeZone.DaylightTime.Month = (short)adjustmentRules[iAdjustment].DaylightTransitionStart.Month;
request.TimeZone.DaylightTime.Time = adjustmentRules[iAdjustment].DaylightTransitionStart.TimeOfDay.ToString("HH:mm:ss");
// Add the mailboxes to the request.
request.MailboxDataArray = mailboxes;
// Add the free/busy view options to the request.
request.FreeBusyViewOptions = fbViewOptions;
DateTime startExchange = DateTime.Now;
// Send the request and get the response.
GetUserAvailabilityResponseType response = esb.GetUserAvailability(request);
DateTime endExchange = DateTime.Now;
TimeSpan timeWSE2010 = endExchange - startExchange;
CLogger.WriteLog(ELogLevel.INFO, "getListRoomsExchange2010 -timeWSE2010-WS=" + timeWSE2010.ToString());
// Access free/busy information.
if (response.FreeBusyResponseArray.Length < 1)
MessageBox.Show("An error occurred while getting the available rooms - No free/busy response data available.", "Pick A Room");
CLogger.WriteLog(ELogLevel.ERROR, "GetUserAvailability - An error occurred while getting the available rooms - No free/busy response data available.");
else
for (int j = 0; j < response.FreeBusyResponseArray.Length; j++)
FreeBusyResponseType fbrt = response.FreeBusyResponseArray[j];
if (fbrt.ResponseMessage.ResponseClass == ResponseClassType.Error)
Console.WriteLine(string.Format("Error: {0}", fbrt.ResponseMessage.MessageText));
else
//Get the free/busy data
FreeBusyView fbv = fbrt.FreeBusyView;
if (!fbv.MergedFreeBusy.Contains("2") && !mailboxes[j].Email.Address.ToString().Equals(""))
availableUsers = availableUsers + ThisAddIn.dictionaryRooms[mailboxes[j].Email.Address.ToString()] + ";";
catch (Exception ex)
//Error processing.
MessageBox.Show("An error occurred while getting the available rooms - Exception:" + ex.Message, "Pick A Room");
CLogger.WriteLog(ELogLevel.ERROR, "getUserAvailability - An error occurred while getting the available rooms - Exception:" + ex.Message);
return availableUsers;

Hi,
Please post the detailed error message, it’s more helpful for further troubleshooting.
Since the add-in is related to Outlook client, I recommend contact Outlook for Developers Team so that you can get more professional suggestion.
For your convenience:
https://social.msdn.microsoft.com/Forums/en-US/home?forum=outlookdev&filter=alltypes&brandIgnore=True&sort=relevancedesc&filter=alltypes&searchTerm=
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

We want to confirm that the application will be compatible daylight saving

We want to confirm that the application will be compatible during the daylight savings change over on the 1st of April where the time rolls back from 3am to 2am
confirm that we have the compatible patch sets for Australian Eastern Standard Time for daylight savings change over on 1st April 2012
running ebusiness 11.5.10
Edited by: jemar98 on Feb 24, 2012 12:19 PM

jemar98 wrote:
We want to confirm that the application will be compatible during the daylight savings change over on the 1st of April where the time rolls back from 3am to 2am
confirm that we have the compatible patch sets for Australian Eastern Standard Time for daylight savings change over on 1st April 2012
running ebusiness 11.5.10Please see these docs.
Complying with Daylight Saving Time (DST) and Time Zone Rule Changes in E-Business Suite 11i [ID 458452.1]
Diagnosing DST issue with eBusiness Suite 11i and Release 12 [ID 800420.1]
Thanks,
Hussein

TS1638 When syncing calendar on iPhone with Microsoft Office whole day appointments get moved to double day. I am aware this may be caused by conflicts in clock, viz daylight saving time. However, Outlook seems OK and takes time from Windows time and zone

When syncing my iPhone to Microsoft Outloook all the full day appointments become two day - 2300hrs to 2300hrs next day. Sometimes this will include a nuber of a single day of 23 hours. Looked at solutions and all point to a clock issue or a daylight saving and winter times. Outlook operating time is directly from the Windows clock that incudes the change of times for daylight saving etc. It is set for UTC Dublin, Edinburgh, Lisban, London with daylight saving included in the options. I can't see what I can do.

When syncing my iPhone to Microsoft Outloook all the full day appointments become two day - 2300hrs to 2300hrs next day. Sometimes this will include a nuber of a single day of 23 hours. Looked at solutions and all point to a clock issue or a daylight saving and winter times. Outlook operating time is directly from the Windows clock that incudes the change of times for daylight saving etc. It is set for UTC Dublin, Edinburgh, Lisban, London with daylight saving included in the options. I can't see what I can do.

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 ...

Calendar sync and daylight saving

I have a 6720 classic which i sync with MS Outlook 2007 via OVI suite (latest versions of all software on PC and phone). New zealand has just put it's clocks back one hour for daylight saving. Since this has occured, my existing appointments on my phone now all start one hour too early. I believe that i have the correct sync settings.

I am also having this problem and have tried multiple "fixes" nothing has worked so far. Has anyone found a fix?

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

Recurring events off by 60 minutes after daylight saving time switch

I searched but didn't find this exact issue anywhere. Following this past weekend's switch to Daylight Saving Time (DST), iCal recurring events have been shifted one hour later. It is a problem that I encountered with my own web calendaring application, wherein the offset between UTC and a given time zone changes with the coming and going of DST. I am curious why Apple has never instituted a fix for this, especially considering that the fix is so simple. All that must be done is detect whether the original datetime is in DST or not. If it is not, and the given recurrence is, then you must subtract 60 minutes from the recurrence's datetime. Similarly, if the originating datetime is in DST, and the given recurrence is not, then you must add 60 minutes to the recurrence's datetime.

I have the same problem but much worse. Only 5 of my 18 recurring weekly events have shifted, so I didn't realize that anything was off until I missed one of my classes today. This seems weird....

Exchange Active Sync UTC Daylight Saving Time

Color me a bit confused. I am attempting to write an IOS client application to communicate with Exchange ActiveSync and display calendar information. But I am seeing some conflicting information in the protocol docs when compared to what I am getting from
Exchange. Either that or I am somehow misinterpreting one or the other.
My intent is to save an appointment in my local database in Coordinated Universal Time and then have the UI read in the information and display it as appropriate to the local timezone. In this way an recurring appointment created before daylight saving time
for Noon will still be at the same time of day in local time as an appointment created during daylight saving time for noon. But they are not.
My understanding of the documentation is as such:
In MS-ASCAL pdf section 2.2.2.40 (roughly page 34) it says for Start Time that : ...the value of this element is a dateTime data type as specified in MS-ASDTYPE section 2.3.
Moving to MS-ASDTYPE section 2.3 (roughly page 7) the dateTime value is specified in the format of ISO-8601 and all dates are given in Coordinated Universal Time (UTC)
Looking up coordinated universal time I see that UTC does not changed with the seasons as local or civil time does and therefore DOES NOT support daylight saving time. This makes sense, as DST is decidedly local and is ignored by many areas. You cannot know
from the perspective of UTC whether or not to apply a DST offset without knowing what timezone and area the time represents, therefore no daylight saving time can be supported. Based on this information I should be able to just slap the dates into my database
as they are and merely have the UI adjust itself to display them properly.
However, as a tested I began seeing a divergence of an hour between the two appointments in the database before the UI has even read them. To confirm this I created two recurring appointments representing Lunch at 12 noon local time. One that starts on March
1st 2014 (Standard Time) and one that starts on March 10th 2014 (daylight saving time) in the eastern timezone. This should be March X 2014 at 1700 hours in both cases should it not?
In the WBXML/XML that I am receiving I am getting two different times. The appointment that starts during standard time gives me a start time of 20140301T170000Z. The appointment that starts after daylight saving time is in effect locally gives me 20140301T160000Z.
The difference between the two times is 1 hour, which is the daylight saving time offset. It is my perception based on everything that I have read both in the microsoft protocol documentation and outside it that these two times should be the same and that whatever
client that gets to display them should be the one putting the offset in place as needed. Noon local time is noon local time but local time is the province of the local municipality/timezone, not that of UTC.
So my question is what exactly is going on here? Are the start/stop/date stamp date times in UTC or not. If they are in UTC, then why are they offset by an hour instead of being at the same time? Obviously outlook displays these correctly for local time,
because both appear at noon. But in my case my database contains locally adjusted times instead of the UTC times I thought I was getting which is throwing off when those appointments appear in the UI.
Can someone please clarify what's going on here and what I should be seeing?
Thanks.
E

Thanks for the reply, however after doing what is said the problem still remains. I did not try the manual approach, because of the time that would take with calendars that change at least daily.
I am running the latest update of ICal and IPod, you would think this would have been addressed with one of the updates to allow the sync to work correctly with 5th generation IPods.
I am going to try and turn off day light savings time set the clock to a Central Time zone and see if that works, I do not cross time zones much, anymore.
MacBook Mac OS X (10.4.9)

Daylight saving error in Calendar application

Similar Messages

Maybe you are looking for