iCal/Exchange intermittent sync issues..anyone else seeing these?

Question

We are on 10.7.2 and Exchange: 2007 SP3 RU4Here are the behaviors we are experiencing on more then one client. New event creation issue where new events would not save correctly to exchange server:In my case I was simply creating new appointments by double clicking on iCal and setting date and times.  The &#x27;new event&#x27; issue would occur intermittently among the other issues of events disappearing on refresh.  To me it seemed like there was just an issue with iCal updating to the exchange server.  Depending on the timing, it would update/sync and the iCal event would do one of three things…1.) It would be in the correct place, at the correct time, with the correct name (that day, very rarely would it stay where I wanted it…since then though, it has been much better).2.) It would no longer be on the calendar at all, as though exchange never saw any calendar event when it synced, and instead synced an empty calendar over the event time.3.) It would go halfway…which is it would have an appointment listed, at the time that I double-clicked on, named New Event…but wouldn&#x27;t have the proper name or the date/time I might have changed it to.Drag and Drop Issues:    If you do things to fast(especially with drag and drop) you can lock up iCal and the changes which you want to make do not get passed to the server. When you relaunch iCal you do not see the changes made.    If you quit too fast after making a change I&#x27;ve seen it where changes do not get passed. This should correct with the relaunch of iCal however this is sporadic at best.     I have not seen or been able to reproduce the instance where when you set up a new meeting that it never makes it to the calendar or gets reverted back to being a New Event.As we are in an enterprise environemnt there are higher ups who are just not happy about losing appointments this way. Is anyone else experincing this.

Axsnyder · Answer

I am having this exact same issue.  It started for me after switching from MobileMe to iCloud.  I cannot remember what I did during the setup, but I did do something that changed my calendar settings for my @me.com account.  It was some sort of sync with other calendars option, but I&#x27;m not 100% sure of that.  It was from that moment when I started to have these Exchange issues.  The really weird part is I am only experiencing this issue on a single device (just happens to be my work computer where I need Exchange to work flawlessly).  Other people in my office (with Lion installed but have not switched to iCloud yet) are not having this problem.

nutbrownhare · Answer

Also seeing these problems.  An event created in iCal (OS X 10.7.2) fails to register properly on Exchange. On Exchange (viewed through the Web interface) the event shows as "New Event" but iCal sometimes retains the details originally entered. Sometimes it deletes those details and displays "New Event." In both of these cases, my iPhone 3GS (iOS 5), which is configured to "push" Exchange calendar events, is properly synced with Exchange; i.e., if the Exchange web interface shows "New Event", then iPhone shows "New Event," regardless of what iCal shows. Using drag-and-drop to move events on iCal usually fails; the event moves to the new time, for a while, then snaps back to its original position. This is for events created on iCal synced to Exchange. Curiously, though, events created on iPhone and pushed back to Exchange work more reliably. The event details are registered properly, and re-scheduling works too. What compounds the mystery here is that I wasn&#x27;t able to reproduce the iCal/Exchange problems on my mac mini, which has the identical OS and account info. Finally, colleagues at work who use Outlook for Mac and Outlook Web Access are also seeing anomolies with Exchange calendar, which makes me wonder if Exchange is at least part of the problem. I tried deleting the Exchange account from my MacBook Pro, then re-creating it. That did not help.

FrankVandebergh · Answer

I too have the problem with calendar events being renamed to "New Event". It does not happen when events are created on iPhone, only when created in iCal. This is with a Exchange 2010 account. Maybe it is related to Exchange 2010 ? I did not have the problem when we were still at 2007.

chiefhabeb · Answer

Same problems here.  It changes to a New Event that is an all day event.  On Exchange 2010 and just updated to iCloud.

eddy! · Answer

Ditto to all that. Same problems.I found that if I make my appointments in Exchange however, they always stay. I&#x27;ve got about a 50% chance of keeping them if I make them in iCal. Otherwise, I get a lot of &#x27;New Event&#x27;.maybe there&#x27;s a fix in 10.7.3?e.

Axsnyder · Answer

Quick update:  I am now experiencing the issue on all of my machines with Lion installed.  My Snow Leopard machines have no issues.  I am also experiencing this with both the Exchange servers I&#x27;m syncing with (one is 2010 and the other is 2007).I spoke to my IT department today and they say they&#x27;ve heard this exact "New Event" complaint from all but one of the people who have upgraded to Lion in our office.  They also said that everyone who has complained moved from MobileMe to iCloud.  They&#x27;re also hearing some people having "New Event" issues with Outlook.  According to them Microsoft is also trying to track down the problem and is hopeful a future patch/fix could help.  Microsoft told our IT department that they have been successful in fixing 1 out of 7 of these issues, and acknowledge that this isn&#x27;t a satisfactory result, so they continue to work.  They claim that they&#x27;re unsure whether it is an Exchange issue or an Apple issue.  I was pleased to hear Microsoft (at least the reps we&#x27;re working with) isn&#x27;t pointing any fingers.

tenderidol · Answer

I&#x27;m having the exact same problem with 10.7.2, iCal and Exchange Server. Here are my observations:1. If I double click on anywhere to create a new entry, the chance of getting it synced to the server is about 50%. Either it sticks or turns into "New Event"2. If I drag and drop appointments around, the chance of getting it synced to the server is about 50%. Some appointments stay at the new location, while some revert back.3. If I create a new entry by clicking on the "+" icon next to the "Calendars" button, it syncs fine every time and never reverts back to "New Event".4. If I double-click on any existing entry and change the date, time etc through the edit menu, the entries always stay at their new location and never reverts back.It seems like drag&amp;drop changes and creating new entries via double-clicking break the sync process with the Exchange server. I have the iCal on my iPod Touch setup as Exchange Mail/Calendar, and I don&#x27;t sync Calendars via iCloud. I&#x27;m surprised that this hasn&#x27;t gotten any more attention, since it is extremely annoying to find your new entries changed to "New Event", as well as seeing all recent changes reverted back to the previous state.Let&#x27;s hope that Apple comes up with a solution in 10.7.3.

preugels · Answer

Sorry I saw that post too late, so I reported the problem in a different thread again. Got the same problem here.

nutbrownhare · Answer

Thanks, all, for your comments. No solution yet. After talking to one of our tech folks, it seems the problem may be connected to an Exchange server crash we suffered a couple of months ago, and from which we&#x27;re still recovering (involving data corruption, which may be ongoing). We also upgraded to Exchange 2010 from 2007. That may (or may not) account for the emergence of new problems: As of this week, when I create all-day appointments that span 2 or more days in iCal, they&#x27;re registered as events that run from 12 am on the first day through midnight on the ending day on Exchange and iPhone. This anomaly is new. Also new is the inconsistent behavior of "push" calendar updates. I configured my iPhone&#x27;s calendar to get "push" sync from Exchange. Most of the time that works. Sometimes, though, it behaves like "fetch", and I have to wait for events to download and appear on the iPhone.

DJ Flyte · Answer

I am seeing this with a client on 10.7.2 with a Hosted Exchange provider. They are hosting a variant of 2007 Exchange.Events that are created in iCal will keep their date and time but will revert to the "new event" name. Is this a bug introduced with 10.7.2Would love to see a fix.

David Pakman · Answer

Having all of the exact same issues above. Lion 10.7.2, Exchange 2010, also upgraded to iCloud but AM NOT using iCloud calendar, mail or contacts.Please help. So annoying.

Eicos · Answer

Having the same trouble - Lion 10.7.2, Exchange 2010. Like the previous poster, I upgraded to iCloud but use no iCloud services at all. Very frustrated with Apple.

DJ Flyte · Answer

Bump... I had this happen at another client todoay. This is not good.

PJ Kent · Answer

We&#x27;ve done some testing - and applied a patch to Exchange 2010 but the problem continues...  Some notes below on what we can recreate, although it&#x27;s a bit sporadic.  Very frustrating for our users and for us, as there seems to be no fix available other than to stop using iCAL or Office for Mac.******************************************************************************** *******With Exchange 2010 – SP1 Update Rollup 6.Issues seem to be more sporadic.  iCAL has crashed shortly after boot.Scenario 1In iCAL, right click calendar and create new event – give event title, etc.Calendar event replicates to Exchange (appears in Outlook client, OWA, iPad) with the correct title.Move event (i.e. drag-and-drop) multiple times within the calendar refresh interval, the moves on Exchange (Outlook client, OWA, iPad) will show previous position.  When the calendar refresh interval happens, the event will revert to the previous position. Scenario 2In iCAL, right click calendar and create new event – give event title, etc.Calendar event replicates to Exchange (appears in Outlook client, OWA, iPad) with the correct title. Scenario 3Create Quick Event in iCAL to create a new event – give event title, etc.  – click Done.Calendar event replicates to Exchange (appears in Outlook client, OWA, iPad) with the correct title.Move event (i.e. drag-and-drop) multiple times within the calendar refresh interval, the moves on Exchange (Outlook client, OWA, iPad) will show previous position.  When the calendar refresh interval happens, the event will revert to the previous position.  Scenario 4Moving any existing event in iCAL multiple times results in Exchange (appears in Outlook client, OWA, iPad) being one step behind iCAL.  When the calendar refresh interval happens, iCAL will move the event to where Exchange thinks it should be (one step behind).******************************************************************************** *******Prior to the update (running Exchange 2010 – SP1 Update Rollup 3 version 3.)These scenarios only appear to happen when iCal has been running for a while – and we have experienced iCal crash.Scenario 1In iCAL, right click calendar and create new event – give event title, etc.Calendar event replicates to Exchange (appears in Outlook client, OWA, iPad) with the title of ‘New Event’ (i.e. loses its correct title).If left for the calendar refresh interval, the event will replicate back to iCAL with the title of ‘New Event’.Double click event to amend, event title changes to ‘New Event’ (i.e. loses its correct title).Change event title to correct title – and click done – and the correct title now replicates across Outlook client, OWA, iPad).Move event (i.e. drag-and-drop), when the calendar refresh interval happens, the event will revert to the original time and change the title to ‘New Event’. Scenario 2Double click in iCAL to create a new event – give event title, etc.Calendar event replicates to Exchange (appears in Outlook client, OWA, iPad) with the title of ‘New Event’ (i.e. loses its correct title).If left for the calendar refresh interval, the event will replicate back to iCAL with the title of ‘New Event’.Double click event to amend, event title changes to ‘New Event’ (i.e. loses its correct title).Change event title to correct title – and click done – and the correct title now replicates across Outlook client, OWA, iPad).Move event (i.e. drag-and-drop), when the calendar refresh interval happens, the event will revert to the original time and change the title to ‘New Event’. Scenario 3Create Quick Event in iCAL to create a new event – give event title, etc.  – click Done.Calendar event replicates to Exchange (appears in Outlook client, OWA, iPad) with the correct title. Scenario 4Moving any existing event in iCAL multiple times results in Exchange (appears in Outlook client, OWA, iPad) being one step behind iCAL.  When the calendar refresh interval happens, iCAL will move the event to where Exchange thinks it should be (one step behind).

Focusedonmac · Answer

We seem to have the same issue here.  Recently upgraded to Exchange 2010, began getting user comments a few days later.  Very strange behavior, events revert from their name to "New Event". Changing details about an event occasionally sends a cancellation notice to the users, events randomly revert to old scheduled times or dissappear completely.  Seems more related to Lion mail than SL, though we have around 50 users on a mix of the two.  Most of the issues seem to originate from Lion users though.Just a few highlights from the console.The fine person who solves this deserves a free cookie.Error Error Domain-SOAPWebServicesErrorDomane Code&#x3D;&#x3D;1 "The operation couldn&#x27;t be completed. (SOAPWebServicesErrorDomain error &#x3D;1.)" UserInfo&#x3D;0x7febb4954b28 (SOAPErrorHTTPStatusKey&#x3D;500) getting free-busy information for ("mailto:me@mybusiness.com")11/28/11 12:46:37.531 PM iCal: Unexpected EOF, returning last token as fallback11/30/11 3:26:40.362 PM iCal: -[CalManagedExchangePrincipal setPrimitiveOverrideBaseURL:]: unrecognized selector sent to instance 0x10d69092012/1/11 2:59:09.750 PM iCal: (          0   CoreFoundation                      0x00007fff84aed286 __exceptionPreprocess + 198          1   libobjc.A.dylib                     0x00007fff845c7d5e objc_exception_throw + 43          2   CoreFoundation                      0x00007fff84b794ce -[NSObject doesNotRecognizeSelector:] + 190          3   CoreFoundation                      0x00007fff84ada133 ___forwarding___ + 371          4   CoreFoundation                      0x00007fff84ad9f48 _CF_forwarding_prep_0 + 232          5   CoreData                            0x00007fff86bd9ac0 -[NSManagedObjectContext refreshObject:mergeChanges:] + 1056          6   CoreData                            0x00007fff86bed6cf -[NSManagedObjectContext _mergeChangesFromDidSaveDictionary:usingObjectIDs:] + 1471          7   CalendarStore                       0x00007fff857785f2 -[CalManagedObjectContext mergeChangesFromContextDidSaveNotification:] + 593          8   CalendarStore                       0x00007fff856547dd -[CALBag managedObjectContextDidSave:] + 114          9   CoreFoundation                      0x00007fff84adca1d -[NSObject performSelector:withObject:] + 61          10  Foundation                          0x00007fff87e83e44 __NSThreadPerformPerform + 214          11  CoreFoundation                      0x00007fff84a5bb51 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17          12  CoreFoundation                      0x00007fff84a5b3bd __CFRunLoopDoSources0 + 253          13  CoreFoundation                      0x00007fff84a821a9 __CFRunLoopRun + 905          14  CoreFoundation                      0x00007fff84a81ae6 CFRunLoopRunSpecific + 230          15  HIToolbox                           0x00007fff8c2c43d3 RunCurrentEventLoopInMode + 277          16  HIToolbox                           0x00007fff8c2cb63d ReceiveNextEventCommon + 355          17  HIToolbox                           0x00007fff8c2cb4ca BlockUntilNextEventMatchingListInMode + 62          18  AppKit                              0x00007fff8f4d23f1 _DPSNextEvent + 659          19  AppKit                              0x00007fff8f4d1cf5 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 135          20  AppKit                              0x00007fff8f4ce62d -[NSApplication run] + 470          21  AppKit                              0x00007fff8f74d80c NSApplicationMain + 867          22  iCal                                0x000000010b59ca9f iCal + 6815          23  iCal                                0x000000010b66edd0 iCal + 867792          24  ???                                 0x0000000000000002 0x0 + 2)12/1/11 4:41:29.641 PM iCal: -[CalManagedExchangePrincipal setPrimitiveOverrideBaseURL:]: unrecognized selector sent to instance 0x7fc1626e76f0Thanks for your time, Apple community!