Daylight Savings Time...Again

It's the semi-annual file synchronization crisis, brought to you by Adobe and Daylight Savings Time, now in its nth year!
My entire 4000+ page site has gone out of synch with my local files due to daylight savings time. Apart from spending hours uploading the entire site, what can I do to maintain proper synchronization? I'd love to see an official tech note addressing this issue. BTW, I do not have any authority over the server to which I post files, so I can't make changes to how the server's timestamps are administered.
Any solutions/suggestions would be appreciated!

I've no solution, but just wanted to post to share your frustration. This has been a problem with Dreamweaver for years, and is frankly a major PITA. You'd think such an expensive product worked on by so many coders would have squashed this bug ages ago, but no, plainly the coders can't write simple code which would detect when Daylight Saving kicks in and offer you the option to 'fix' the synch such that files whose timestamps are exactly an hour behind/ahead would be marked as synched. It's not as if it's a tough algorithm, after all. Sadly, DW has become baroque bloatware since being taken over by the Adobe corporate behemoth, which seems intent on building in pointless features so as to generate sales from those eager to keep up with the latest version. I use it because my employer's bought it, but there's no way on this green earth I'd shell out for such a poor product if I had to pay out of my own pocket.
Just my 2 cent's worth...
Fred
PS: Oh, and here's an 'issue' for the board admins. Hitting reply in Firefox 4 doesn't generate this HTML editor, but instead everything just hangs. I've had to go into Safari to reply. No big, it just adds a few mm to the blood pressure and makes the poster even more cross.

Similar Messages

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 and Time Zone Issue:

Howdy! Many of us woke up this morning to be dismayed to find that our iPhone was TWO hours behind instead of falling back one for the Daylight Savings Time adjustment, and were late for church. I have an iPhone 4S, with iOS 5...
I was working at that time of morning, and the initial switch went well. However, when I woke up, the clock was yet another hour behind. A little investigation showed that the Time zone had been changed to Denver (It was previously on Chicaco, and I live in Dallas.) I tried to select it to change it, and it wouldn't allow me. If I turned off the Set Automatically feature, then I could change it, but when I turned the Set Automatically feature back on, it would re-set the time zone to Denver.
I found another thread where they discuss this:
https://discussions.apple.com/message/16644669
To fix this, put in airplane mode, then back out again, then re-choose your correct time zone. If this doesn't work, then try turning your phone completely off and then on again. Thanks to 4n6doc for the tip!
The airplane mode trick worked for me: I turned airplane mode on, then off, then went to the Date & Time and set my time zone to Dallas, TX while the Set Automatically was off. When I turned the Set Automatically back on, it changed Dallas to Chicago, which is what every iPhone iOS I've ever had has done.

Hi,
Yes this is a correct way to fix the issue. One thing however, how did you set the timezone? For correct daylight saving handling, you'll have to use the long version, like America/New Yorw, NOT GMT-5 (for example).
regards,
~ Simon

Reinstall issue: Is this a Daylight Savings Time Glitch?

I was reinstalling my system software (Garage band was lost when hard drive was backed up)and, after reinstall, the system goes to login screen. After login, the computer immediately goes to Unix login.
I looked at other threads, and can get back to the Mac login but never past it. I found a suggestion to run a diagnostice command "tail -10 /var/log/system.log" and the messages I get all included "unable to synchronize window backing store" The word "sychronize" made me think about the Daylight Savings time change as a source of the problem.
Any ideas?

dave:
Welcome to Apple Discussions.
I have not been able to find out what the message means, without any success. Someone may come along with the knowledge to solve that riddle.
First, I suggest that you boot from your install disk and run Repair Disk:
Insert Installer disk and Restart, holding down the "C" key.
Go to Installer menu and launch Disk Utility.
Select your HDD (manufacturer ID) in the left panel.
Select First Aid in the Main panel.
(Check S.M.A.R.T Status of HDD at the bottom of right panel, and report)
Click Repair Disk on the bottom right.
If DU reports disk does not need repairs quit DU and restart.
If DU reports errors Repair again and again until DU reports disk is repaired.
If DU reports errors it cannot repair you will need to use a utility like Tech Tool Pro or Disk Warrior
If that does not help post back with a description of exactly what is on your screen when you try to boot.
Good luck.
cornelius

