Re: Scheduled tasks copied between servers often do not run

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

When I said there was no log entry, I mean that literally, nothing appears
in the log for the task until it is run manually.
It is not a claim, and it is not guesswork.
The tasks just do not run and there is no record.
We take a daily copy of the scheduler's task log to avoid the 32k
wrap-around.
Each of the tasks records its own log if started. They were never started.

Once they have been run manually the first time, they schedule normally
thereafter.
Approximately 70% of the tasks so far copied in the manner described do not
start on the first day,
on the next day etc until run once. Detailed inspection of the task
properties using the little
Microsoft Tasks utility (cannot remember its name) shows nothing out of the
ordinary.
The properties on the target machine replicate those on the source machine.

This problem has applied to tasks copied from 4 different servers with
different images, to 4 different servers
two of them with different images, so it is not an isolated problem but
generic in our installations.

Thank you for your reply.

"Pegasus (MVP)" <I.can@xxxxxxx> wrote in message
news:uSPnft$wGHA.324@xxxxxxxxxxxxxxxxxxxxxxx
See below.

"Greg" <Greg@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:14AC4AF4-F1B8-4AD2-B3AD-D30C94FD724A@xxxxxxxxxxxxxxxx
(Sorry, misposted in 'Accessibility')
After copying tasks between servers and applying passwords, the copied
task
often does not run on the target machine.
*** How can you tell?

It seems the scheduler simply does not see the task until it has been
manually run once.
*** This is incorrect.

There is no status message and no entry in the log to indicate any cause,
and the last run/next run times never change.
*** Which log?

We are migrating nearly 200 tasks from old servers to new servers, and
cannot just run these tasks at anytime to force them to run automatically
thereafter. The scheduled tasks run-times are distributed over 24 hours

The method used to copy the tasks is:
1. RDP to the old server and copy the tasks to a network folder using
drag
and drop in Windows Explorer
*** That's fine.

2. RDP to the new server, drag and drop tasks into C:\Windows\Tasks.
(Occassionally Windows Explorer crashes when pasting, but tasks
still
arrive
*** This is of concern.

3. Apply passwords.
4. Wait and hope!
*** You can do much better - see below.

Can anyone propose a solution or point to a problem ticket somewhere?

XP 2003 Pro, SP2


So far you claim that some tasks do not run appears to be
largely based on guesswork. To be sure you MUST inspect
the Task Scheduler's log file. You should also embed your
scheduled task into the batch file below, then examine its
log file. I suspect that it will reveal a lot!

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




.

Relevant Pages

  • Re: Scheduled tasks copied between servers often do not run
    ... After copying tasks between servers and applying passwords, ... The scheduled tasks run-times are distributed over 24 hours ... the Task Scheduler's log file. ... echo %date% %time% Start of task> c:\test.log ...
    (microsoft.public.windowsxp.general)
  • Re: Scheduled tasks copied between servers often do not run
    ... log file, then modify it to run the tasks that YOU want to run. ... echo %date% %time% Start of task> c:\test.log ... Once they have been run manually the first time, they schedule normally ... different images, to 4 different servers ...
    (microsoft.public.windowsxp.general)
  • Re: Scheduled Tasks Problem
    ... domain administrator account. ... application still fails to start when done via scheduled tasks. ... echo %date% %time% Start of task> c:\test.log ...
    (microsoft.public.win2000.general)
  • Re: Scheduled tasks not running
    ... If your system partition is a FAT32 ... As it turns out for some reason all my scheduled tasks had dropped their ... The article says that "Scheduled tasks maintains a log file ... echo This task ran on %date% at %time%>> c:\Test.txt ...
    (microsoft.public.windows.server.general)
  • Re: Scheduled tasks not running
    ... with no ultimate success in getting any of my scheduled tasks to run. ... The article says that "Scheduled tasks maintains a log file ... You can view the scheduled tasks logs from within the Task Scheduler ... echo This task ran on %date% at %time%>> c:\Test.txt ...
    (microsoft.public.windows.server.general)