Event times changed when daylight savings time changed - that's just wrong!

My events that were scheduled for certain times all were changed one hour back, when DST changed. Why should that happen? An event that is scheduled for 8:15 should still be 8:15, however, it automatically got moved to 7:15, as did all my other scheduled events.
Is this happening to anyone else?

Well if you are syncing they should both be set the same way. Try turning it on on the Mac and see if the events go back to their correct times.
AK

Similar Messages

Saskatchewan does not change to daylight savings time

Saskatchewan does not change to daylight savings time but my calendar on my iPhone 5s changed and my iMac stayed the same and the iMac time is the correct one

Automatically changing the date and time when set to automatically is carrier dependent since that is acquired by the cell tower the iPhone is connected with.

All Event times change with Daylight Savings time

With the time change associated with daylight savings time (March 8 2008) all my event times were changed by one hour. EG: events that were 8:45 am are now 7:45 am. I have tried using Time machine to restore to pre March 8 status,but an adjustment takes place and the events remain 1 hour ahead. I have looked through the discussions pages and don't even see the issue identified. I have looked through the menu and preference items and find nothing to help.
I am surprised not to find this a front page topic today, March 9 2008.
Can anyone offer some help ?
Bill Mullen

Michael,
I never have changed time zones. Are you suggesting I should have time zone support enabled ?
I just tried turning on Time Zone Support, then restoring my calendar using Time machine. No change here.
As I mentioned earlier, this same problem occurred in the fall (although I don't remember which way the event times moved), this time they moved forward. At the Fall change I was using a Mac G4, which I used as a target to build this machine. The only thing I can think of that makes me unique (although I'm not in that small of a group) is that I have altered one of the files in iSync to allow iSync to sync calendar events with iCal. The syncing has always worked OK.
Right now I'm leary of attempting to do anything with iSync. I'm also finding it difficult to believe I'm not one of 10,000 people experiencing the same problem, but I don't see any other posts.
I found a time zone in south america which returns my times to the correct figure, with time zone support enabled, but that looks like a deeper hole to dig out of.
Still stuck,
Bill

ICal times changed with change from Daylight savings time

My times on iCal on my G5 are correct. I transferred them to my iPod through iTunes. But when I changed the time from Daylight savings time Sat, my times on my iPod's iCal all moved an hour earlier. However, an event that I added today has the correct time. Besides having my iPod clock set for the wrong time, how do I correct the times in my iCal?

I now have a follow-up problem. Almost everything is right in my iPod calendar as I deleted and then manually added repeated events for Mon, Tue, Thurs, Fri, Sat, and Sun. into my G5 iCal. Mondays, Wednesdays, Thursdays, Fridays, Saturdays, and Sundays are correct in the iPod. However, my Tuesdays show both my Monday AND Tuesday events. Have you run into that problem?

IdM Scheduler and Time Change to Daylight Savings Time GMT to BST

This isn't really a 'question' , but just a topic for discussion.
We're not live yet, but will be by the time the clocks go back. So I'm just interest to hear everyone's experiences and any issues with regards to the switching to / from DST
I did some "interesting" (or not) tests last night to see what happens with Pending Values which are due to take effect at the time change threshold of 01:00 GMT when switching to Daylight Savings Time (BST) GMT +0100.
It seems as if the IdM scheduler keeps going according to UTC or GMT. However any values provisioned to target systems or to local tables using the ddm.datetime8601 system variable are in local time according to the runtime server or SQL server's locale settings.
I set up a task to output from a javascript the current system date
using the following in the functions.
currentTime = new Date();
return currentTime.toString(); // returns Locale Time String
currentTime = new Date();
return currentTime.toUTCString(); // returns UTC Time String
in the same pass I also output the ddm.datetime8601 system parameter and the ddm.time24 system parameter.
This task was to update a comment on an entry and Scheduled to run at 00:00:00 and was executed at 00:00:06 GMT all times were still in GMT as expected.
Local Time: Sun Mar 27 00:00:06 GMT-0000 (GMT) 2011, UTC Time: Sun, 27 Mar 2011 00:00:06 GMT, ddm.datetime8601: 2011-03-27T00:00:06, ddm.time24: 00:00:06
This task was scheduled at 01:00:00 in IdM and was exectued at 01:00:08 GMT by the runtime, and you can see the local time is being correctly reported as 02:00:08 BST. Note also the ddmdatetime8061 is also 02:00:08 i.e. BST.
Local Time: Sun Mar 27 02:00:08 GMT+0100 (BST) 2011, UTC Time: Sun, 27 Mar 2011 01:00:08 GMT, ddm.datetime8601: 2011-03-27T02:00:08, ddm.time24: 02:00:08
In the database the entry values MXI_VALUES ModifyTime field has the GMT / UTC timestamp.
I also set up some pending value objects to be applied at 00:59:59 and 01:30:00 to see if the 01:30:00 would be 'skipped' as the locl clock change would've gone from 00:59:59 to 02:00:00. Well the pending values were correctly applied and expired and no 'lost' transactions happened as a result of the change.
So essentially it seems to me that the IdM runtime and scheduler times are all based on UTC / GMT.
I guess it's only an issue twice a year if you're expecting something to happen at a specific local time 01:00:00 or if you've got a global user base and their account expiry should be in each user's own country's local time. In these cases, it would seem that you'd need to convert the schedule times and pending value times to UTC first before setting them in the database.
Has anyone else had any issues, thoughts, questions or suggestioins on scheduling tasks which span the DST time change when switching to and from Daylight Savings Time.
Edited by: Paul Abrahamson on Mar 27, 2011 10:51 AM

