Conflict Resolver problem back

I'm having the same problem. After the update I keep getting a conflict resolver window with 580 sync conflicts between my Entourage and iCal. I've tried both manually and automatically resolving all of them 4 times and it keeps popping up.

Hi,

Only to contribute to the misery of upgrading to the newest version of iTunes and conflicts with Mobile Me. I have searched all of the help documents and I cannot figure out how to reconcile the "calendar" and "contact" conflicts.

Cheers

DjJ

I'll throw my 2 cents in -- and relieve the stress that makes me want to throw my computer. PLEASE FIX THIS.

I have the same problem. I have tried everything including turning off all syncs between ical, Entourage, mobileme. It is still going on and there seems no way to stop it. It just started once I updated in the latest software update two days ago. I similarly feel like throwing the computer at the wall because it has slowed down everything with the conflict resolver continually popping up no matter if I resolve them or not. It never resolves. PLEASE FIX THIS.

I got this 'conflict resolver' problem, soon after upgrading to iPhone 3G.

I recently upgraded to iTunes 9.2, still happening.

Help!

m@

Yeah and great that it chews up 2.75 GIG!!!! of memory and has to be killed every few hours

I have experienced the same issue. I've tried resetting the sync data (deleting the sync database), resettin MobileMe, etc. I get the spinning beach ball and the last time Conflict Resolver was taking 4.5 GB of memory. There's a leak somewhere.

Count me in, this happens frequently to me lately, probably since the iTunes 9.2 update but I am not exactly sure about that.

To be clear for Apple;s sake: there are 2 different but related issues: sync issues and a memory leak in the conflict resolver.
(1) Everything seems to run fine for several weeks and suddenly - wham: sync issues.
(2) The most dreadful part of this is this memory leak which makes your computer near unusable the time you come back from a meeting.

Apple, please run Valgrind and I bet you'll find the memory issue easily as soon as there is a sync issue it cannot immediately resolve.

I got this problem solved. I visited the Apple Genius Bar. I had to because there was complete drag on the entire performance. It took two geniuses to fix it, because the first genius wasn't sure how to do it. But the second genius knew exactly how to fix it. It took several turning off of all syncs, resetting to synch with the computer, and restarting twice during the process. They did not have to touch my iPhone tho, which is good news, just my computer. They did not give me an instruction list, but clearly Apple should simply post these instructions for others, either in this forum or elsewhere!

Uh...how about posting the fix here?! PLEASE.

I am having the same problem. It is driving me crazy!!! Can someone please post a fix??

A quick and dirty solution seems to be to use Activity Monitor (Utilities Folder). Launch that, select Conflict Resolver, then the info button in the toolbar. Then click Quit to kill the process. Not ideal, but a solution at least.

This is extremely frustrating. Conflict Resolver drains all the CPU when it pops up like this -- so much so that it's difficult even getting to the activity monitor to kill it. Starting to feel like I'm working on a PC.

Had the same problem, killed the process using activity monitor. Definitly a memory leak, it chews a **** ton of memory. I'm software developer so I can **** ton, it's a common term in my world:-) It used 4 gigs.

Whenever I open up entourage conflict resolver pops up and it consumes to memory at a gregarious pace.

It's gotta be a problem with iCal.....Does anyone know how to log a ticket with apple?

Here's what my log files say:

