The fact you have to stay logged on for it to successfully run indicates
there's something fundamentally wrong with the task (mapped drives, etc.)
Scheduled Tasks|Advanced|View Log may provide some details. If the job
connects to another machine you may need to add the user/ group 'logon as
batch job' rights (server side). Control Panel|Admin Tools|Local Security
Policy\Local Policies\User Rights Assignments
"Log on as a batch job"
If the task completes but the job does not then there is a problem in the
job itself. Remember that if it involves network resources to make sure the
user account has permissions to the resources and also use UNC paths as
mapped drives won't natively exist when no one is logged on.
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows] http://www.microsoft.com/protect
> I have a scheduled task running overnight on Windows Server 2003. The
> administrative user that configures and "runs" this task remains logged
> the server, so that the task successfully runs. And, this task has run
> successfully every night for months.
> Over the last two nights, ithough, it has not run. I do not know why nor
> are the logs mentioning anything pertinent as usual.
> Any ideas as to why? The task runs a .cmd (macro) file. When I run this
> file by itself, it runs perfectly. It's just that I cannot get the
> Task to run.
> I recreated the task, stopped and started SQL, and stopped and started the
> Task Scheduler service.