Error running scheduled task, Windows Server 2008

Discussion in 'Windows Server' started by Joe Grover, Oct 10, 2008.

  1. Joe Grover

    Joe Grover Guest

    I am setting up a new fileserver on a Windows Server Standard 2008 machine.
    The machine is currently running in evaluation mode. I installed it on

    On our existing fileserver we have a data replication script that copies
    data from remote office fileshares to the local system for backup every
    night. I have copied the script to the new fileserver, making one change to
    the path (the target for copied files is on the C: drive instead of the D:
    drive now). Here is the script:

    robocopy \\\share c:\datamirrors\AA /R:3 /MIR > AA.Log
    robocopy \\\share c:\datamirrors\GR /R:3 /MIR > GR.Log
    robocopy \\\share c:\datamirrors\TC /R:3 /MIR > TC.Log

    robocopy \\\c$\db-backup c:\datamirrors\Kaseya\db-backup /R:3
    /MIR > Kaseya.Log
    robocopy \\\c$\kaseya c:\datamirrors\Kaseya\Kaseya /R:3 /MIR >>

    - Both the old and new fileservers are members of the domain, as are the
    remote fileservers
    - The script on both servers is configured to use the domain admin account
    - If I manually run the script from the new fileserver, it starts running
    - If I create a scheduled task to run the script, it fails with error 0x10

    Any help is appreciated. I'd really like this script to run on a schedule.
    Joe Grover, Oct 10, 2008
    1. Advertisements

  2. Joe Grover

    Joe Grover Guest

    As an update, the script runs fine if I don't have it go to a log file. I
    tried using the /LOG command (changing > AA.log to
    /LOG:"c:\datamirrors\aa.log") and it worked as well.

    I've updated the script with this information (using /LOG+ for the kaseya
    log that we append to) and it seems to be working fine.
    Joe Grover, Oct 10, 2008
    1. Advertisements

  3. Your script probably ran all along but you were looking at the wrong log
    files. When running batch files then it is highly recommended to fully
    qualify all file names with drive and folder names. When running scheduled
    tasks then it is compulsory. Your output file are "TC.log" and "Kaseya.Log",
    with no drive or folder stated. Where should the scheduled task locate this

    Have a look in c:\windows\system32. You'll be pleasantly surprised!
    Pegasus \(MVP\), Oct 10, 2008
  4. Joe Grover

    Joe Grover Guest

    Yeah, I thought about that, but there was nothing there. The script would
    never run with the "> filename.log" statement in it. If I set it to run a
    minute from now and watched it, it'd just change to "last ran at XX:XX" with
    a "Last Run Result" of 0x10, which from everything I could find was pointing
    to a permissions issue.

    If I took the log statements out and set it to run a minute from then, it'd
    start running just dandy. I wasn't actually using the log files to
    determine if it ran, but the Modified date of the folders themselves (each
    office always has updated files to copy), and they hadn't been modified
    since 10/7/2008 (the day I mirrored the data from the old fileserver to the
    new one).

    Apparently the 2003 box was much more tolerant of that logfile syntax (the
    previous admin used that output just because it was normal script syntax,
    and not robocopy-specific) and always worked, so I didn't think of changing
    it when I copied it all over to the 2008 box. Ah well. Now I know (and
    knowing is half the battle).

    (Yo) Joe
    Joe Grover, Oct 10, 2008
  5. If the account used for the scheduled task has full access to the log file
    then it makes no difference to the task whether you redirect its output to a
    file or not. The task does not even know where the output goes - it only
    sees a device to which it sends it data stream.
    Pegasus \(MVP\), Oct 10, 2008
    1. Advertisements

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 (here). After that, you can post your question and our members will help you out.