scheduling a job on 2000 server URGENT !

[viztek]

hello ,

This is Vztek.
I want to schedule a batch file to be run on Windows 2000 server. for this i use the task scheduler and schedule my tasks as
at /delete /yes
at 18:00 /every:M c:\backup_scripts\faps_backup_M.bat

but at the desited time it does not run.
i have checked the task scheduler service.

the at command gives the task.
But still it does not run automatically.

When i doubleclick the batch file it runs.

Please help.

Viztek

 

[hads]

If you are using Windows 2000 then there is a Task Scheduler - is there a reason you cannot use that?

 

[viztek]

Task scheduler shows the task as schedules.
at command gives the task. but doesnt run(batch file) at the desired time.

 

[peterve]

maybe a dumb question :
is the scheduler service running (it should be running on the local system account) ?
Is the task enabled (in task scheduler) ? ---------------------------------------------------------------------
I have not failed, I've just found 10,000 ways that don't work
---------------------------------------------------------------------
Peter Van Eeckhoutte
peter.ve@pandora.be
*:->* Did this post help? Click below to let me know !

 

[viztek]

task scheduler is running fine let me know the procedure how one could schedule a batch file to run in windows 2000 at a scheduled time.

Viztek

 

[jjgraf]

Check security and see if the system account has access to those resources which would keep it from running. Allso you can have a task in W2K login as a different user so it get the security access without turning system account into all powerful user.

I have task which backups the network and it logs in as Domain Admin with out changing th the Scheduler service login.

to schedule a task do the following
go into Control panel then to Schedule Tasks then Double click on Add Scheduled Task follow the wizards instruction and you also can change the log in from there.

 

[rjbj]

I have found that there are some batch files that need to be placed on the root drive in order for them to run as "Scheduled tasks." Another thing that could be wrong, if you recently changed the password of the account you use to run this task but did not EDIT the task to reflect the password change, it also will not run as a scheduled task but work fine is you manually run the task. Hope all this makes sense.

 

[vesselescape]

For Viztek
The old NT 'at' command still exists in 2k but has some changes and differences. 2k prefers you use the gui "task scheduler" (start>accessories>system tools>task scheduler) Open the interface and click 'add scheduled task'
Enter path to batch file or other executable. If a batch file, best to enter a working directory as well. Batch or executable must reside on machine that task scheduler is running on.
If you use the "browse" function in the dialog, path and working directory will be entered for you. Next screens allow you to enter basic scheduling information, daily weekly etc.
You can specify addition parameter under 'properties.advanced' dialog after the initial entry is created. Next screen is run as user...default is the logged on user creating the task. Most of our scheduled tasks run as the stystem administrator. Make sure password matches user! In next box check open advanced properties. Under the security tab, make sure the account the scheduled task is running under has 'full control' of the file. Click "apply" and the task should now show up. Left click task, and click "run". Task should run with an exit code of 0x0 if it completed ok. If not, click "view log" under tools. Check the log entry for any additional information. If log does not give enough info to find the problem, try running the batch file from the command line rather than from a gui. The cmd window will stay open after the batch runs (or trys to) and will give you additional troubleshooting info.
The above scenario is used to run a number of batch files on our system, both from the DC and standalone rras/nat servers for various backup, upload and download functions, as well as UPS shutdown etc. Hope it helps.

For Alpesht
We had a number of problems running scheduled shutdowns and reboots via any means including task scheduler. We finally opted for a commercial product pointed to in thread96-432202. Solved all the problems and confusion, added several useful functions, and was cheap.
30 day trial available for up to 100 client license.

We have no affiliation with this company, just found that it worked for us.