none
SynchToy 2.0 does not run using scheduled tasks RRS feed

  • Question

  •  

    When I try to run synctoy 2.0 trough scheduled tasks I get an "Invalid option" pop-up and "The ability to execute folder pairs from the commandline (-R option) is now available from synctoy.exe, when the scheduled time arrives.  I tried addint the folder pair after the -R option and I still get the same error.
    Friday, February 22, 2008 2:03 PM

Answers

  • Thanks Liam, found the problem.  I was pointing to SyncToy.exe and needed to point to SyncToyCmd.exe.  Seems to run fine now. 

     

    Friday, February 22, 2008 6:47 PM
  • Liam - I experienced a similar problem with SynchToy not running as a scheduled task, and others may experience the same problem.  When I upgraded from the Beta version I forgot to change the address from SynchToy Beta 2.0 to SynchToy 2.0 in the Scheduled Task address.  A rookie oversight, but one that's easy to make.  Great product, keep up the good work. - Dave

    Monday, September 22, 2008 5:23 PM

All replies

  • Can you send us the exact command line that you are using?  Are you certain that it is finding the 2.0 SyncToyCmd.exe?  Also, if you go to the SyncToy directory and run this command (outside of your scheduled task) does it work?

     

    Friday, February 22, 2008 5:04 PM
  • Thanks Liam, found the problem.  I was pointing to SyncToy.exe and needed to point to SyncToyCmd.exe.  Seems to run fine now. 

     

    Friday, February 22, 2008 6:47 PM
  • Liam - I experienced a similar problem with SynchToy not running as a scheduled task, and others may experience the same problem.  When I upgraded from the Beta version I forgot to change the address from SynchToy Beta 2.0 to SynchToy 2.0 in the Scheduled Task address.  A rookie oversight, but one that's easy to make.  Great product, keep up the good work. - Dave

    Monday, September 22, 2008 5:23 PM
  • Thanks for pointing that out.

     

    Liam

     

    Monday, September 22, 2008 8:15 PM
  • Hi Liam, i'm still running on 32bit system. The 32 bit version software is having the same issue. I've downloaded the most up-to-date software. The problem is still there. Thanks in advance.

    I found the problem, that i wasn't executing the CMD software, i was running the GUI software :P

    • Proposed as answer by D_Kan Monday, April 20, 2020 5:09 AM
    • Edited by D_Kan Monday, April 20, 2020 5:11 AM Found solution
    Monday, April 20, 2020 5:06 AM