Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
SyncToy has encountered a user-defined breakpoint RRS feed

 > 

  • General discussion

  • Discussion
    Sign in to vote
    0
    Sign in to vote

    For your information:

    When I ran SyncToy this morning I got a dialog window stating what is in the subject: "SyncToy has encountered a user-defined breakpoint". The rest of the text on that dialog reads: "A breakpoint in an application indicates a program error. After this dialog is dismissed, the application will continue running, but it may be in an unstable state.". It has buttons for "Debug" and "Close".

     

    Sure I have Visual Studio installed (2003 and 2005 versions) but I have not set a breakpoint in SyncToy. Visual Studio was not even running when the problem ocurred.

     

    Regards, Peter

    Thursday, June 12, 2008 6:02 AM

All replies

  • Discussion
    Sign in to vote
    0
    Sign in to vote
    Hi,

    just had the same problem... Vista64 if thats relevant.

    Regards,
    Thomas
    Sunday, June 15, 2008 5:43 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote

    Hi,

     trottig wrote:
    Hi,

    just had the same problem... Vista64 if thats relevant.

    Regards,
    Thomas

     

    Me to me to - only mine was running on a win2003 server.

     

    Anyboy have any clue as to what the reason is? Maybe even a workaround (happend twice within a week or so)?

    Thursday, July 3, 2008 7:22 AM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
     arleth69 wrote:

    Hi,

     trottig wrote:
    Hi,

    just had the same problem... Vista64 if thats relevant.

    Regards,
    Thomas

     

    Me to me to - only mine was running on a win2003 server.

     

    Anyboy have any clue as to what the reason is? Maybe even a workaround (happend twice within a week or so)?

     

    Still no hints as to what to do to avoid those annoying errors?

     

    Or what they mean?

    Monday, August 18, 2008 8:08 AM
  • Discussion
    Sign in to vote
    0
    Sign in to vote

    Hi -

     

    Do you hit this error when opening SyncToy, when doing a Run/Preview, or some other operation. Those of you who do have debuggers installed on your box could you attach SyncToy to the debugger and check if you can extract extra information about where this error is coming from?

     

    Thanks

    Deepa

    Monday, August 18, 2008 5:23 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote

    One more question guys. Which version of SyncToy are you running? We released an update to the 2.0 final build late last week? Are you using that?

    Monday, August 18, 2008 6:12 PM
    Answerer
  • Discussion
    Sign in to vote
    0
    Sign in to vote

     Deepa Choundappan wrote:

    Hi -

     

    Do you hit this error when opening SyncToy, when doing a Run/Preview, or some other operation. Those of you who do have debuggers installed on your box could you attach SyncToy to the debugger and check if you can extract extra information about where this error is coming from?

     

    Thanks

    Deepa

     

    I run Synctoy from the scheduler in a nigthly "runall" job. Unfortunately I dont have a debugger on that box. 

     

     

     Ashish Shah [MSFT] wrote:

    One more question guys. Which version of SyncToy are you running? We released an update to the 2.0 final build late last week? Are you using that?

     

    Aerh hmm, it was the beta version. I did not realised that the final build was released until after I posted the message. Now I am using it :-)

    Tuesday, August 19, 2008 5:59 AM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    And are you still having the same issue with the final version?

     

    Tuesday, August 19, 2008 9:00 PM
    Answerer
  • Discussion
    Sign in to vote
    0
    Sign in to vote

    I have not run into the problem since when I first reported it. I changed the synchronization rules since they caused another problem that I posted an issue about too. Since I do not have the original set of rules stored somewhere I cannot really say if version 2.0 (that I did upgrade to last week) resolved this issue.

     

    / Peter

    Wednesday, August 20, 2008 5:57 AM
  • Discussion
    Sign in to vote
    0
    Sign in to vote

    Hi Ashish,

     

     Ashish Shah [MSFT] wrote:
    And are you still having the same issue with the final version?

     

     

    I installed it only a few days ago and forgot to change the path to the executable in the scheduler so it has only been run once (manual run just after installing the new version).

    Anyway, I did not get the error more than once a month or so with the beta so I cant say yet if the final version is an improvement in that respect.

     

    --

    Tom Arleth

    Ascott Software Denmark A/S

    Wednesday, August 20, 2008 7:00 AM