6/29/10 10:17:24 PM Conflict Resolver[11347] [110680] |ConflictManager|Warning| Skipping delta conflict with recordId F55627F5-1CC9-47C5-A808-9BFB7770939F, either because it no longer exists in main conflict file, or clients/properties don't match. Core conflict: (null), delta conflict: <ISDConflict 0x11f622420>{ record F55627F5-1CC9-47C5-A808-9BFB7770939F com.apple.calendars.Event com.apple.Calendars (
"<ISDPropertyConflict 0x11f622820>{ record F55627F5-1CC9-47C5-A808-9BFB7770939F\n conflict on main event , winner = com.microsoft.Entourage2008 {\n \"com.apple.iCal\" = {\n \"main event\" = \"<ISDPropertyChange 0x11f622d60>{ set main event }\";\n };\n \"com.microsoft.Entourage2008\" = {\n \"main event\" = \"<ISDPropertyChange 0x11f6221d0>{ set main event }\";\n };\n} }"
) }
6/29/10 10:17:26 PM iCalExternalSync[11425] [ICalExternalSync ]Failed Event/p592 modify validation - Events cannot have multiple exceptions for the same date.
6/29/10 10:17:26 PM com.apple.syncservices.SyncServer[10543] 2010-06-29 22:17:26.157 iCalExternalSync[11425:903] [ICalExternalSync ]Failed Event/p592 modify validation - Events cannot have multiple exceptions for the same date.
6/29/10 10:17:26 PM iCalExternalSync[11425] [ICalExternalSync ]Error: Core Data save failed. Sync canceled. - Events cannot have multiple exceptions for the same date.
6/29/10 10:17:26 PM com.apple.syncservices.SyncServer[10543] 2010-06-29 22:17:26.159 iCalExternalSync[11425:903] [ICalExternalSync ]Error: Core Data save failed. Sync canceled. - Events cannot have multiple exceptions for the same date.
6/29/10 10:17:26 PM iCalExternalSync[11425] [ICalExternalSync ]Events cannot have multiple exceptions for the same date.
6/29/10 10:17:26 PM com.apple.syncservices.SyncServer[10543] 2010-06-29 22:17:26.170 iCalExternalSync[11425:903] [ICalExternalSync ]Events cannot have multiple exceptions for the same date.
6/29/10 10:17:47 PM [0x0-0x7f27f2].com.apple.systemevents[11479] com.apple.FolderActions.enabled: Already loaded
6/29/10 10:17:57 PM Microsoft AutoUpdate[10577] * __NSAutoreleaseNoPool(): Object 0x18704f40 of class CarbonWindowAdapter autoreleased with no pool in place - just leaking
6/29/10 10:17:57 PM Microsoft AutoUpdate[10577] * __NSAutoreleaseNoPool(): Object 0x17611f20 of class WebView autoreleased with no pool in place - just leaking
6/29/10 10:17:57 PM Microsoft AutoUpdate[10577] * __NSAutoreleaseNoPool(): Object 0x4066c0 of class NSCFArray autoreleased with no pool in place - just leaking
6/29/10 10:17:57 PM Microsoft AutoUpdate[10577] * __NSAutoreleaseNoPool(): Object 0x408d40 of class NSCFArray autoreleased with no pool in place - just leaking
6/29/10 10:17:57 PM Microsoft AutoUpdate[10577] * __NSAutoreleaseNoPool(): Object 0x409530 of class NSCFArray autoreleased with no pool in place - just leaking
6/29/10 10:17:57 PM Microsoft AutoUpdate[10577] * __NSAutoreleaseNoPool(): Object 0x403880 of class NSCFArray autoreleased with no pool in place - just leaking
6/29/10 10:17:57 PM Microsoft AutoUpdate[10577] * __NSAutoreleaseNoPool(): Object 0x401610 of class NSCFArray autoreleased with no pool in place - just leaking
6/29/10 10:17:57 PM Microsoft AutoUpdate[10577] * __NSAutoreleaseNoPool(): Object 0x419d00 of class NSCFArray autoreleased with no pool in place - just leaking

I solved my issue. Follow these instructions:

http://support.apple.com/kb/TS1627?viewlocale=en_US


Mac OS X v10.6 Snow Leopard

1. If you see this Sync menu extra in your menu bar skip to step 2. If you do not have this icon, you need to enable it in System Preferences:
* From the Apple () menu choose System Preferences.
* Click MobileMe and then click the Sync tab.
* Select the option to "Show status in menu bar."
2. While holding down the Option key on your keyboard, click the Sync icon in the menu bar (if you see the Sync menu extra but you are unable to open it, skip to step 5)
3. Choose Reset Sync Services.
4. Click Reset Sync History.
If this does not resolve your issue or if you are unable to open the Sync menu extra, follow these steps:
5. In the Finder, choose Utilities from the Go menu.
6. Open Terminal.
7. In the Terminal window, type or paste the following command on a single line:
/System/Library/Frameworks/SyncServices.framework/Versions/A/Resources/resetsyn c.pl reset
8. Press Return.
9. When the operation is complete quit Terminal.