Daylight savings time issue with iphone

When syncing iphone to pc (Vista) and Microsoft Outlook 2007, the time on the iPhone is one hour LATER that it is on the computer source.
It seems that, once again, Apple and Microsoft are at odds with each other and the new rules on Daylight Savings time were never considered.
Anybody have ideas? Seen this? There is NOTHING on the Apple website (also typical!!).

This seems like it might be similar to the problem I was having. Please see the following thread for the solution:
http://discussions.apple.com/thread.jspa?threadID=1791145&tstart=0
It worked for me, give it a shot.

IPhone not picking up Daylight Savings Time

In reviewing last year, I see that there was an issue with iPhones making the time switch to Daylight Savings Time (it appeared to be limited to New Mexico).
Well, it seems to be happening again. My wife and I are in New Jersey and neither of our iPhones made the auto switch. I assume it is an AT&T issue (again) but I'm curious if anybody else is seeing this?
I guess the work around for now is to turn off auto and set it yourself. Irritating.

You may get your wish one day which at the earliest would be sometime in 2010 and if so, then you will be talking to a bunch of idiots at whichever provider for the iPhone as none of the front line folks who answer the phone for technical support issues and questions with cellular providers are overpaid by any means, and some are not going to become a rocket scientist.
The few times I've called AT&T customer or technical support, I have no complaints whatsoever, which has been about the same with every provider I've used.
There are Verizon, Sprint, and T-Mobile subscribers who say the very same thing at times - "I just got off the phone with a bunch of idiots at - fill in the blank".

Daylight Savings time, and how dates are stored internally and displayed

This is probably a question that appears here annually, but I couldn't really find clear answers, so I'll try asking this in my own words:
I'm in the Eastern timezone, and this Sunday, we'll be turning our clocks back an hour at 2:00 AM. That means that accordign to us humans, the time 1:30 AM will occur twice on Sunday.
I've got an Oracle application that runs every 5 minutes around the clock, and it selects records from a certain table whose updated timestamp (TIMESTAMP(6)) is greater than SYSDATE - 5/1440, meaning any record that was updated in the last 5 minutes. Will we have a problem with some records being processed twice on Sunday morning? I'm theorizing that everything will be OK, that internally, Oracle stores DATE fields using something like an epoch which then gets interpreted when we display them. An epoch value will continue to grow each second no matter what “time” it is according to the U.S. Congress.
A simpler way to look at the question might be as follows:
If you store SYSDATE in a DATE column in row “X” at 1:30 AM before the time change, and you store sysdate in row “Y” exactly one hour later, will Oracle say that X’s timestamp is 60 minutes less than Y’s timestamp? All fields that are related to my particular situation are either DATE or TIMESTAMP(6).
We use 11g.

