sync toy: strange message after the sync action

Hi all, I have a problem with sync toy: after a scheduled run (contribute)
over two local drives I obtain the following message (I try to translate from
Italian):

It's impossible to handle an exception produced by the application:
Process ID 0xe50 (3664) Thread ID 0xb60 (2912)
Press OK to terminate operation
Press cancel to debud

The scheduled operation remain active in scheduler, and, after pushing OK
button, the result is a 0xe434f4d message (instead of 0x0) in the scheduler.

Any suggestions??
Many thanks

Hi Joe,

We have had a couple of reports of similar issues and we're tracking them
down. A couple of quick thoughts:

1. Check the application log to see if SyncToy completed the run. In most
reported cases, SyncToy was able to complete the run in spite of the
exception.
2. At least one user was unable to reproduce the bug after uninstalling and
reinstalling SyncToy.
3. Are you using the Windows scheduler or another scheduler?

I hope this helps...
george

"Joe_black" wrote:

> Hi all, I have a problem with sync toy: after a scheduled run (contribute)
> over two local drives I obtain the following message (I try to translate from
> Italian):
>
> It's impossible to handle an exception produced by the application:
> Process ID 0xe50 (3664) Thread ID 0xb60 (2912)
> Press OK to terminate operation
> Press cancel to debud
>
> The scheduled operation remain active in scheduler, and, after pushing OK
> button, the result is a 0xe434f4d message (instead of 0x0) in the scheduler.
>
> Any suggestions??
> Many thanks
>