Well -- I see what's happening in that first appointment, but I don't know why. Perhaps you can remember some history of this appointment, but it's possible that a previous bug caused the behavior.
The CS Staff Meeting occurs every Thursday. In the text, I see that there was an original meeting that started on May 1, 2008. Then there was another one that started on June 18, 2009. In the .xml, there is a recurrence-id of 4/9/2009. This occurs before 6/18/2009, so Outlook cannot find that occurrence. Because these inconsistencies can cause sync problems on later modifications, we don't want weird messages like this to show in Outlook, so we issue the local failure and don't sync it to Outlook.
I'm not sure how we decided there was a recurrence id of 4/9 on a meeting that started on 6/18. It may depend on how the data came to us (migration, some other client, etc.), and how that original 5/1 meeting was deleted.
IN ANY CASE, FOR THE 5.0.17 RELEASE, I HAD ALREADY FIXED BUG 37833 WHICH DEALS WITH THIS EXACT SCENARIO. THERE'S NO POINT IN ISSUING THIS LOCAL FAILURE, AS IT SHOULDN'T REALLY AFFECT THINGS, SINCE THE ANOMALY WAS IN THE PAST. SO IN ZCO 5.0.17 WE WILL SYNC MEETINGS LIKE THIS TO OUTLOOK WITHOUT LOCAL FAILURES.  |