scheduler fails on mapped drives

  • Thread starter Thread starter Adam SK
  • Start date Start date
A

Adam SK

I'm using the scheduler service to run a batch file that
resides on a mapped drive. If I set the scheduler to run
the batch file in a couple of minutes, I can stand back
and watch it work. However, it fails to run when it's
supposed to at night. I suspect it is because the batch
file is on another computer on the network and the mapped
drive falls asleep. Can anyone confirm this as a
potential problem? Any solution?
 
Is there any reason you can't put the batch file on the local PC? If it
still relies on the remote PC for processing you could always start the file
with:

net use <driveletter>: /d
net use <driveletter>: \\servername\sharename

Where you would replace <driveletter> with the mapped drive letter, and
\\servername\sharename with the name of the shared folder/drive the process
needs to run from.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top