Scheduled NTBackup can't run

[Guest]

NTBackup is created in the scheduler with /UM added to the command line.
It's being run under the administrator account and prior to enabling the job
the password is added in the run as dialog. The first scheduled backup occurs
successfully. Subsequent scheduled times occur but the job doesn't start, the
scheduler entry reads, job couldn't start. The log shows success for the
first run of the job and then errors for others, stating that the run as
account couldn’t log on because of invalid account or password.
Either
1. The log message must be bogus, due to the fact that the first time the
job ran.
2. Or does the job loose the authentication information after the first
iteration?
3?

 

[Pegasus \(MVP\)]

NTBackup is created in the scheduler with /UM added to the command line.
It's being run under the administrator account and prior to enabling the job
the password is added in the run as dialog. The first scheduled backup occurs
successfully. Subsequent scheduled times occur but the job doesn't start, the
scheduler entry reads, job couldn't start. The log shows success for the
first run of the job and then errors for others, stating that the run as
account couldn't log on because of invalid account or password.
Either
1. The log message must be bogus, due to the fact that the first time the
job ran.
2. Or does the job loose the authentication information after the first
iteration?
3?

runas.exe is an interactive program. You cannot run it as a
scheduled job, because there is nobody to type in the password.

The standard way to run backup jobs is to specify an appropriate
account/password when scheduling the job under the Task
Scheduler.

 

[Guest]

The job was run from the scheduler, which had a field (and resulting dialog)
for account to run as. The fact that the job ran the first showed that it
got logged in as a detached process the first time. Sorry for the confusion.
Thanks for the suggestion. Any other ideas?

 

[Pegasus \(MVP\)]

Use the following batch file to build up things. Run it a few
times with the two "rem" statements in place, to build up
your confidence that the Task Scheduler works as it should.
Now remove the "rem" statements and see what happens.
Remember to examine the two log files after each run.

@echo off
echo %date% %time% Start of task > c:\test.log
echo User=%UserName%, Path=%path% >> c:\test.log
rem c:\winnt\system32\ntbackup /.. /.. /.. 1>>c:\test.log 2>c:\test.err
rem echo ErrorLevel of c:\Tools\YourTask.exe=%ErrorLevel% >> c:\test.log
echo %date% %time% End of task >> c:\test.log