Windows Forum

Ask something
Discussion Locked

Why is SOON.EXE off by an hour?

0 helpful
4 replies

by lakespringer

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

SOON.EXE started scheduling jobs for 1 hour earlier than they should be after Daylight Savings Time came into effect on Sunday. So executing "SOON 30 sample.exe" at 10 AM executes AT 9:00:30 sample.exe. This is true when executing from my server machine through SQL Server's xp_cmdshell. But if I execute interactively to run on my server, ala "SOON \\myserver 30 sample.exe" at 10 AM it executes "AT \\myserver 10:00:30 sample.exe" correctly.

The obvious place to look is the "Adjust for Daylight Savings Time" box in the Time Zone tab of Date/Time applet. But these are set correctly for all of our servers. We do use NTPDATE to keep the clocks in synch on all our servers.

Have checked MS KB articles to no avail. Any ideas out there?

4 replies

by pbgerrard

Check the BIOS time. If it is set correctly, it appears that the program is set to notify of an event half an hour in advance. Check the settings. Perhaps it has its own time setting somewhere hidden away. Check that. If none if these ideas work, then you could always set the time on the servers ahead half an hour.

by lakespringer

As suspected, SOON.EXE is working correctly again after April 8, just as Dr. Gui said it would...

This discussion is closed to new replies.