E
Eoin Verling
Hi,
I'm running Windows 2000 server, SP2 at the moment. I'm trying to
schedule commands (backups mostly!) with the at command.
I've created a simple "file.cmd" file, that stops a DB service, copies a
DB file, and starts the service again. If you run the file from the
command line, it works fine.
I use the "at" command:-
at hh:mm cmd.exe /c "C:\directory\bin\file.cmd"
I immediately get a response:-
"The system cannot find the drive specified"
... and the script does not run at the specified time! If I type "at"
after is has supposed to run, I get a listing of the job, with an
"Error" in the status field.
any clues as to what's going on?
I've tried patching the system to SP4, but there's some other error, I
may have to re-install the machine. It's a production server though, so
I don't want to do that yet really.
cheers
E
I'm running Windows 2000 server, SP2 at the moment. I'm trying to
schedule commands (backups mostly!) with the at command.
I've created a simple "file.cmd" file, that stops a DB service, copies a
DB file, and starts the service again. If you run the file from the
command line, it works fine.
I use the "at" command:-
at hh:mm cmd.exe /c "C:\directory\bin\file.cmd"
I immediately get a response:-
"The system cannot find the drive specified"
... and the script does not run at the specified time! If I type "at"
after is has supposed to run, I get a listing of the job, with an
"Error" in the status field.
any clues as to what's going on?
I've tried patching the system to SP4, but there's some other error, I
may have to re-install the machine. It's a production server though, so
I don't want to do that yet really.
cheers
E