Successful MobileMe to iCloud migration, but iCal now giving error messages

I've the same problem in Italy whit my iMac and MacBook Pro!

Same here, have not been able to use iCal for weeks. All my calendars look to have been imported twenty times each, and are all selected.

I'd pay good money to go back to mobileme and pretend this whole iCloud disasterpiece never happened.

Isn't there a fix for this? Starting to rely on my phone to keep organized, which is agonizing.

Same issue for me. What is going on here, Apple?

interesting thread. I migrated, everything ok but ical not sync'ing. can't figure out how to get ical on icloud but while investigating can understand these threads. Would be nice if Apple would have worked this out better.

Anyone know how to find the icloud URL you should be subscribing to?

Same problem here. Help anybody?

I also don't understand why Apple would move away from I-Disk/Mobile Me when the Cloud won't sync all of my documents. Seems like a good time to buy stock in DropBox (is it a public company?). I just migrated my doc. storage to DropBox and it appears to be everything that I-Disk never was. Maybe that's why Apple has discontinued it.

Hey, Apple, do you hear us? As an exclusive user of Apple products for 25 years, I am irritated that this problem seems to fall on deaf ears. Also, provide a "Delete All" for junk mail on iphone. PLEASE!

This is a user to user forum. Apple is not here.

Allan

This is indeed an unsolved problem.

I also have a persistent "the server responded with 509 to operation CalDAVMigrateToServerQueueableOperation".

I also have this in my system.log:

Jan 11 10:24:43 alma [0x0-0x67a67a].com.apple.iCal[2749]: 2012-01-11 10:24:43.708 iCalExternalSync[3337:407] [ICalExternalSync ]CESSyncTool:Encountered -[__NSCFDictionary setObject:forKey:]: attempt to insert nil value (key: MigrationGroup/p88) stack: (

Jan 11 10:24:43 alma [0x0-0x67a67a].com.apple.iCal[2749]: 0 iCalExternalSync 0x000000010ce5277a iCalExternalSync + 128890

Jan 11 10:24:43 alma [0x0-0x67a67a].com.apple.iCal[2749]: 1 iCalExternalSync 0x000000010ce34094 iCalExternalSync + 4244

Jan 11 10:24:43 alma [0x0-0x67a67a].com.apple.iCal[2749]: 2 ??? 0x0000000000000007 0x0 + 7

Jan 11 10:24:43 alma [0x0-0x67a67a].com.apple.iCal[2749]: )

Jan 11 10:24:43 alma iCalExternalSync[3337]: [ICalExternalSync ]CESSyncTool:Encountered -[__NSCFDictionary setObject:forKey:]: attempt to insert nil value (key: MigrationGroup/p88) stack: (

0 iCalExternalSync 0x000000010ce5277a iCalExternalSync + 128890

1 iCalExternalSync 0x000000010ce34094 iCalExternalSync + 4244

2 ??? 0x0000000000000007 0x0 + 7

)

Do you guys have something like this in your system.log? (use Utilities/Console.app to find out if you aren't command-line savvy).

I have filed a bug at bugreport.apple.com,

I suggest you all do the same.

(You might want to reference my problem ID, but I don't know whether your problem is exactly the same I have.)

Same problem here... Amazing that thre is no fix!1

Apple engineers are actively looking into this -- I have exchanged debug information with them in the problem ID cited above. The problem itself is probably easy to fix, but a fix will just lead to the "Gemino curse" of magically replicating iCal calendars going on and on again. So that needs to be fixed first, and sync problems are always extremely hard to fix.

Where did I read recently:

"Calendaring indeed is the biggest unmitigated disaster in the Apple

ecosystem. iCal and its servers in the iCloud system deserve CEO

attention, now."

Can't google it, now.

I have the same issues.

By the way, Mountain Lion finally solves the 509 problem, and there is no further duplication of calendars.

Unfortunately, it does nothing to reign in the existing duplicates that the bug created.

Interestingly, 10675237 is still marked as open...

Just upgraded to Mountain Lion on both machines (Mac Pro 2008 and MacBook Pro 2011) and the 509 error persists.

I can't believe there isn't a solution for this yet.

THIS TOTAL CRAP!