at not working. 1

[bigscouse]

Can any onr help?<br>
I have started the schedule service but when I issue jobs with the at command they do not run. The jobs are scheduled correctly as I have listed by typing at with no parameters. A sample command I have tried is: -<br>
at 09:25 "cmd /c ged.bat" <br>
where ged.bat contains 'dir &gt; c:\test/log'<br>
<br>
Thanks.

 

[duncan]

Your first source of information here is the event log, also I would recommend the resource kit's scheduler. It does the same thing but with a graphical interface and some validation of your schedule. Essentially it is necessary to srew around with it until it does work.<br>
<br>
duncan

 

[PCReese]

Just a thought, I found you should stop and restart the schedule service anytime you make a change to a job. Other wise the new entries wont fire off at the expected time.

 

[AntsMac]

Try...<br>
at 09:25 /INTERACTIVE cmd /c ged.bat<br>
<br>
This will run cmd with the logged on users rights. Without the /INTERACTIVE switch the command runs with system rights which doesn't have the right to launch batch jobs.<br>
<br>
<br>
Ants<br>
<br>

 

[SRG]

Just another suggestiong try checking the service account ID make sure that the at service has the apprtopraite rights to run the program, (I am guessing that this is not your final application). <br>
<br>
at 9:25pm get.bat<br>
<br>
loose the cme and quotes etc. and unless it needs to interact with the desktop you should not need /interactive.<br>
<br>
Note when using at or soon to schedule programs to a remote NT machine you must have admin right to the remote machine.<br>
<br>

 

[GeorgiaRebel]

Just to emphasize what SRG said....<br>
When running BAT/CMD files through the scheduler, the NT Scheduler service should be started with an ID that has appropriate rights to run those files. Otherwise, they (in many cases) will not run.<br>
<br>
Also, use the NT Resource Kit's "Command Scheduler" instead of the command line. The GUI interface makes setting things up a LOT easier.