none
SyncToyCmd.exe produces syncronize error RRS feed

  • Question

  • Hello,

    I recently upgraded to SyncToy 2.1 from SyncToy 2.0. Since the upgrade, I have been having problems syncing the folder pairs automatically using SyncToyCmd.exe, however the Syncing is working fine from the GUI. When I attempt to sync all folder pairs using SyncToyCmd.exe -R I receieve the error below. I've tried to delete all the DAT files and resync using the GUI, but I still get the error when using SyncToyCmd.exe after doing this. The DAT files are recreated during the GUI step, but it seems the SyncToyCmd still has issues for some reason.

    SyncToyCmd has detected that the folder pair Templates - DC East has not been synchronized yet. Please run SyncToy.exe to complete the initial synchronization.
    SyncToyCmd has detected that the folder pair Templates - Dillingham has not been synchronized yet. Please run SyncToy.exe to complete the initial synchronization.
    SyncToyCmd has detected that the folder pair Templates - Markham CPG has not been synchronized yet. Please run SyncToy.exe to complete the initial synchronization.
    SyncToyCmd has detected that the folder pair Templates - Mississauga has not been synchronized yet. Please run SyncToy.exe to complete the initial synchronization.
    SyncToyCmd has detected that the folder pair Templates - Pickering has not been synchronized yet. Please run SyncToy.exe to complete the initial synchronization.
    SyncToyCmd has detected that the folder pair Templates - Regina has not been synchronized yet. Please run SyncToy.exe to complete the initial synchronization.
    SyncToyCmd has detected that the folder pair Templates - Saskatoon has not been synchronized yet. Please run SyncToy.exe to complete the initial synchronization.
    SyncToyCmd has detected that the folder pair Templates - Sudbury has not been synchronized yet. Please run SyncToy.exe to complete the initial synchronization.
    SyncToyCmd has detected that the folder pair Templates - Toronto has not been synchronized yet. Please run SyncToy.exe to complete the initial synchronization.
    SyncToyCmd has detected that the folder pair Templates - UK has not been synchronized yet. Please run SyncToy.exe to complete the initial synchronization.
    SyncToyCmd has detected that the folder pair Templates - Vancouver has not been synchronized yet. Please run SyncToy.exe to complete the initial synchronization.
    SyncToyCmd has detected that the folder pair Templates - Vancouver (Seymour) has not been synchronized yet. Please run SyncToy.exe to complete the initial synchronization.
    SyncToyCmd has detected that the folder pair Templates - WEITS102 has not been synchronized yet. Please run SyncToy.exe to complete the initial synchronization.
    SyncToyCmd has detected that the folder pair Templates - WEITS103 has not been synchronized yet. Please run SyncToy.exe to complete the initial synchronization.
    SyncToyCmd has detected that the folder pair Templates - WEITS10 has not been synchronized yet. Please run SyncToy.exe to complete the initial synchronization.
    SyncToyCmd has detected that the folder pair Templates - Winnipeg has not been synchronized yet. Please run SyncToy.exe to complete the initial synchronization.
    SyncToyCmd has detected that the folder pair Templates - Thunder Bay has not been synchronized yet. Please run SyncToy.exe to complete the initial synchronization.
    SyncToyCmd has detected that the folder pair Templates - India has not been synchronized yet. Please run SyncToy.exe to complete the initial synchronization.
    SyncToyCmd has detected that the folder pair Templates - Calgary has not been synchronized yet. Please run SyncToy.exe to complete the initial synchronization.
    
    Friday, January 22, 2010 8:45 PM

Answers

  • I found a solution!  I uninstalled SyncToy 2.1 and reinstalled it.  That's it!  No pair recreation - it just remember them.  New .DAT files were recreated in source and target directories when I ran the GUI version and SyncToyCmd then worked without complaint. 

    It seems a bit "hit & miss" though.  I wonder if it will mess up again. 

    Thx for your help Tyler
    Tuesday, January 26, 2010 6:18 PM