Read here:
http://www.appleinsider.com/articles/10/10/11/applesays_ios_software_update_to_fix_pesky_alarm_clockbug.html

Reminder times change with daylight savings time

How can I prevent my reminders from changing with daylight savings? I want the times to remain static throughout the year.

Michael,
I never have changed time zones. Are you suggesting I should have time zone support enabled ?
I just tried turning on Time Zone Support, then restoring my calendar using Time machine. No change here.
As I mentioned earlier, this same problem occurred in the fall (although I don't remember which way the event times moved), this time they moved forward. At the Fall change I was using a Mac G4, which I used as a target to build this machine. The only thing I can think of that makes me unique (although I'm not in that small of a group) is that I have altered one of the files in iSync to allow iSync to sync calendar events with iCal. The syncing has always worked OK.
Right now I'm leary of attempting to do anything with iSync. I'm also finding it difficult to believe I'm not one of 10,000 people experiencing the same problem, but I don't see any other posts.
I found a time zone in south america which returns my times to the correct figure, with time zone support enabled, but that looks like a deeper hole to dig out of.
Still stuck,
Bill

IPhone calendar time problem post daylight savings time change

Addendum to the similar post about a one hour differential between iCal and iPhone. THis is not just iCal. I have the same problem on WIndows XP/Outlook 2003. Everythign worked fine until the time change last weekend. Now this is what happens:
Any meeting set up in Outlook BEFORE Daylight Savings that has a start date BEFORE Daylight Savings appears properly on iPhone. FOr example, every Thursday beginning Nov 1 at 8am. THis shows up correct in iPhone at 8am for today, Nov 8.
But, any meeting set up AFTER Daylight Savings shows up one hour later on the iPhone when I sync. SO a meeting I set up in OUtlook for 10am today shows up at 11am on the iPhone.
And, any calendar event I set up on the iPhone AFTER Daylight Savings shows up one hour earlier in Outlook 2003.
THis is a huge problem for me! Both of my calendars are wrong now. PLease help!!! I have tried everything I can:
I tried setting up meetings with the OUtlook Daylight Savings setting enables and disabled: no change. No differnce whether I set up the meeting on my PC or it is an invitation from someone else. I lost all sync history. no change. I overwrote all calendar content (in iPhone advanced options) - no change.
And, as my fellow poster mentions - the tiime on the two systems match.

I think this problem is more complex. Background - UK clocks went back at the end of October; the USA went back one week later. I am in the UK and my Outlook calendar contains appointments created in the USA.
Someone in the USA created a recurring appointment before any clocks went back. In Outlook everything is correct. The meeting times are the same each week except for the one week between the two clock changes when, quite correctly, the meeting shows up one hour earlier. When I sync with my iPhone, the meeting shows at the same time every week regardless - this is incorrect.
Someone in the USA created a recurring appointment in the week after the UK clocks went back but before the USA clocks did. Outlook correctly shows the first occurrence as one hour earlier than all the following occurrences. Unfortunately - and this is the really nasty bit - the iPhone shows ALL the appointments one hour earlier than they should be. The only one that is correct is the first one.
This is a nasty bug and something that Apple needs to fix.

Make clock change for daylight savings time

how?
bios clock is set to local
I dualboot with vista
using xfce

When using OpenNTPD I recommend not to uncomment lines
# Addresses to listen on (ntpd does not listen by default)
#listen on *
#listen on 127.0.0.1
#listen on ::1
in your /etc/ntpd.conf. I had some strange problems when I did that. The clock was constantly about 40 minutes slow.

READ THIS PLEASE : New technote crashing, Daylight Savings Time, Nov 4th time change in US.

