iCal 7.0 (Mavericks) Quite suddenly not synching with Office365

Question

Level 1

0 points

iCal 7.0 (Mavericks) Quite suddenly not synching with Office365

I've been using iCal successfully with Office365 for a while now.

Recently, accepted meetings in mail do not show up in iCal. New meetings created in the Office web ap do not show in iCal.

Events created in iCal, oddly, show up in Office365 web app - no issue.

So - iCal is not pulling info from office365.

Any ideas? thoughts about troubleshooting?

I tried deleting and re-adding the account (under accounts, in maverics) - no Joy.

Going into ~Library and deleting everything under ~Library/Calendars - no joy

Any thoughts?

iCal-OTHER, OS X Mavericks (10.9), iCal 7.0

Posted on Nov 16, 2013 1:45 PM

Reply

Answer 1

homegilad Author

Level 1

0 points

Nov 16, 2013 1:47 PM in response to homegilad

Just noticed the following error log in Console:

=======

11/16/13 9:45:33.186 PM CalendarAgent[215]: [com.apple.calendar.store.log.exchange.queue] [Save failed in -[CalOperationQueue executeOperations]. Error = Error Domain=NSCocoaErrorDomain Code=1560 "Multiple validation errors occurred." UserInfo=0x7fcfe0c78e10 {NSDetailedErrors=(

"Error Domain=CalCalendarStorePersistenceErrorDomain Code=1550 \"Alerts that open files or scripts must include a file path.\" UserInfo={\n CalAlarmUID = \"44F739FB-6617-4400-87C5-0545D0F1153A\";\n CalCalendarItemUID = \"598680C1-E4C1-4269-920B-85D4D4F4D52F\";\n CalCalendarUID = \"D7FCEC40-B0B0-4AF8-B6B1-0D326854CA9A\";\n CalManagedObjectType = CalManagedAlarm;\n NSLocalizedDescription = \"Alerts that open files or scripts must include a file path.\";\n}",

"Error Domain=CalCalendarStorePersistenceErrorDomain Code=1550 \"Alerts that open files or scripts must include a file path.\" UserInfo={\n CalAlarmUID = \"8DBF3C93-E323-4851-9282-B3BFD4B7F251\";\n CalCalendarItemUID = \"598680C1-E4C1-4269-920B-85D4D4F4D52F\";\n CalCalendarUID = \"D7FCEC40-B0B0-4AF8-B6B1-0D326854CA9A\";\n CalManagedObjectType = CalManagedAlarm;\n NSLocalizedDescription = \"Alerts that open files or scripts must include a file path.\";\n}"

)}. {

NSDetailedErrors = (

"Error Domain=CalCalendarStorePersistenceErrorDomain Code=1550 \"Alerts that open files or scripts must include a file path.\" UserInfo={\n CalAlarmUID = \"44F739FB-6617-4400-87C5-0545D0F1153A\";\n CalCalendarItemUID = \"598680C1-E4C1-4269-920B-85D4D4F4D52F\";\n CalCalendarUID = \"D7FCEC40-B0B0-4AF8-B6B1-0D326854CA9A\";\n CalManagedObjectType = CalManagedAlarm;\n NSLocalizedDescription = \"Alerts that open files or scripts must include a file path.\";\n}",

"Error Domain=CalCalendarStorePersistenceErrorDomain Code=1550 \"Alerts that open files or scripts must include a file path.\" UserInfo={\n CalAlarmUID = \"8DBF3C93-E323-4851-9282-B3BFD4B7F251\";\n CalCalendarItemUID = \"598680C1-E4C1-4269-920B-85D4D4F4D52F\";\n CalCalendarUID = \"D7FCEC40-B0B0-4AF8-B6B1-0D326854CA9A\";\n CalManagedObjectType = CalManagedAlarm;\n NSLocalizedDescription = \"Alerts that open files or scripts must include a file path.\";\n}"

);

}]

Reply

Answer 2

Nov 19, 2013 12:07 PM in response to homegilad

i'm having this exact same issue!

related log entries

Reply

Answer 3

Nov 19, 2013 2:51 PM in response to homegilad

i'm having this problem as well. It appears when i'm making an open file alarm to an event using AppleScript. The function to add a filepath to the alarm has modified, i think. I tested to get (with applescript) the filepath of an existing open file alarm and the result was {””}.

Reply

Answer 4

Nov 19, 2013 3:55 PM in response to mariojoerres

ok, so i think i got mine sorted out.

i happened to have access to Outlook 2010 on a PC. i followed Monica Tong's directions to switch Outlook Calendar to list view, and proceeded to mass-delete old calendar data. in doing this a few times, i guess i removed the offending event (it was in a section titled "Recurrence: Weekly", i believe).

one thing to note: in order for this to work immediately, i *did* have to switch-off "Use Cached Exchange Mode" in Outlook 2010 under Account Settings > Data Files > Settings... > Advanced. (see: http://imgur.com/KG4mwzA)

i vaguely remember playing with running an AppleScript as an alarm for an event a couple years ago, so i guess that was what was making it fail. not to say there's not still an issue between Office 365 and Mavericks...

hope this helps someone 🙂

Reply

Answer 5

homegilad Author

Level 1

0 points

Dec 17, 2013 2:00 PM in response to homegilad

So, thanks everyone who pitched in

The question is, how does one identify the offending event without mass deleting events in the exchange.

Can one just debug calendar to reveal what's breaking it?

Reply

Answer 6

-wen-

Level 1

29 points

Jun 5, 2014 8:35 AM in response to Chris Seymour

This advice helped me solve an identical issue with a recurring event I'd scheduled that used to have an AppleScript attached (or maybe just a file attachment to open a link).

I had the same "Alerts that open files or scripts must include a file path." log messages mentioned at the top of the thread.

This was enough to jog my memory, find the very first of the recurring events I'd tried to script, and delete it. I got a dialog asking to delete ALL future occurences, and I clicked "Delete all future". Luckily for me, I knew exactly which event was the offender.

Then I refreshed my calendars, and lo & behold! Exchange is now syncing properly.

Many thanks to everyone who contribued to this thread.

Reply