All replies

  • Did you run a full Sync with GUI? If not, you could try to sync all of the folder pairs first with GUI. Then if there are changes, try to use command then.


    Thanks,
    Ping
    This posting is provided "AS IS" with no warranties, and confers no rights.
    Saturday, January 23, 2010 6:08 AM
  • I've just started using SyncToy 2.1 and am getting the same "SyncToyCmd has detected that the folder pair ... has not been synchronized yet. Please run SyncToy.exe to complete the initial synchronization." messages.  The full Sync with GUI has been completed (i.e. I have used SyncToy,exe to complete the initital synchronisation) but the command line SyncToyCmd fails with the message above. 

    Log showing full sync completion followed by command line evocation failure :-

    SYNC: 01/25/2010 19:30:42:187: SyncToy run of WHS TV to NAS (\\Faustina1\Recorded TV\, \\Ba-061fe8\Public\Our Videos\) completed at 25/01/2010 19:30:42.
    SyncToy action was 'Echo'.
    SyncToy options were:
     Active for run all
     All files included
     No files excluded
     Do not check file contents
     Include read-only files
     Include hidden files
     Include system files
     Backup older files (send to Recycle Bin)
     All subfolders included
    SyncToy run took 00:00:00:093.
    Copied 0 bytes in 1 files in 00:00:00:93.
    Bytes per second 0.0, files per second 10.7.
    Avoided copying 3,234,681,288,960 bytes in 1,298 files that did not require action.
    Saved approximately 21:02:42:00 by not copying all files.

    SYNC: 01/25/2010 19:31:06:718: -------------------------------------------------------------------------
    SYNC: 01/25/2010 19:31:06:718: Starting SyncToyCmd, version 2.1.0.0, built 19/10/2009 03:58:16.
    SYNC: 01/25/2010 19:31:06:781: *** SyncToyCmd has detected that the folder pair WHS TV to NAS has not been synchronized yet. Please run SyncToy.exe to complete the initial synchronization.

    • Edited by WonkyBass Monday, January 25, 2010 7:34 PM
    Monday, January 25, 2010 7:28 PM
  • Ping,

    Yes I've run a full sync using the GUI. This does not help, I still get the error seen above. It looks like this may be an issue with the new version, as the person above (WonkyBass) appears to be having the same problem also.
    Monday, January 25, 2010 7:31 PM
  • I recreated my folder pairs from scratch and now all is working.
    Tuesday, January 26, 2010 1:11 AM
  • I'm pleased Tyler has been able to overcome this by starting from scratch.  My SyncToy pair is for 1.5 TBytes (651 files in a single folder) of TV programs and takes days to initially synchronise.  Starting again without understanding what the cause of the problem was and whether it will reoccur is not the best answer for me.
    Tuesday, January 26, 2010 12:44 PM
  • I understand our frusturation, it took me over an hour to recreate all the pairs, but its working now so the time was worth it. I could not wait for another fix as I am actually using this tool for pushing our templates to all offices across the country.
    Tuesday, January 26, 2010 4:31 PM
  • I found a solution!  I uninstalled SyncToy 2.1 and reinstalled it.  That's it!  No pair recreation - it just remember them.  New .DAT files were recreated in source and target directories when I ran the GUI version and SyncToyCmd then worked without complaint. 

    It seems a bit "hit & miss" though.  I wonder if it will mess up again. 

    Thx for your help Tyler
    Tuesday, January 26, 2010 6:18 PM
  • SyncToy wasn't really working for me, particularly as I was trying to use it to synchronsise Windows Media Center TV programs that have "Date Modified" that are updated each time they are browsed from Windows Media Center. The changed date field caused SyncToy to unnecessarily copy files which were otherwise identical and this does not appear to be configurable. I have therefore implemented RichCopy instead which seems to do what I want.
    Wednesday, January 27, 2010 10:57 PM
  • I am sorry to hear that synctoy could not accomplish your scenario.
    But it is good to know, you guys could solve the initial sync problem. :)


    Cheers,
    Ping
    This posting is provided "AS IS" with no warranties, and confers no rights.
    Saturday, February 20, 2010 8:31 AM
  • I had a similar issue until I realized that I was recreating the pairs as 'Echo' or 'Contribute', following a reinstallation on new hardware platform. It seems that when creating a pair you MUST run it as 'synchronize' first. Once run you can then change the method to either 'echo' or 'contribute'. If you do not carry out an initial 'synchronize' it seems that synctoycmd reports that synchronize has not been carried out.
    Saturday, October 31, 2015 7:37 AM