>
That settles that! Thank you! My theory was wrong! I appreciate the help.
>
You may think it settles that but, sorry to burst your bubble, that doesn't really settle much of anything.
One thing that was settled is the answer to this question
>
But are they talking about what you can EXTRACT and DISPLAY from the field or what is actually STORED internally?
>
which is, as Mark stated, they are talking about what is stored internally.
The other thing that was settled is that you will pull the same, or mostly the same, data twice during that one hour. I say 'mostly the same' because of the major flaw your extraction method has to begin with.
>
If you store SYSDATE in a DATE column in row “X” at 1:30 AM before the time change, and you store sysdate in row “Y” exactly one hour later, will Oracle say that X’s timestamp is 60 minutes less than Y’s timestamp?
>
No - they will have the same time since 'one hour later' would have been 2:30 AM but the clock was turned back an hour so is again 1:30 AM. So the second time your job runs for 5 minutes at 1:30 AM it will pull both the original 1:30 AM data AND the data inserted an hour later.
And Oracle will say that data stored in row "Z" exactly 45 minutes later than "X" at 1:30 AM will have a date of 1:15 AM and will appear to have been stored earlier.
Your method of extracting data is seriously flawed to begin with so the daylight savings time issue is the least of your problems. The reason is related to the answer to this question you asked
>
do people avoid using DATE and TIMESTAMP datatypes because they are too simple?
>
That method isn't reliable - that is why people avoid using a date/timestamp value for pulling data. And the more often you pull data the worse the problems will be.
>
I've got an Oracle application that runs every 5 minutes around the clock, and it selects records from a certain table whose updated timestamp (TIMESTAMP(6)) is greater than SYSDATE - 5/1440, meaning any record that was updated in the last 5 minutes
>
No - it doesn't do that at all, at least not reliably. And THAT is the why your method is seriously flawed.
The reason is that the value that you use for that DATE or TIMESTAMP column (e.g. SYSDATE) is assigned BEFORE the transaction is committed. But your code that extracts the data is only pulling data for values that HAVE BEEN committed.
1. A transaction begins at 11:59 AM and performs an INSERT of one (or any number) of records. The value of SYSDATE used is 11:59 AM.
2. The transaction is COMMITTED at 12:03 AM.
3. Your job, which runs every five minutes pulls data for the period 11:55:00 AM to 11:59:59 AM. This job will NOT see the records inserted in step #1 because they had not been committed when your job query began execution - read consistency
4. Your job next pulls data for the period 12:00:00 AM to 12:04:59 AM. This job will also NOT see the records inserted in step #1 because the SYSDATE value used was 11:59 AM which is BEFORE this jobs time range.
You have one or ANY NUMBER of records that ARE NEVER PULLED!
That is why people don't (or shouldn't) use DATE/TIMESTAMP values for pulling data. If you only pull data once per day (e.g. after midnight to get 'yesterdays' data) then the only data you will miss is for data where the transaction began before midnight but the commit happened after midnight. Some environments have no, or very little, activity at that time of night and so may never have a 'missing data' problem.
Creating your tables with ROW DEPENDENCIES will store an SCN at the row level (at a cost of about 6 bytes per row) and you can use the commit SCN to pull data.
Just another caveat though - either of those approaches will still NEVER detect rows that have been deleted. So if you need those you need yet a different approach such as using a materialized view log that captures ALL changes.

Dreamweaver CS3 crashes after Daylight Savings Time ends

In Windows XP x64, Dreamweaver CS3 crashes after
Daylight Savings Time ends. There is a technote that seems to
describe the situation exactly.
http://kb.adobe.com/selfservice/viewContent.do?externalId=kb402776&sliceId=1
However...
1) The technote says this happens only with ASP and PHP code.
I'm using ColdFusion. (That's a minor point.)
2) The technote says...
Delete the WinFileCache-AD76BB20.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
However, I coudn't find WinFileCache-AD76BB20.dat in
Documents and Settings or in Program Files (86)\Adobe. (The 86 is
because this is a 32-bit program on a 64-bit machine, but all the
rest is the same.) I then searched both directories for *.dat and
there was no file that looked anything like
WinFileCache-AD76BB20.dat.
.Can anybody help me?
Thanks!

Alan, thanks for the suggestion.
I did the search found the file, deleted it, opened
Dreamweaver CS3, selected the same text -- and it crashed as
before.
THEN I REBOOTED and tried again - NO CRASH. So it seems that
a reboot is an essential part of the fix.
BTW: My situation fit the Technote description exactly. (1)
The crash happened when selecting -- in design or code view --
certain text in a context of HTML intermingled with ColdFusion
code; (2) I had no problem with these files before Daylight Savings
ended; (3) even after that I had no problem with them in Macromedia
Dreamweaver 8 on another machine -- the problem was only on CS3.
So the Technote is correct as far as it goes, but should be
amended as follows:
1) ColdFusion should be included in the types of code that
can be associated with the problem.
2) Instead of deleting WinFileCache-AD76BB20.dat, one should
delete WinFileCache-[whatever].dat.
3) A reboot after the deletion may be required.
Anyway, problem solved.
Thank you!

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

Outlook 2011 for mac daylight savings time issue

