Task Scheduler problem after SP4

[Tom Boykin]

Since upgrading to Windows 2000 Service Pack 4, some of
the jobs submitted to the Task Scheduler do not run. When
checking the status of the jobs that did not run at their
given time, the job indicates a status of "could not
start". After much research, found that the jobs that
would not run under Task Scheduler were submitted without
a file extension (i.e. .exe). Those jobs that did run had
their file extension included. The same jobs ran without
any problems prior to updating to Service Pack 4. Is
there a patch to resolve this issue or a registry setting
for Task Scheduler that can resolve this problem?

 

[Pegasus \(MVP\)]

Since upgrading to Windows 2000 Service Pack 4, some of
the jobs submitted to the Task Scheduler do not run. When
checking the status of the jobs that did not run at their
given time, the job indicates a status of "could not
start". After much research, found that the jobs that
would not run under Task Scheduler were submitted without
a file extension (i.e. .exe). Those jobs that did run had
their file extension included. The same jobs ran without
any problems prior to updating to Service Pack 4. Is
there a patch to resolve this issue or a registry setting
for Task Scheduler that can resolve this problem?

In view of the many types of extensions that are permissible under
Win2000, it's probably a good idea to always include file extensions.
(.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH)