로그인
Microsoft.com
 
Microsoft
 
 
 
Microsoft >
> 
> 
SyncToy 2.1 "FileTime" failure on Windows 7

คำตอบ SyncToy 2.1 "FileTime" failure on Windows 7

  • 2009년 12월 7일 월요일 오후 11:36
     
     
    로그인하여 투표
    0
    I have just started using SyncToy with the release of V2.1 (have not used previous versions).

    OS = Windows 7.
    Sync locations = Hard Drive of local PC to NAS device.
    SyncToy Action = Synchronise

    On creating folder pairings and running SyncToy for the 1st time, no problems, run completed with no errors.

    When re-running the operation 2nd time and beyond, the operation fails on one of the 8 pairs I have set-up, all others run OK.

    Failure Message:

    Exception during preview: Not a valid Win32 FileTime.

    Parameter name: fileTime


    If I follow this up by excluding the left folder at which the failure appears to occur, the same error is returned at the corresponding right hand folder. If I then exclude the right folder; on re-running SyncToy the same failure results, but appears to occur on a folder that had previously completed successfully.

    Excluding these folder pairs simply results in the same failure at an apparently earlier point in the sync.

    The directory in question contains 20,339 Files and 723 Folders.

    The failure point is not deeply nested, top or second level folders, containing a small number of files; first point of failure held 2 scanned JPEG images (<1MB each) and a PDF (40kB).

    Log Extract:

    SYNC: 12/07/2009 23:18:29:863: Started scanning directory : D:\Documents\
    SYNC: 12/07/2009 23:18:29:863: Started scanning directory : P:\Study-Documents\
    SYNC: 12/07/2009 23:18:40:299: Stopped scanning directory : D:\Documents\
    SYNC: 12/07/2009 23:18:45:151: Stopped scanning directory : P:\Study-Documents\
    SYNC: 12/07/2009 23:18:45:728: *** Exception during preview: {0} :
     System.ArgumentOutOfRangeException: Not a valid Win32 FileTime.
    Parameter name: fileTime
       at System.DateTime.FromFileTimeUtc(Int64 fileTime)
       at Microsoft.Synchronization.Files.FileData.FileTimeToDateTime(FILETIME fileTime)
       at Microsoft.Synchronization.Files.FileSyncProvider.FileSyncProviderCallback.OnApplyingChange(String newDirectoryPath, String currentDirectoryPath, _WIN32_FIND_DATAW newFileInfo, _WIN32_FIND_DATAW currentFileInfo, FILESYNC_CHANGE_TYPE dwChangeType)
       at Microsoft.Synchronization.CoreInterop.ISyncSession.Start(CONFLICT_RESOLUTION_POLICY resolutionPolicy, _SYNC_SESSION_STATISTICS& pSyncSessionStatistics)
       at Microsoft.Synchronization.KnowledgeSyncOrchestrator.DoOneWaySyncHelper(SyncIdFormatGroup sourceIdFormats, SyncIdFormatGroup destinationIdFormats, KnowledgeSyncProviderConfiguration destinationConfiguration, SyncCallbacks DestinationCallbacks, ISyncProvider sourceProxy, ISyncProvider destinationProxy, ChangeDataAdapter callbackChangeDataAdapter, SyncDataConverter conflictDataConverter, Int32& changesApplied, Int32& changesFailed)
       at Microsoft.Synchronization.KnowledgeSyncOrchestrator.DoOneWayKnowledgeSync(SyncDataConverter sourceConverter, SyncDataConverter destinationConverter, SyncProvider sourceProvider, SyncProvider destinationProvider, Int32& changesApplied, Int32& changesFailed)
       at Microsoft.Synchronization.KnowledgeSyncOrchestrator.Synchronize()
       at Microsoft.Synchronization.SyncOrchestrator.Synchronize()
       at SyncToy.SyncEngine.CreateAndStartSession(FileSyncProvider destinationProvider, FileSyncProvider sourceProvider)
       at SyncToy.SyncEngine.RunSyncSessionsForChosenSyncType(FileSyncProvider leftProvider, FileSyncProvider rightProvider, SyncMode syncMode)
       at SyncToy.SyncEngine.Run(Boolean previewMode)
       at SyncToy.SyncEngine.Preview()
       at SyncToyUI.PreviewDialog.PreviewOnePair(SyncEngine she)
    SYNC: 12/07/2009 23:18:45:728: *** Exception during preview: Not a valid Win32 FileTime.
    Parameter name: fileTime

    Same failure occurs when running from the command line.

    All other folder pairs currently complete with no failure.
    • 편집됨 Racey 2009년 12월 7일 월요일 오후 11:41 Missing info.
    •  
     