Hello,
I have a problem in my company where after daylight savings time meetings are shown an hour off in the calendar, but in the body of the meeting the time seems fine. The real problem is when after updating the meeting from it's body (just pressing save and
close) the meeting is bloated by an hour.
E.g. if a meeting after daylight savings time is from 11:00 to 12:00, it's shown on the calendar from 12:00 to 13:00, but after updating the meeting it's shown from 11:00-13:00.
This happens only on the macs in the company.
Thank you.

Hi Harel,
This is the forum to discuss questions and feedback for Windows-based Microsoft Office client. Since your query is directly related to Office for mac, I would suggest you to post in the forum of Office for Mac, where you can get more experienced responses:
http://answers.microsoft.com/en-us/mac/forum/macoffice2011?tab=Threads
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
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]

Solaris 10 u8 system did not update daylight savings time

I am running Solaris 10 u8 x86, and my system did not update for the daylight savings time change on Nov. 1, 2009. I am in the US/Mountain time zone. What should I do?
Patch 141517-04 is installed, I assume it came with u8.
Does this have something to with JAVA Time Zone updater? I saw this:
http://java.sun.com/javase/timezones/tzdata_versions.html
Shouldn't u8 take care of all this automatically? Do I have to somehow get TZUT 1.3.20? By contacting support? What?
Any suggestions would be greatly appreciated.

BTW, I'm running 64-bit Solaris as a VirtualBox (3.0.10) guest VM on a 32-bit WinXP host.

Daylight Savings Time and Alarmsk

Since the daylight savings time updated over the weekend the alarms I had programmed on my iPhone will not set properly. The phone displays the correct current time so I know the clock has updated but any alarms I have set for the hour of 2am - 3am don't display the proper time. They keep reverting to 1-2am. I have deleted them and recreated them with the same results, on 2 different iPhones, a 4gig and an 8gig.

I see im not the only one that gets up early. v1.1.3 and updated to 1.1.4 I am unable to set the alarm to any time in 2AM (2:01, 3, 4, 5, etc..) any time set to 2AM shows 1AM in the alarm. 2PM shows fine. Any hour of the day shows fine. The error is setting a time of 2AM as it will not show that time and will revert to 1AM.
I am in a zone that uses DST.
I guess apple doesnt want us to wake up to pay the bills.
I hope someone has a fix for this before I goto bed... busting out the old alarm clock now.

Daylight Savings Time for the USA

I am trying to add a new entry for the new daylight savings time change implemented in the United States in a 4.6C system. I am trying to make the change per SAP note 919538.
The problem is when I go into transaction STZBC, and try to add a new entry for the USA, after I input what was stated in the SAP note and try to save the new entry, I receive an error "Choose the key from the allowed name space".
How have others implemented this change? I am unsure of modifying the entry that is there already for the USA since the sap note says to add a new entry.
Regards,
Doug Slupski

Hi Doug
Isn't this message informational only?? It does not show as an Error. If you hit Enter a couple of times, it should go thru...
I am not sure if it will wipe out the previous entry under the Key "USA"from the table.
Make a note of the previous values before u hit enter. After you have made the change, check if it overwrote that value.
If not, then you should be fine..If yes, chnage the value under USA to he original values and open up an OSS message.
Hope that helps..
Thanks
Abhi

2007 Daylight savings time - Oracle 9.2

Hi All,
My Oracle database runs on Windows 2000 Advanced Server. I have followed Microsoft instructions to update the Daylight Savings Time to new settings. Given this, will I need to apply Oracle patches ?
Thanks for your help,
P.

You will need to patch Oracle, check this blog for more info.
http://blogs.oracle.com/otn/stories/storyReader$367

2007 Daylight Savings Time Changes

What, if any, effects will the 2007 changes to US daylight savings time have on the operation of the LabVIEW 7 Express development environment and deployed applications created with it?

I believe the answer depends on the OS the application runs under.
If MS has there act together and the machine in question has recieved updates, there should be no issue.
If you are running Unix (or a variation o such), a patch must be applied (at least that was the story my wife gave for working all night Saturday night).
I can not answer this Q for Mac or LV-RT running under Pharlap.
Ben
Message Edited by Ben on 02-27-2007 10:24 AM
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Daylight Savings Time...Again

Similar Messages

Maybe you are looking for