Even after hangs or failures, has anyone developed a way to ensure that, after re-starting, MS will run the proper reiterative scripts at the correct times, instead of picking a time itself?
It's also possible that I just don't know how to use the advanced section of the "Run When" part of the scripts' properties.
How to: Make scripts start at the correct time every day?
Moderators: Dorian (MJT support), JRL
-
- Newbie
- Posts: 6
- Joined: Tue Sep 16, 2003 2:22 pm
- Contact:
Armstrong,
Type the following in a command prompt window:
AT /?
However, to the original poster - can you clarify the problem? The built in scheduler should have no problem keeping the script running to the defined schedule.
Type the following in a command prompt window:
AT /?
However, to the original poster - can you clarify the problem? The built in scheduler should have no problem keeping the script running to the defined schedule.
MJT Net Support
[email protected]
[email protected]
4 Armstrong (and to whom it may concern)
Click the following link to see more about: Windows NT commands
Click the following link to see more about: Windows NT commands
Similar problem with scripts starting at the correct time.
I've run into a similar situation and would like to know if anyone else has run into this. Also can Support reply to this as it appears to be a bug in the reset process.
This problem occurs when rebooting a PC running Macro-scheduler (vs 7.2.036). A number of the macro-start times are not correct for scripts which repeat throughout the day.
The script runs daily from 00:15 to 23:30 M-F repeating every 10 min. Resets after 23:30. This runs on W2000 server.
The scenario is as follows:
- On saturday morning by 5:30am the scripts had reset themselves (or at least from the outside it appears all is OK) Friday night at 23:30
- the PC is rebooted at 5:30 AM Sat morning.
After the reboot, the start time for the scipt on Monday is 14:00 instead of 00:15. This occured with 10 or so scripts.
Has anyone else seen this? It seems that MS is very sensitive in this area. I have opened a script in editor just to make a copy of it for another script. This is done during the day prior to the reset time. This can have the same effect. The next day you find out that the script will start at about the same time you opened it up in editor.
If you don't touch the script - it's reliable and works all week starting, stopping at the correct time. If you don't reboot on Saturday, all is well and it will start Monday AM at 00:15
( As a work-around, I created a script2 to run at 00:20 each day. It looks for the existance of the Script1.log file and if doesn't find it- sends out a warning email. Someone has to reset times manually. Also, you have to delete the log file at 23:58 so the prior day's log is not there when new day starts)
This problem occurs when rebooting a PC running Macro-scheduler (vs 7.2.036). A number of the macro-start times are not correct for scripts which repeat throughout the day.
The script runs daily from 00:15 to 23:30 M-F repeating every 10 min. Resets after 23:30. This runs on W2000 server.
The scenario is as follows:
- On saturday morning by 5:30am the scripts had reset themselves (or at least from the outside it appears all is OK) Friday night at 23:30
- the PC is rebooted at 5:30 AM Sat morning.
After the reboot, the start time for the scipt on Monday is 14:00 instead of 00:15. This occured with 10 or so scripts.
Has anyone else seen this? It seems that MS is very sensitive in this area. I have opened a script in editor just to make a copy of it for another script. This is done during the day prior to the reset time. This can have the same effect. The next day you find out that the script will start at about the same time you opened it up in editor.
If you don't touch the script - it's reliable and works all week starting, stopping at the correct time. If you don't reboot on Saturday, all is well and it will start Monday AM at 00:15
( As a work-around, I created a script2 to run at 00:20 each day. It looks for the existance of the Script1.log file and if doesn't find it- sends out a warning email. Someone has to reset times manually. Also, you have to delete the log file at 23:58 so the prior day's log is not there when new day starts)
Bill Ault
Cargill Investor Services, Inc.
Chicago, IL
312-460-4000
Cargill Investor Services, Inc.
Chicago, IL
312-460-4000