Scheduled Jobs on DS One Hour Late after DST
matthilt
March 9th, 2009
This morning I noticed that all of my scheduled jobs on my DS's were scheduled one hour later than they were when we first set them up (Example: Backup job that was scheduled to run at Midnight every day, now runs at 1am everyday). This change happened over the weekend I'm assuming because of DST. I looked in the Altiris KB and found KB 18061, https://kb.altiris.com/display/1n/kb/article.asp?aid=18061&n=4&s=, but that only applies to 6.1, 6.2, and 6.5 and we're running DS 6.9 SP1. I'm running the DS on Server 2003 that is up to date on patches.
Am I the only one that has noticed this? Does anyone have a fix other than manually resetting all of the jobs? Thanks.
Matt Hilton
I'm having a similar issue
I'm having a similar issue right now, but I'm confused by it.
My client computer has the right time and time zone. My server has the right time and time zone.
If I schedule a job to run right now or use "Start Now" it won't work. But if I put the job at least 1 hour in the "past" then it will run perfectly fine.
RE: Scheduled Jobs on DS One Hour Late after DST
I had the same issue, however, the SQL server was the culprit. Once I applied the patches from http://support.microsoft.com/kb/931975 my issue was addressed.
An easy way to tell if the SQL is at fault execute the following sql query:
select getdate()
Compare the time with your server.
nelo
Doesn't appear to be SQL =/
I just did select getdate() on the server and the date/time is exactly the same as what is in Windows. But jobs are still running an hour off.
I've still not made any
I've still not made any progress on this, what I did find out though. Is if I move the date to 3/15 at 8am all jobs run immediately after scheduled. Which I find odd, since Chile/Brazil/Antartica are the only locations that changes to DST on the 3rd week of March.
Found out and verified with
Found out and verified with my Symantec Rep that certain "one off" versions of axengine.exe has this DST issue. Looks like time to up our SP1/MP1 implementation.
Call support
Support is handling these incidents on a case by case basis. Give them a call if you are experiancing this issue.
Would you like to reply?
Login or Register to post your comment.