http://www.adobe.com/go/kb402776
TechNote
Dreamweaver CS3 crashes after Daylight Savings Time ends
Issue
Adobe Dreamweaver CS3 crashes when working with certain PHP
or ASP files in
Code view or Design view after the clock goes back one hour,
when Daylight
Savings Time ends. The crashes only occur when selecting
certain lines in
Code view, or selecting certain objects in Design view. The
crashes only
occur in files that have PHP or ASP code, intermingled with
HTML code. The
crashes do not occur in Dreamweaver 8 or earlier (Ref.
229536).
Reason
The Dreamweaver CS3 WinFileCache-7A9586CB.dat file has been
corrupted by the
time change.
Solution
1. If Dreamweaver is open, quit the application.
2. Delete the WinFileCache-7A9586CB.dat file from the
Dreamweaver user
configuration folder. Note that on Windows, the Application
Data and AppData
folders are hidden by default, so verify that your Windows
Explorer folder
options are set to View Hidden Folders. The location of this
file is as
follows:
* Dreamweaver CS3 on Windows Vista:
C:\Users\[username]\AppData\Roaming\Adobe\Dreamweaver
9\Configuration
* Dreamweaver CS3 on Windows XP:
C:\Documents and Settings\[username]\Application
Data\Adobe\Dreamweaver
9\Configuration
3. Restart Dreamweaver.
Keywords
Code/Design view, Daylight Savings Time, Dreamweaver, crashes
TechNote Details
Last Update: 11-02-2007
ID: kb402776
OS:
* Windows XP, Windows Vista
Permanent Link:
http://www.adobe.com/go/kb402776
Alan
Adobe Community Expert, dreamweaver
http://www.adobe.com/communities/experts/

Alan wrote:
>
http://www.adobe.com/go/kb402776
>
> TechNote
>
> Dreamweaver CS3 crashes after Daylight Savings Time ends
>
> Issue
>
>
> Adobe Dreamweaver CS3 crashes when working with certain
PHP or ASP files in
> Code view or Design view after the clock goes back one
hour, when Daylight
> Savings Time ends. The crashes only occur when selecting
certain lines in
> Code view, or selecting certain objects in Design view.
The crashes only
> occur in files that have PHP or ASP code, intermingled
with HTML code. The
> crashes do not occur in Dreamweaver 8 or earlier (Ref.
229536).
>
>
> Reason
>
>
> The Dreamweaver CS3 WinFileCache-7A9586CB.dat file has
been corrupted by the
> time change.
>
>
> Solution
>
>
> 1. If Dreamweaver is open, quit the application.
> 2. Delete the WinFileCache-7A9586CB.dat file from the
Dreamweaver user
> configuration folder. Note that on Windows, the
Application Data and AppData
> folders are hidden by default, so verify that your
Windows Explorer folder
> options are set to View Hidden Folders. The location of
this file is as
> follows:
> * Dreamweaver CS3 on Windows Vista:
> C:\Users\[username]\AppData\Roaming\Adobe\Dreamweaver
9\Configuration
> * Dreamweaver CS3 on Windows XP:
> C:\Documents and Settings\[username]\Application
Data\Adobe\Dreamweaver
> 9\Configuration
> 3. Restart Dreamweaver.
>
>
> Keywords
>
> Code/Design view, Daylight Savings Time, Dreamweaver,
crashes
>
> TechNote Details
> Last Update: 11-02-2007
> ID: kb402776
> OS:
> * Windows XP, Windows Vista
> Permanent Link:
http://www.adobe.com/go/kb402776
>
>
>
Interesting, because on my PC that cache file is only in my
old DW8
folder, while this one is in my DW9 (CS3) folder:
WinFileCache-AD76BB20.dat
What's up with that?
E. Michael Brandt
www.divaHTML.com
divaPOP : standards-compliant popup windows
divaGPS : you-are-here menu highlighting
divaFAQ : FAQ pages with pizazz
www.valleywebdesigns.com/vwd_Vdw.asp
JustSo PictureWindow
JustSo PhotoAlbum, et alia

Having problems setting alarm time since daylight savings time change today

Since the change to Daylight Savings time this morning, I am unable to set my alarm correctly. I set it to 2:40 a.m. but the time on the alarm shows 3:40 a.m. I have all the proper settings correctly done. I have powered down the phone numerous times, and still the same result. Any assistance would be greatly appreciated.

I've cleared the clock cache, powered off the phone and the problem remains the same. I have the Automatic date & time checked, and the same for Automatic time zone (GMT-5:00, Eastern Daylight Time). I have even unchecked both and still get the same result.
What is weird, I can set the alarm for any other time, but unable to set it at 2:40 a.m. When I do this, it sets to 3:40 a.m. Any time that I set from 2:00 a.m. to 2:59 a.m. goes to that time setting in the 3 a.m. time.

