FIX SyncToy 1.4 Exception FIX

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

The SyncToy exceptions are caused by the 1.4 installer placing files into a
different directory than the 1.1 and 1.2 installers. Scheduled Tasks created
with 1.1 and 1.2 point to the outdated files, which are trying to run with
the data files created by 1.4 in MyDocs/SyncToy. The fix is listed below.
Its cut from another thread.

-owen


I noticed that the exception lists version 1.2 of the SyncToyEngine.dll
(1.1
in your case paul). I checked the path of SyncToy from my Start Menu, the
one placed here by the 1.4 installer, and noticed it points to
C:\Documents and Settings\USERNAME\Local Settings\Application Data\SyncToy\

The previous install, SyncToy 1.2, placed SyncToy in
C:\Program Files\Microsoft\SyncToy

The files there were not updated by the 1.4 installer, and hence the
scheduled task was trying to run with version 1.2, and using the data files
created by SyncToy 1.4.. bad news. I simplied copy the contents of the first
folder in LocalSets\AppData\Synctoy to the progfiles\synctoy directory, and
my scheduled tasks ran as they should without errors or corruption.

-owen
 
Nice one Owen. I suspected something similar but Windows search didn't find
the new copy. Your post solved my problem.

Thanks,

Andy
 
I guess there can be a lot of different exception errors - unfortunately this
does not fix 'system.objectdisposedexception' when the completed SyncToy run
is closing in a scheduled task in MCE2005! It breaks MCE2005 which no longer
geos back to sleep and requires a full re-boot after every crash! Not very
friendly...
 
To clarify, the installation directory fix was used to fix the following
exception.

************** Exception Text **************
System.ArgumentOutOfRangeException: Ticks must be between
DateTime.MinValue.Ticks and DateTime.MaxValue.Ticks.
Parameter name: ticks


It apparently does NOT fix the following exception
system.objectdisposedexception
 
Back
Top