none
SyncToy 20B Exception:Value does not fall within the expected range. RRS feed

  • Question

  • When triyng to backup my "Documents and Settings" (My Documents, Desktop and a user directory), SynkToy stops whith the errot:
    Exception during run: Value does not fall within the expected range.

    Nothing is written to the event log or to the syncToy log about the error.

    Two directory pairs, instead, works correctly, My Mozilla profiles and my big user data directory (17 GB) outside "Documents and Settings".

    How can I ubnderstand the cause of the error?
    Thursday, June 26, 2008 5:10 PM

All replies

  • Similar issue: SyncToy 2.0B on XP Pro SP2.

    On large number (>1300) of files and directories, get "Exception during run: Value does not fall within the expected range" error. Log file only shows preamble with preview info. Nothing more.

    During the run, the status bar in the results window shows this sequence of messages:

    Looking for changes

    Adding an action

    98% done copying <filename>

     

    Any suggestion where to start looking further?

     

    -EM

    Tuesday, July 1, 2008 1:28 PM
  • I'm getting the same "Exception during run:  Value does not fall within the expected range" error message.  I thought some of my path names might be too long, and that this might be causing SyncToy 2 to fail.  I sorted my path names and shortened the ones that were pushing 255 characters, but this did not solve the problem.  My experiment does not mean that path name length or other path name matters are not causing the problem, just that fixing the issues I could find did not solve the problem. 

    SyncToy seems like such a good idea; I wish I could get it to work.
    Thursday, July 24, 2008 4:07 PM
  • Just installed 20B on an XP machine and a Vista machine. I am getting the same exception on both machines. When the dialog closes, SyncToy does not display anything useful as the program preview or progress window closes too quickly. I have successfully synched a larger folder set than the one I am trying to synch now.

     

    Friday, July 25, 2008 3:58 AM
  • can anybody give me the repro steps ? I tried several times, still did not meet this error.
    Tuesday, July 29, 2008 1:46 AM
    1. Install 20B
    2. Setup folder pair to sync
    3. Preview or Run results in the exception.

    Some folder pairs work. In my case, one of four folder pairs produces the exception each time I try. No error message locates the problem. Nothing at all about the failed operation is written to the log file.

    Tuesday, July 29, 2008 2:59 AM
  • Hi -

     

    Has anyone running into this issue - been able to narrow this down to  the particular file on which error occurs. Anything that stands out particularly about the absolute file path or file name or attributes on that file?

     

    Thanks

    Deepa

     

    Wednesday, July 30, 2008 1:34 AM
    Moderator
  • I had a bit of a play this morning. If you leave the exception window up, you can see the file or folder name where (possibly) the exception occurred.

     

    I renamed the file and re-ran the preview. The exception popped up with the new filename showing.

    I deleted the file and re-ran preview. The exception occurred on a different file.

    I deleted that file and re-ran the preview. Again, the exception occurred on a different file.

    I didn't feel like doing this to 1000 files, so stopped the test at this point.

     

    Oddly, a sync on a larger folder set that includes the problematic folder set works.

    I tried a preview on the same larger folder set (eg. ABig Smileocuments --> BBig Smileocuments) and all was OK. However, previewing a sub-folder set produced the exception (eg. ABig Smileocuments\data --> BBig Smileocuments\data).

    I tried previewing the larger folder set again - all OK.

     

    I am trying to sync to a network drive. I will try the test to a local drive.

    Wednesday, July 30, 2008 3:32 AM
  • So you have narrowed this down to files within a single folder? Anything special about the folder?

     

    Thanks

    Deepa

    Wednesday, July 30, 2008 4:04 AM
    Moderator
  •  

    I am testing on two local folders now. On Vista.

     

    Preview exception occurred on file U1_bits.pas ( 14k text file ). I renamed the Left folder file U1_bitsAAA.pas.

    Re-ran preview - exception occurred on U1_bits.pas. I renamed the Right folder file U1_bitsAAA.pas.

    Exception now occurred on file "SL8M label 02.skf". ( 125k CAD file ) File prompt notes "Adding an action for ...". Right folder file.

     

    I ran the test using a folder pair one folder up in the hierarchy. The exception occurred on file "SL8M label 02.skf". Re-named left folder file "SL8M label 02AAA.skf".  The file did not exist in the right folder.

    Re-ran preview. Exception occurred at the same file.

     

    I copied the file manually - cut & paste.

    Re-ran the preview. The exception occurred at a different file ( small TMP file ) - again noting "Adding an action for ...".

     

    I copied the file manually - cut & paste.

    Re-ran the preview. The exception occurred at a different file ( Word document backup ) - again noting "Adding an action for ...". The file did not exist in the left folder.

     

    Tried the preview on the smaller file set and the exception occured at the same place.

     

    There is nothing special about the files, that I can see.

     

    Wednesday, July 30, 2008 4:57 AM
  • After a bit more testing on local drive folders ...

     

    I can consistently get past an exception on a particular file by making a copy of the file in each folder.

     

    Some new information ...

     

    I deleted a file that was present in only one folder. An exception was thrown on that file even though it was not there. So I guess SyncToy expecting it from it's history ( dat ? ) file.

     

     

     

    Wednesday, July 30, 2008 9:28 PM
  • Hi -

     

    We are still trying to repro this issue and try to find a fix. It would be great if you could check a few other things for us -

     

    On the Help->Customer FeedBack Options - Do you have the radio button set to Yes or No? If you do have it set to Yes - can you change it to No and see what happens

     

    In your Folder pair options - do have anything different from the default folder options?

     

    Thanks for helping

    Deepa

    Thursday, July 31, 2008 1:03 AM
    Moderator
  • Something else that could help is if you could actually attach a debugger to SyncToy and see if you can catch the exception. I am trying to see if you could potentially provide us with a stack trace which would help us narrow down the problem.

     

    Thanks

    Deepa

     

     

    Thursday, July 31, 2008 1:15 AM
    Moderator
  • I think the options are the default ...

    files to include = *, files to exclude blank

    exclude read only OFF, exclude hidden OFF, exclude system OFF

    select sub-folders = not active

    active for run all ON, save overwritten in recycle bin ON, check file contents OFF

     

    I'll try the debugger thing. I have Delphi 5, Turbo Delphi 2006 and the Express Visual Studio 2008 (which I haven't used much). I'll see what I can get working.

     

    Turbo Delphi ...

    SyncToy is much slower. of course. It seems to stall on some files, some of which are empty folders or files.

    Delphi didn't catch the exception. Before closing the exception dialog, I paused the program then stepped forward. After a few priveleged instruction failures at 0x76635fcf, which I continued past, I got an assertion failure "index<=itmes.n()" in DBKIMPL.CPP AT LINE 2661.

    Continuing past that I get an Access violation in the debugger DLL.

     

    I'll see if I can get Visual Studio operational.

    Thursday, July 31, 2008 2:47 AM
  • Found and installed Windbg. Selected the same preview, got the info below when I closed the exception dialog. Couldn't seem to get a stack trace. Will explore the Windbg options.

    ....

    ModLoad: 637a0000 63d28000   C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Xml\c98cb65a79cfccb44ea727ebe4593ede\System.Xml.ni.dll
    SYNC: 07/31/2008 14:28:05:170: -------------------------------------------------------------------------
    (2d64.2d68): CLR exception - code e0434f4d (first chance)
    ModLoad: 74e10000 74e18000   C:\Windows\system32\version.dll
    SYNC: 07/31/2008 14:28:05:179: Starting SyncToy, version 2.0.0.0, built 12/10/2007 12:10:32 PM.
    ModLoad: 6f820000 6f826000   C:\Windows\system32\dciman32.dll
    ModLoad: 50200000 50256000   C:\Program Files\SyncToy 2.0 Beta\mergedsyncprovider.dll
    ModLoad: 757f0000 75874000   C:\Windows\system32\CLBCatQ.DLL
    ModLoad: 03f20000 03f43000   C:\Program Files\Microsoft SQL Server Compact Edition\v3.1\sqlceoledb30.dll
    ModLoad: 03f50000 03f73000   C:\Program Files\Microsoft SQL Server Compact Edition\v3.1\SQLCEER30EN.DLL
    ModLoad: 25000000 2504b000   C:\Program Files\Microsoft SQL Server Compact Edition\v3.1\sqlcese30.dll
    ModLoad: 04250000 042d4000   C:\Program Files\Microsoft SQL Server Compact Edition\v3.1\sqlceqp30.dll
    (2d64.2e94): CLR exception - code e0434f4d (first chance)
    (2d64.2e94): CLR exception - code e0434f4d (first chance)
    eax=feeefeee ebx=00000000 ecx=000001e9 edx=00380574 esi=79fd9e90 edi=00000001
    eip=76f80f34 esp=0025f700 ebp=0025f710 iopl=0         nv up ei pl zr na pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246
    ntdll!KiFastSystemCallRet:
    76f80f34 c3              ret
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Windows\system32\KERNEL32.dll -
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll -
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Windows\system32\mscoree.dll -

     

    Thursday, July 31, 2008 4:40 AM
  • Been playing with windbg. No stack seems traceable. May have managed a dump file - can I send it to you?

    This is running preview on a smaller folder pair that is still causing the exception. I am trying to trace it to a single simple folder - I hope.

     

    From Windbg ...

     

    0:000> .restart /f
    CommandLine: "C:\Program Files\SyncToy 2.0 Beta\SyncToy.exe"
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    (2f48.2ca0): Break instruction exception - code 80000003 (first chance)
    eax=00000000 ebx=00000000 ecx=002bf52c edx=76f80f34 esi=fffffffe edi=76fe5d14
    eip=76f62ea8 esp=002bf544 ebp=002bf574 iopl=0         nv up ei pl zr na pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntdll.dll -
    ntdll!DbgBreakPoint:
    76f62ea8 cc              int     3
    0:000> exe CLR
    *** ERROR: Module load completed but symbols could not be loaded for SyncToy.exe
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Windows\system32\KERNEL32.dll -
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Windows\system32\mscoree.dll -
    Couldn't resolve error at 'xe CLR'
    0:000> sxe CLR
    0:000> g
    Create thread 1:1de4
    Create thread 2:1d3c
    Create thread 3:2678
    Create thread 4:1b08
    Create thread 5:1c74
    Create thread 6:1d6c
    Create thread 7:1cc8
    Create thread 8:1acc
    SYNC: 07/31/2008 15:58:12:442: -------------------------------------------------------------------------
    (2f48.2ca0): CLR exception - code e0434f4d (first chance)
    First chance exceptions are reported before any exception handling.
    This exception may be expected and handled.
    eax=002be4b8 ebx=e0434f4d ecx=00000001 edx=00000000 esi=002be540 edi=004eae58
    eip=7658b08e esp=002be4b8 ebp=002be508 iopl=0         nv up ei pl nz ac pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000216
    KERNEL32!RaiseException+0x58:
    7658b08e c9              leave
    0:000> sxe CLR
    0:000> g
    SYNC: 07/31/2008 15:58:40:305: Starting SyncToy, version 2.0.0.0, built 12/10/2007 12:10:32 PM.
    Create thread 9:f00
    Create thread 10:684
    Create thread 11:18b8
    Create thread 12:f7c
    Exit thread 11:18b8, code 0
    Exit thread 10:684, code 0
    Create thread 10:23c8
    Exit thread 4:1b08, code 0
    Create thread 4:1fac
    Create thread 11:1be0
    Exit thread 5:1c74, code 0
    Exit thread 6:1d6c, code 0
    Create thread 5:2110
    (2f48.23c8): CLR exception - code e0434f4d (first chance)
    First chance exceptions are reported before any exception handling.
    This exception may be expected and handled.
    eax=0527c1fc ebx=e0434f4d ecx=00000001 edx=00000000 esi=0527c284 edi=03b28228
    eip=7658b08e esp=0527c1fc ebp=0527c24c iopl=0         nv up ei pl nz na pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000206
    KERNEL32!RaiseException+0x58:
    7658b08e c9              leave
    0:010> !cen
    No export cen found
    0:010> !clrstack
    No export clrstack found
    0:010> gn
    (2f48.23c8): CLR exception - code e0434f4d (first chance)
    First chance exceptions are reported before any exception handling.
    This exception may be expected and handled.
    eax=0527eef8 ebx=e0434f4d ecx=00000001 edx=00000000 esi=0527ef80 edi=03b28228
    eip=7658b08e esp=0527eef8 ebp=0527ef48 iopl=0         nv up ei pl nz ac po nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000212
    KERNEL32!RaiseException+0x58:
    7658b08e c9              leave
    0:010> !cen
    No export cen found
    0:010> !clrstack
    No export clrstack found
    0:010> gh
    WARNING: Continuing a non-continuable exception
    Exit thread 5:2110, code 0
    (2f48.23c8): Break instruction exception - code 80000003 (first chance)
    eax=00000001 ebx=00000000 ecx=00000000 edx=0527ef24 esi=00000000 edi=79f071bc
    eip=76f62ea8 esp=0527ea84 ebp=0527ef30 iopl=0         nv up ei pl nz na po nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000202
    ntdll!DbgBreakPoint:
    76f62ea8 cc              int     3
    0:010> gn
    (2f48.23c8): Break instruction exception - code 80000003 (!!! second chance !!!)
    eax=00000001 ebx=00000000 ecx=00000000 edx=0527ef24 esi=00000000 edi=79f071bc
    eip=76f62ea8 esp=0527ea84 ebp=0527ef30 iopl=0         nv up ei pl nz na po nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000202
    ntdll!DbgBreakPoint:
    76f62ea8 cc              int     3
    0:010> g
    Exit thread 1:1de4, code 80131506
    Exit thread 3:2678, code 80131506
    Exit thread 9:f00, code 80131506
    Exit thread 7:1cc8, code 80131506
    Exit thread 11:1be0, code 80131506
    Exit thread 12:f7c, code 80131506
    Exit thread 10:23c8, code 80131506
    Exit thread 8:1acc, code 80131506
    Exit thread 2:1d3c, code 80131506
    Exit thread 0:2ca0, code 80131506
    eax=9cd47fe0 ebx=00000bb8 ecx=0023cd00 edx=9cd47d44 esi=0584f978 edi=76d5baa8
    eip=76f80e40 esp=0584f8e8 ebp=0584f954 iopl=0         nv up ei pl zr na pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246
    ntdll!KiUserCallbackDispatcher:
    76f80e40 648b0d00000000  mov     ecx,dword ptr fs:[0] fs:003b:00000000=0584f9e0
    0:004> .restart /f
    CommandLine: "C:\Program Files\SyncToy 2.0 Beta\SyncToy.exe"
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    (2854.2a28): Break instruction exception - code 80000003 (first chance)
    eax=00000000 ebx=00000000 ecx=001bfa8c edx=76f80f34 esi=fffffffe edi=76fe5d14
    eip=76f62ea8 esp=001bfaa4 ebp=001bfad4 iopl=0         nv up ei pl zr na pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntdll.dll -
    ntdll!DbgBreakPoint:
    76f62ea8 cc              int     3
    0:000> sxe CLR
    0:000> g
    Create thread 1:266c
    Create thread 2:2804
    Create thread 3:2584
    Create thread 4:2580
    Create thread 5:1fa4
    Create thread 6:2914
    Create thread 7:2e14
    Create thread 8:ba0
    SYNC: 07/31/2008 16:04:22:159: -------------------------------------------------------------------------
    (2854.2a28): CLR exception - code e0434f4d (first chance)
    First chance exceptions are reported before any exception handling.
    This exception may be expected and handled.
    eax=001bea18 ebx=e0434f4d ecx=00000001 edx=00000000 esi=001beaa0 edi=003bae58
    eip=7658b08e esp=001bea18 ebp=001bea68 iopl=0         nv up ei pl nz ac pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000216
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Windows\system32\KERNEL32.dll -
    KERNEL32!RaiseException+0x58:
    7658b08e c9              leave
    0:000> g
    SYNC: 07/31/2008 16:04:25:395: Starting SyncToy, version 2.0.0.0, built 12/10/2007 12:10:32 PM.
    Create thread 9:1b24
    Create thread 10:1c48
    Exit thread 4:2580, code 0
    Create thread 4:1dc
    Exit thread 5:1fa4, code 0
    (2854.1b24): CLR exception - code e0434f4d (first chance)
    First chance exceptions are reported before any exception handling.
    This exception may be expected and handled.
    eax=043cc52c ebx=e0434f4d ecx=00000001 edx=00000000 esi=043cc5b4 edi=03addc70
    eip=7658b08e esp=043cc52c ebp=043cc57c iopl=0         nv up ei pl nz na po nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000202
    KERNEL32!RaiseException+0x58:
    7658b08e c9              leave
    0:009> !cen
    No export cen found
    0:009> !clrstack
    No export clrstack found
    0:009> g
    (2854.1b24): CLR exception - code e0434f4d (first chance)
    First chance exceptions are reported before any exception handling.
    This exception may be expected and handled.
    eax=043cf228 ebx=e0434f4d ecx=00000001 edx=00000000 esi=043cf2b0 edi=03addc70
    eip=7658b08e esp=043cf228 ebp=043cf278 iopl=0         nv up ei pl nz ac pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000216
    KERNEL32!RaiseException+0x58:
    7658b08e c9              leave
    0:009> !cen
    No export cen found
    0:009> !clrstack
    No export clrstack found
    0:009> g
    Exit thread 10:1c48, code 0
    Exit thread 9:1b24, code 0
    Exit thread 6:2914, code 0
    Create thread 5:2518
    Exit thread 2:2804, code 0
    Exit thread 8:ba0, code 0
    Exit thread 5:2518, code 0
    Exit thread 3:2584, code 0
    Exit thread 1:266c, code 0
    Exit thread 4:1dc, code 0
    Exit thread 7:2e14, code 0
    eax=feeefeee ebx=00000000 ecx=00000043 edx=fffffff7 esi=79fd9e90 edi=00000001
    eip=76f80f34 esp=001bfc80 ebp=001bfc90 iopl=0         nv up ei pl zr na pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246
    ntdll!KiFastSystemCallRet:
    76f80f34 c3              ret
    0:000> !dae
    No export dae found
    0:000> .restart /f
    CommandLine: "C:\Program Files\SyncToy 2.0 Beta\SyncToy.exe"
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    (1908.12d0): Break instruction exception - code 80000003 (first chance)
    eax=00000000 ebx=00000000 ecx=0017f77c edx=76f80f34 esi=fffffffe edi=76fe5d14
    eip=76f62ea8 esp=0017f794 ebp=0017f7c4 iopl=0         nv up ei pl zr na pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntdll.dll -
    ntdll!DbgBreakPoint:
    76f62ea8 cc              int     3
    0:000> sxe CLR
    0:000> g
    Create thread 1:1cd0
    Create thread 2:2a08
    Create thread 3:2130
    Create thread 4:8c0
    Create thread 5:1628
    Create thread 6:f70
    Create thread 7:934
    Create thread 8:2a1c
    SYNC: 07/31/2008 16:17:32:252: -------------------------------------------------------------------------
    (1908.12d0): CLR exception - code e0434f4d (first chance)
    First chance exceptions are reported before any exception handling.
    This exception may be expected and handled.
    eax=0017e708 ebx=e0434f4d ecx=00000001 edx=00000000 esi=0017e790 edi=0027ae58
    eip=7658b08e esp=0017e708 ebp=0017e758 iopl=0         nv up ei pl nz ac po nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000212
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Windows\system32\KERNEL32.dll -
    KERNEL32!RaiseException+0x58:
    7658b08e c9              leave
    0:000> g
    SYNC: 07/31/2008 16:17:36:406: Starting SyncToy, version 2.0.0.0, built 12/10/2007 12:10:32 PM.
    Create thread 9:1768
    Create thread 10:144
    Create thread 11:1020
    Create thread 12:1f30
    Create thread 13:2928
    Create thread 14:117c
    Exit thread 11:1020, code 0
    Exit thread 10:144, code 0
    Exit thread 4:8c0, code 0
    Create thread 4:2c84
    Exit thread 5:1628, code 0
    (1908.2928): CLR exception - code e0434f4d (first chance)
    First chance exceptions are reported before any exception handling.
    This exception may be expected and handled.
    eax=05c0c61c ebx=e0434f4d ecx=00000001 edx=00000000 esi=05c0c6a4 edi=037575d8
    eip=7658b08e esp=05c0c61c ebp=05c0c66c iopl=0         nv up ei pl nz na po nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000202
    KERNEL32!RaiseException+0x58:
    7658b08e c9              leave
    0:013> !load sos
    0:013> !pe
    No export pe found
    0:013> !clrstack -p
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    PDB symbol for mscorwks.dll not loaded
    failed to load from resource.Failed to load SOS data.
    No valid SOS data table found.
    0:013> g
    Exit thread 12:1f30, code 0
    (1908.2928): CLR exception - code e0434f4d (first chance)
    First chance exceptions are reported before any exception handling.
    This exception may be expected and handled.
    eax=05c0f318 ebx=e0434f4d ecx=00000001 edx=00000000 esi=05c0f3a0 edi=037575d8
    eip=7658b08e esp=05c0f318 ebp=05c0f368 iopl=0         nv up ei pl nz ac pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000216
    KERNEL32!RaiseException+0x58:
    7658b08e c9              leave
    0:013> g
    Exit thread 14:117c, code 0
    Exit thread 13:2928, code 0
    Exit thread 6:f70, code 0
    Create thread 5:1a4c
    (1908.1a4c): Break instruction exception - code 80000003 (first chance)
    eax=7ffd9000 ebx=00000000 ecx=00000000 edx=76faf06d esi=00000000 edi=00000000
    eip=76f62ea8 esp=0597f878 ebp=0597f8a4 iopl=0         nv up ei pl zr na pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246
    ntdll!DbgBreakPoint:
    76f62ea8 cc              int     3
    0:005> .restart /f
    CommandLine: "C:\Program Files\SyncToy 2.0 Beta\SyncToy.exe"
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    (1cf8.1ea4): Break instruction exception - code 80000003 (first chance)
    eax=00000000 ebx=00000000 ecx=001ff7d4 edx=76f80f34 esi=fffffffe edi=76fe5d14
    eip=76f62ea8 esp=001ff7ec ebp=001ff81c iopl=0         nv up ei pl zr na pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntdll.dll -
    ntdll!DbgBreakPoint:
    76f62ea8 cc              int     3
    0:000> bp kernel32!RaiseException ".dump /ma /o c:\\temp\\myapp.dmp; g"
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Windows\system32\KERNEL32.dll -
    0:000> bp kernel32!RaiseException ".dump /ma /o c:\\temp\\myapp.dmp; g"
    breakpoint 0 redefined
    0:000> g
    Create thread 1:f14
    Create thread 2:1ab0
    Create thread 3:f04
    Create thread 4:e68
    Create thread 5:1ebc
    Create thread 6:fa4
    Create thread 7:1b08
    Create thread 8:1d88
    Creating c:\temp\myapp.dmp - mini user dump
    Dump successfully written
    SYNC: 07/31/2008 16:24:31:598: -------------------------------------------------------------------------
    Creating c:\temp\myapp.dmp - mini user dump
    Dump successfully written
    (1cf8.1ea4): CLR exception - code e0434f4d (first chance)
    First chance exceptions are reported before any exception handling.
    This exception may be expected and handled.
    eax=001fe758 ebx=e0434f4d ecx=00000001 edx=00000000 esi=001fe7e0 edi=003eae58
    eip=7658b08e esp=001fe758 ebp=001fe7a8 iopl=0         nv up ei pl nz ac po nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000212
    KERNEL32!RaiseException+0x58:
    7658b08e c9              leave
    0:000> g
    Creating c:\temp\myapp.dmp - mini user dump
    Dump successfully written
    SYNC: 07/31/2008 16:24:52:870: Starting SyncToy, version 2.0.0.0, built 12/10/2007 12:10:32 PM.
    Create thread 9:22a8
    Create thread 10:540
    Create thread 11:a54
    Exit thread 4:e68, code 0
    Exit thread 9:22a8, code 0
    Exit thread 6:fa4, code 0
    Create thread 4:f7c
    Creating c:\temp\myapp.dmp - mini user dump
    Dump successfully written
    (1cf8.540): CLR exception - code e0434f4d (first chance)
    First chance exceptions are reported before any exception handling.
    This exception may be expected and handled.
    eax=0535c32c ebx=e0434f4d ecx=00000001 edx=00000000 esi=0535c3b4 edi=03723650
    eip=7658b08e esp=0535c32c ebp=0535c37c iopl=0         nv up ei pl nz na po nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000202
    KERNEL32!RaiseException+0x58:
    7658b08e c9              leave
    0:010> g
    Creating c:\temp\myapp.dmp - mini user dump
    Dump successfully written
    (1cf8.540): CLR exception - code e0434f4d (first chance)
    First chance exceptions are reported before any exception handling.
    This exception may be expected and handled.
    eax=0535f028 ebx=e0434f4d ecx=00000001 edx=00000000 esi=0535f0b0 edi=03723650
    eip=7658b08e esp=0535f028 ebp=0535f078 iopl=0         nv up ei pl nz ac pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000216
    KERNEL32!RaiseException+0x58:
    7658b08e c9              leave
    0:010> g
    Exit thread 11:a54, code 0
    Exit thread 10:540, code 0
    Create thread 6:121c
    Exit thread 2:1ab0, code 0
    Exit thread 8:1d88, code 0
    Exit thread 4:f7c, code 0
    Exit thread 5:1ebc, code 0
    Exit thread 3:f04, code 0
    Exit thread 1:f14, code 0
    Exit thread 0:1ea4, code 0
    Exit thread 6:121c, code 0
    eax=000000c0 ebx=00000002 ecx=040dfdb8 edx=76f80f34 esi=00000000 edi=00000000
    eip=76f80f34 esp=040dfd0c ebp=040dfda8 iopl=0         nv up ei pl zr na pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246
    ntdll!KiFastSystemCallRet:
    76f80f34 c3              ret

     

    Thursday, July 31, 2008 6:33 AM
  • Just been un-selecting folders in the folder list in a folder pair that produces the exception.

     

    If, for example, the SyncToy folder list is ...

     

    folder1

    folder2

    folder3

    folder4

    folder5

     

    and the exception occurs when SyncToy is displaying folder5 in the status, and I un-select folder5, the next preview run will cause the exception to run when folder4 is displayed in the status.

    Un-select folder4, the exception occurs when folder3 is displayed, etc.

     

    Thursday, July 31, 2008 6:45 AM
  • Thanks for trying this out. We are still working on narrowing down the issue.

     

    Can everyone seeing this issue report back on what their screen resolution is when they are running SyncToy?

     

    Thanks

    Deepa

     

     

    Tuesday, August 5, 2008 12:31 AM
    Moderator
  • Still receiving this error and unable to sync.   What changed?    Synctoy 2.0 worked perfectly for months before it suddenly broke - was it a recent MS patch?

    Screen resolution is 1024x768.
    Saturday, August 9, 2008 2:13 PM
  • I also had the problem 'value does not fall within the expected range' and by chance I found the odd file within 80,000: It was a file with a wrong date: For some reason the original date of last change was damaged and was now in the year 2120. After correcting the date SyncToy worked properly. So I propose to look via the search function for data in future (or eventually far in the past). Of course, it would be extremely helpful if SyncToy would indicate which file causes the problem...
    Saturday, August 16, 2008 3:55 PM
  • Wow.. thanks for that fine bit of forensic investigation. We were having a tough time trying to reproduce this problem in-house without exact cause evidence. We will check if this problem exists in the latest 2.0 release.

     

    Sunday, August 17, 2008 5:27 PM
    Answerer
  •  

    Great now that you have what you need any idea as to when this will be fixed? I am using this to sync to Sharepoint which currently doesnt work.. Thanks.
    Wednesday, September 3, 2008 4:09 PM
  •  

    Oh and YES the latest release does not work for Syncing to SharePoint. Tried beta and final...
    Wednesday, September 3, 2008 4:11 PM
  • I know this is an old thread but I had the same errors on a couple of files and it turned out that the date created was mangled. I used Properties Plus to fix the dates, deleted the Synctoy data file in the source directory and the two files that were causing the error transferred just fine.
    Thursday, September 22, 2011 4:02 PM
  • The error is because of the file size. Try to use NTFS on both drives.
    • Proposed as answer by Masaaaaaas Sunday, October 25, 2015 7:05 AM
    Tuesday, December 25, 2012 7:22 PM
  • My usb drive was FAT32, the file to be copied was more than 1GB. As soon as i formatted my USB to NTFS, I was able to copy the huge file.
    Sunday, October 25, 2015 12:25 PM