• Task scheduler job is failing due to

    From Srikant Patil@21:1/5 to All on Wed May 27 06:01:50 2020
    Hi Folks,

    I have created a powershell script to copy files over network using robocopy utility.

    The script works fine manually without mapping a drive but it fails when i use task scheduler to run that job.

    After mapping the drive the script started working but i don't want to map a drive.

    Is there any other option to copy files over network using a specific user credentials?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Charlie Hoffpauir@21:1/5 to srikant.madhukar.patil@gmail.com on Wed May 27 09:10:00 2020
    On Wed, 27 May 2020 06:01:50 -0700 (PDT), Srikant Patil <srikant.madhukar.patil@gmail.com> wrote:

    Hi Folks,

    I have created a powershell script to copy files over network using robocopy utility.

    The script works fine manually without mapping a drive but it fails when i use task scheduler to run that job.

    After mapping the drive the script started working but i don't want to map a drive.

    Is there any other option to copy files over network using a specific user credentials?

    I have a task scheduled to back up my data overnight to a networked
    NAS unit. It's a simple Robocopy script, and it works fine. Perhaps
    the problem is you haven't set the task properly? The structure of the
    Robocopy script is:
    Robocopy B:\ \\NAS-name\home\GB\B-backup /MIR /R:1 /W:1 /A-:S /A-:H

    (where home\GB is the location set up on the NAS)

    repeated for each disk to be copied.
    These are all included in a *.bat file, called from the task
    scheduler.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tom@21:1/5 to All on Wed May 27 23:18:58 2020
    there should be no need to map a drive.
    could you post your code so one could check what is going on.
    please anonymize any personal or company related information.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)