Inspect the output of
SET PATH
and compare it to the registry value for
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
or, alternatively, with the content of: Control Panel / System /
Advanced / Environment Variables... / System variables / Path
Why do you use a batch file? Couldn't you just enter the command:
XCOPY source destination
into the scheduled task's "Run:" box?
Please post the exact content of the scheduled task's "Run:" and
"Start in:" boxes.
Please post the batch file here.
Are you sure the source file exists? Is it a fully qualified name?
Are you logged in when the scheduled job runs? If you are not, note
that access to network drives for scheduled jobs is problematic.
Good luck.
On Thu, 20 Jun 2002 11:17:20 -0700, "gil dering"
<gil.d...@sbs.siemens.com> wrote in
microsoft.public.win2000.cmdprompt.admin:
--
Michael Bednarek, IT Manager, Tactical Global Management
Waterfront Pl, Brisbane 4000, Australia. "POST NO BILLS"
http://mcmbednarek.tripod.com/
Yes, I can run XCOPY from directories other than System32.
I am not sure what to look for in the reference you made
to the registry . . . ??
I am using the Task Scheduler and I do not see "RUN"
OR "STARTIN" boxes. That is the reason for the ".bat"
files.
The batch file is . . .
***************
XCOPY g:\KANA\data\solutionline\knowledgebases\brain2000
d:\kana\data\solutionline\knolwedgebases\brain2000
exit
*******************
The file definately exits and is correct as I can run
the ".bat" from System32 but cannot run it when signed on
the server from the Task Scheduler.
>.
>
>Thanks for the reply . . . Answers below . . .
>
>Yes, I can run XCOPY from directories other than System32.
>
>I am not sure what to look for in the reference you made
>to the registry . . . ??
I was trying to find out whether your PATH environment variable
included system32 so that the scheduled job will find XCOPY.EXE .
>I am using the Task Scheduler and I do not see "RUN"
>OR "STARTIN" boxes. That is the reason for the ".bat"
>files.
I was referring to the properties of the scheduled task, as available
by right-clicking its entry in the Task Scheduler. They have a "Run:"
and "Start in:" box on my systems (Win4, NT5.0).
>The batch file is . . .
>
>***************
>XCOPY g:\KANA\data\solutionline\knowledgebases\brain2000
>d:\kana\data\solutionline\knolwedgebases\brain2000
>exit
>*******************
>The file definately exits and is correct as I can run
>the ".bat" from System32 but cannot run it when signed on
>the server from the Task Scheduler.
Are d: and g: local or network drives?
Are you logged at the time when the scheduled jobs are to be run?
--
Michael Bednarek, IT Manager, TGM Ltd, Brisbane, Australia
http://mcmbednarek.tripod.com/ "POST NO BILLS"
I have a bu batch file which works fine in either case..
however when Task Scheduler invokes the bu file, a CALL
from within [to copy & delete old log files], will not
execute.
This also has me stumped. Can't see any errors thrown
anywhere.
ZS
>.
>
If you can run the batch file when logged in
interactively, it might be a permissions thing...
Scheduled tasks run in the system context (unless you've
set up a specific account for the scheduler to run as), so
ensure that SYSTEM has access to what you're trying to
copy...
HTH
Alan Crowe MCSE
NT Systems Manager
Shell Information Technology International Ltd.
St. Magnus House, Guild Street
Aberdeen. AB11 6NJ.
>.
>
Ensure that the scheduled process is run as a domain user, not as the
local system account. The local system account has no network access
rights.