This discussion is archived
1248 Views 2 Replies Latest reply: Aug 20, 2010 4:01 PM by Bonnie Price
Currently Being ModeratedMar 25, 2007 6:01 PM (in response to Bonnie Price)If you have removed the events from SOHO Organizer, that action alone should remove them from the framework and halt the launch of the Conflict Manager. It only launches, by the way, when it cannot resolved what it determines are conflicting fields in matching records: conflicts exist at the field level, and not the record level, and represent differences in the records stored by different applications, devices or servers.
If the removal and subsequent synchronization alone does not resolve the issue, launch iSync, open the Preferences… dialog and press the Reset Sync History… button.
By following the instructions which appear, you will leave your sync clients registered and their data intact, but trigger a first-time slow synchronization during the next event, in which all data is pushed by each client, resolved or 'merged' if you will in the truth database, then pulled by each client. It will likely take more than just the initial event to fully distribute all of the changes throughout the framework, but you should not see the Conflict Manager intervene once this process is completed.PowerBook G4 12 867 MHz 640 meg 40 gig SuperDrive, Mac OS X (10.4.9), coupled with a Palm Treo 600 on the T-Mobile network
Currently Being ModeratedAug 20, 2010 4:01 PM (in response to Bonnie Price)The situation resolved itself in a way I don't remember. Apparently I left this thread hanging for three years!