Re: scheduled task can not access shared drive
- From: "Pegasus \(MVP\)" <I.can@xxxxxxxxxx>
- Date: Sun, 4 May 2008 07:35:12 +0200
"powdered_toast_man" <powderedtoastman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:81D01B94-2218-45CA-99C3-8E2883898004@xxxxxxxxxxxxxxxx
This is actually on a Windows 2003 server but I didn't see it among the
options.
I've created a batch file on server A to generate a report and copy it to
a
shared drive on server B. When I log onto server A and run the batch file
it
works; when I use the task scheduler to run the batch it fails. A coworker
suggested using the unc path rather than the mapped drive letter
designation
but that didn't help - all that did was generate a "CMD does not support
UNC
paths as current directories" error message.
I have a hunch that the problem is because the shared drive is not
recognized unless the user physically logs onto the box. Is that the case
and
is there a way to work around this?
Let's have a look at your batch file!
What account do you use for the scheduled task? Does it have access
to the shared resource?
About newsgroups: There are several with the word "Server" in it, e.g.
"windows.server.general".
.
- Follow-Ups:
- Re: scheduled task can not access shared drive
- From: powdered_toast_man
- Re: scheduled task can not access shared drive
- References:
- scheduled task can not access shared drive
- From: powdered_toast_man
- scheduled task can not access shared drive
- Prev by Date: scheduled task can not access shared drive
- Next by Date: Re: scheduled task can not access shared drive
- Previous by thread: scheduled task can not access shared drive
- Next by thread: Re: scheduled task can not access shared drive
- Index(es):
Relevant Pages
|
Loading