Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Exception during preview: Failed to Detect Changes RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    New user here trying to make sense of everything.  I am trying to do an echo from a local hard drive to a network hard drive.  The amount of data is about 130gb.  The sync made it through 63gb+/- and then stopped.  Every time that I try to run the program again on the same folder pair, I get this error during the preview: "Exception during preview: Failed to Detect Changes".  Is this a known issue? Suggestions?  I am running 2.0 that I just downloaded yesterday.  The local machine is a W2k3 SBS server, and the network drive is on an XP machine with SP3.  Thanks.

    Thursday, October 9, 2008 2:52 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi -

     

    Can you take a look at the log ( File->View Log) and copy-paste what is in there? If you could also turn on verbose logging before you send it to us. To change this – look at the SyncToy.config file in the SyncToy install folder and change the trace level from “Info” to “Verbose”. Re run the failing sync and let us know what you have in the log.

     

    Thanks

    Deepa

    Thursday, October 9, 2008 5:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Here is the beginning and end of the verbose log.  I cut a large portion out of the middle to save space and keep my entire file structure off the web!  Let me know what you see.   Thanks.

     

    SYNC: 10/10/2008 10:13:14:554: Started scanning directory : E:\projects\
    SYNC: 10/10/2008 10:13:14:554: Started scanning directory :     \\20020108-1\Projects Sync\
    SYNC: 10/10/2008 10:13:14:569: Scanning Directory : E:\projects
    SYNC: 10/10/2008 10:13:14:569: Scanning Directory :     \\20020108-1\Projects Sync
    SYNC: 10/10/2008 10:13:14:679: Scanning Directory : E:\projects\A Library
    SYNC: 10/10/2008 10:13:14:679: Scanning Directory : E:\projects\A Library\AAdetails


    ***BULK of LOG removed for brevity.  All entries read: "Scanning Directory :"


    SYNC: 10/10/2008 10:16:01:664: Scanning Directory : \\20020108-1\Projects Sync\Project + Name\Structural Engineer (Engineer Name)\Rec'd 2006.06.30
    SYNC: 10/10/2008 10:16:14:789: *** Exception during preview: {0} :
     Microsoft.Synchronization.SyncException: Failed to detect changes. ---> System.Runtime.InteropServices.COMException (0x80070017): The FileSyncProvider failed while detecting changes.
       at Microsoft.Synchronization.Files.Interop.FileSyncProviderClass.DetectChanges()
       at Microsoft.Synchronization.Files.FileSyncProvider.DetectChanges()
       --- End of inner exception stack trace ---

    Server stack trace:
       at Microsoft.Synchronization.Files.FileSyncProvider.DetectChanges()
       at SyncToy.SyncEngine.DetectChangesOnProvider(FileSyncProvider syncProvider, String replicaRootPath)
       at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
       at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
       at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)

    Exception rethrown at [0]:
       at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
       at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
       at SyncToy.SyncEngine.DetectChanges.EndInvoke(IAsyncResult result)
       at SyncToy.SyncEngine.Run(Boolean previewMode)
       at SyncToy.SyncEngine.Preview()
       at SyncToyUI.PreviewDialog.PreviewOnePair(SyncEngine she)
    SYNC: 10/10/2008 10:16:14:789: *** Exception during preview: Failed to detect changes.

     

    Friday, October 10, 2008 3:33 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm not sure if this was the cause of the problem or a result of the problem, but I wanted to follow up and let you know that the drive has failed.  It was about three years old, a WD 320gb.  I will re-try everything on a new drive and post here if I can duplicate the failure.

     

    Thursday, October 16, 2008 1:56 PM