Multiple instances spawned after daylight savings time change

This is a known issue and there is an SAP Knowledge Base Article created on this issue:
1448881 - Multiple instances spawned after daylight savings time change
Below is the information from the SAP Knowledge Base Article:
Symptom
Scheduled reports that are supposed to run once a day, run multiple times.
Duplicate instances are being created.
Environment
BusinessObjects Enterprise XIR2 SP5
BusinessObjects Enterprise XIR2 SP5 + FP5.x
Reproducing the Issue
A report is scheduled to be run on a daily basis - this is a Recurring schedule.
Normally the report runs once a day, at a particular time.
After Daylight Savings Time change, the report runs at the specified time, but immediately after the successful instance, another instance is spawned.
Many more instances spawn after each instance completes.
Cause
This is a known issue: ADAPT01318487. This issue is because of DST and how our code handles this change.
Resolution
There is currently no known fix for this issue. There is however a script that can quickly resolve the problem.
The issue it seems is related to Daily recurring schedules.
What this script will do:
it will run a query to display all your DAILY Recurring jobs
you will have the option to choose your jobs and reschedule them by 1 hour
you will then highlight the same job and change them back by 1 hour
by modifying the schedule times, you are modifying the schedule itself and this will keep the issue of duplicate instances from occurring.
Exact Steps to Complete:
Stop the Job Servers.
Double click on the .hta file.
Change the System Name to that of your CMS name.
Add the Administrator's password.
Click Logon.
Click List All Recurring Instances.
Select All.
Make note of what it says in: Schedule Selected Recurring Instances: Should be 1 hr earlier.
Click Reschedule Selected Recurring Instances.
Choose All instances again and change Schedule Selected Recurring Instances to 1 hour Later.
Click Reschedule Selected Recurring Instances.
Now start your Job Servers.
The issue should not occur again.
The Script is attached here, but please review the SAP Knowledge Base article 1448881 as well

Hi Nicola,
- The multiple spawned instances issue ONLY affects XI3 SP3+ only. For XI3 SP1 and SP2 all Fix Pack levels this is not an issue as it was introduced as a problem in SP3.
- 1568239 notes the Java version and can apply to all O/S environments and is updated to reflect that.
If you are located in Europe you can also apply the patches in advance of the DST change to avoid the problem. If you are in Americas at this point utilizing the clean up scripts for this year is the approach needed to clean up the spawned instances and reschedule the existing schedules.
Thanks,
Chris

Daylight Savings Time not changing

I have a Verizon Wireless iPhone 4 and the time didn't change for daylight savings time today. It is set to do it automaticly and I also tried to sync it to see if it would change but it didn't. Any advice?

I, too, suffered the same problem with my iphone 4, os 4.3. My phone did not spring forward an hour, unless I turned it off to do so automatically in the settings. However, my son has a 3gs and his phone DID spring forward. Same house, same AT&T, same os, same everything except for the type of phone. Very strange. I restarted my phone two times, but the only thing that would make it spring forward was to turn off "Set Automatically," then it moved, but if I turned it back on it would go back an hour. Erg.

Has anyone had problems in v5.0a of Iplanet calendar installed on a Sun box with creating events and daylight savings time?

Events created around 4/6/2002 at 8pm get created with the wrong time (9pm) and there are several other creation and display problems tied to Daylight Savings in April and October. Version 5.1 of the software seems to fix that but we are looking for a fix until we can upgrade. We have been using Windows systems to access the calendar.
Thanks.

We have not seen exactly this, but many users appointments are lining up in the wrong time slots. Also, when scheduling, the time display is off by an hour. We have found what looks like a temporary fix.
We noticed that the problem only affects users who have the start of the week set to Sunday (when daylight savings time started). Setting the week to start on Monday fixed our display problems (you can do it in the users, options section).
I am placing a support call w/SUN.

Cron job and daylight savings time

What is the behaviour of cron when the time changes from daylight savings time to standard time and vice versa ?

This has been discussed at length in
http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=1&catid=7&threadid=12 44419&highlight_key=y&keyword1=dst

Phone didn't change for daylight savings

my droid 4 did not change to daylights savings time last night, and I was very late, and what is up with that? this has never happened before. It finally changed at about 10 AM, as I was sending a text. all settings on the phone are correct for automatic time changes. has this happened to anyone else today?

Hello Sciaccajan
I'm sorry you were late! The issue you experienced was very odd. It may have been a delayed signal or an application that interfered. Please power down the device remove and reinsert the Sim card and retest. This will force the device to see all the towers.
JoeL_VZW
Follow us on Twitter @VZWSupport

Event times changed when daylight savings time changed - that's just wrong!

Similar Messages

Maybe you are looking for