모든 응답

  • 2009년 12월 8일 화요일 오후 9:30
    중재자
     
     답변됨
    로그인하여 투표
    0

    Hi Racey,

    this is most likely due to the corrupted file attributes. you can use file explorer to fix the attribute and then re-sync.

    thanks
    Yunwen

    This posting is provided "AS IS" with no warranties, and confers no rights.
     
  • 2011년 3월 3일 목요일 오후 2:53
     
     제안된 답변
    로그인하여 투표
    5

    I still had this problem with SyncToy 2.1 on several of my files.  The problem is trying to find which files out of my 355,000 files has an invalid time.  So I wrote a utility that will list the offending files and optionally change the invalid file times to the current time.

    You can use it http://www.isdigital.com/FindInvalidFileTime.zip

    Although I can assure you there is nothing intentionally malicious in the program, you use it at your own risk as I haven't tested it extensively, only on my own computer.

    Cheers and good luck!

    • 답변으로 제안됨 Nigel M 2012년 7월 10일 화요일 오후 2:41
    •  
     
  • 2011년 4월 1일 금요일 오전 11:33
     
     
    로그인하여 투표
    0

    Hey ISDigital,

    I have tried your little progam but it is not doing anything.

     

    SyncToy 2.1 is still having the Win32 FileTime ERROR

     

     

     
  • 2011년 8월 18일 목요일 오후 9:14
     
     
    로그인하여 투표
    0
    It works for me, thank you very much.
     
  • 2012년 5월 5일 토요일 오후 7:21
     
     
    로그인하여 투표
    1
    Thank you very much for the utility (and for keeping it available for so long - I encourage you to keep on making it available). It would have taken me ages to track down all the invalid FileTime entries on my system, as there were about 30 of them. You saved me having to write my own utility.
     
  • 2012년 7월 10일 화요일 오후 2:45
     
     
    로그인하여 투표
    0

    I still had this problem with SyncToy 2.1 on several of my files.  The problem is trying to find which files out of my 355,000 files has an invalid time.  So I wrote a utility that will list the offending files and optionally change the invalid file times to the current time.

    You can use it http://www.isdigital.com/FindInvalidFileTime.zip

    Although I can assure you there is nothing intentionally malicious in the program, you use it at your own risk as I haven't tested it extensively, only on my own computer.

    Cheers and good luck!


    Brilliant! For what it is worth, the files were all from the backup of my TomTom (GRRR!)

    -- Nigel M

     
  • 2012년 8월 7일 화요일 오전 3:29
     
     
    로그인하여 투표
    0
    Brilliant. Thank you for doing the job that SyncToy should be doing. In my case they were all recently added files that were pictures from an Ipod. Your utility found them all and repaired them quickly.
    Thanks again.
     
  • 2012년 9월 9일 일요일 오후 1:52
     
     
    로그인하여 투표
    0
    ISDigital..... All I can say is thanks. It works perfect.
     
  • 2013년 1월 28일 월요일 오후 6:41
     
     
    로그인하여 투표
    0
    Thank you so much ISDigital for the utility you uploaded, wouldn't have known what to do if I didn't stumble across this thread. Much appreciated!!!