Unable to Save Calendar to Exchange Office 365 in iCal on Yosemite

This problem was so **** infuriating but your fix solved it. Out of frustration, sometimes I hit "Save" on those spurious dialog boxes, and for whatever reason, an invitation would be sent out to all of the original people invited, even if I wasn't the one who originated the invite. Frustrating. The problem seems to happen to me every day or two, regardless of whether I'm traveling or not.

I wrote a *very* simple shellscript to repeat doing this on an as needed basis. It's called "~/bin/resetical". See below:

#! /bin/sh

#

#

rm -f /Library/Caches/com.apple.AutoTimeZone.plist

osascript -e 'display notification "Cleared iCals TimeZone Cache" with title "ResetIcal"'

Then, I made it owned by Root and put the sticky with the following commands:

$ sudo sh

# chown root resetical

# chmod +x resetical

# chmod +s resetical

# ^D

Using QuickSilver (or Alfred or whatever), I just invoke "resetical" and it does its magic.

Thank you very much, wler711, for the solution.

I tried this but seem to have no AutoTimeZone cache to delete. Also I'm just a user, not IT so I haven't the foggiest idea what MikePet is talking about. Any further suggestions/instructions for luddites?

Also I realize I'm using Calendar not iCal.

My error message reads: Access to " " in "Work" in account "iCloud" is not permitted.

The server responded" "403" to operation CalDAVWriteEntityQueueableOperation.

With options to click: Ignore, Try Again, Revert to Server.

I would be happy to delete the entire event series and manually enter the events if I could.

Any suggestions?

Thank you Basic101, you made my day!

I have searched my cache folder for com.apple.AutoTimeZone.plist, but it does not exist!

So this issues JUST crept up for me today. I've review several posts, including this one, and looked at the following items:

1. Find and delete the "autotimezone.plist" file. I couldn't find it in ANY folder so I guess I've skipped this one.

2. Looked for reoccurring calendar events as recommended in a post on another site. I didn't have any so this can't be the issue.

3. Another post in a sire indicated that something might have "changed" in my Calendar settings with Microsoft365 and that I should look at the incoming server settings in Outlook and copy to Calendar. This too was NOT the case, everything was the same so I skipped this one as well.

4. I've switch syncing on and off, no changes, same errors occur.

5. Turned off ALL firewall settings to see if there might be a conflict there. No go, didn't help.

The ONLY thing I have not tried was the "~/bin/resetical" from above and since I'm NOT an IT guru I don't feel comfortable with this one. So, here I am, and my Calendar will NOT sync! Guess it's time to switch to OUTLOOK, since I'm getting the feeling that Calendar is a bit of a joke in a corporate environment. Unless someone can come up with a fix ASAP!

I see no cache file on my disk. Lame problem. My iPhone6 and iPadAir2 both fine.

Using all these machines for business. Why can't we get support for basic services??

Same problem here. Can't add or change any Office365 calendar events via Calendar on my desktop machine but it works fine via my phone. Between this fiasco and the jumbled email threads problem on Yosemite it is almost as if Apple is intentionally crippling their desktops and trying to drive business over to Windows. My Mac is now useless for any work-related efforts since neither Mail nor Calendar function correctly and I am having to spend countless hours and dollars trialing and paying for 3rd party software. Apple has seriously lost their way.

I found the resolution to my problem but forgot to post the solution. I apologize if this inconvenienced anyone with the same problem.

I thought it was a volume thing or something else. It turns out that Yosemite is NOT compatible with ALL versions of Exchange. If your provider is using an order version of Exchange, then you are likely going to have this problem. I had my provider upgrade the exchange to 2007 (2010 is the latest I believe), and everything started to works just fine. All calendar entries are just where they are supposed to be.

However I seemingly "lost" all my old and filed email. Turns out it is still there on the Exchange server using OWA. However my Mac thinks it was a completely new account so the "old" email is hidden way inside the Library folder on my computer. So if I really need an old email, I can find it one way or another (but no easy way to search for it).

Off topic, but relevant, there is a terrific program called Daylite that runs only on the Mac platform that has a helper app that links AND STORES all of your important email in its own database so you can delete it off of your Exchange server. You manually link an email to a particular project and/or person (often the program chooses correctly for you by itself) and the email is put in a format where you can keep it for the duration of the project and find it instantly. Its expensive my most standards ($300), but well worth it if you run your projects via email. I never have to worry about "old" email again. Nor having to search for email by subject or person. The email is cross referenced by person, date, project, and tag (optional). Works best if you are an all mac user with iPhone.

I don't know why people are trying to rely on rumours instead of just looking into the log files to determine what's wrong with their iCal. There are multiple reasons why you can see the exclamation mark and not able to sync with the Exchange server. Most of these are due to the poor implementation of the iCal application: instead of notifying the user re: the encountered problem and giving the user an option to ignore the error the developers thought that it's much more user-friendly just silently stuck on the error.

Anyway, there multiple incompatibilities when iCal talks with Exchange servers, the one I currently have manifests itself with the following in the logs (you can see the logs if you launch the Console application):

===

2015-07-10 13:24:25.293 CalendarAgent[250]: -[SOAPParser:0x7fd7335b6370 parser:didStartElement:namespaceURI:qualifiedName:attributes:] Type not found in EWSFileAttachmentType for IsInline (t:IsInline)

===

This particular error, if I understand correctly reports that a calendar entry in the stream of events has an unrecognised field (IsInline) with the type EWSFileAttachmentType. As far as I investigated it means that somebody has sent you an invite (and you accepted it) with an emoji embedded into the invitation (or a small image or something like that). The only way to mitigate this would be to locate such an event and either modify its notes not to include the embedded image or to delete the whole event completely.

I wish Apple was more supportive and stepped up the quality of their software products. Apple's hardware and design are beauties, while software becomes uglier and uglier with every year: take a fresh install of OS X and look into logs after the installation and see how many serious and critical errors reported there (and keep in mind - it's a fresh install and not user activities were performed there yet).

I have wasted so much time with Calendar! None of the above suggestions solve this problem. Given the countless threads devoted to discussing the Calendar-Exchange bug and the volume of people forced to use Exchange, Apple needs to fix Yosemite. Please! I cannot stand the thought of working in Outlook. My calendars work fine on the iPhone and iPad, so I know the issue is with Yosemite.

gm.outside THANK YOU!

I had some invitations with Strange signs (!"#!"%!@) that i saw on the web platform for my calendar. I Deleted them and now Calendar is working again.

Apple should fix this!

gm.outside, great suggestion to use the Console, rather than try possible fixes blindly.

Many of the messages in the Console are still very cryptic. Any suggestions on resources to assist in deciphering the messages?

For example, some console messages reference a record ID, which I think could be a specific Calendar entry. I have not yet found a way to map the record ID to the entries that I see via the Calendar app. In other words, even if I suspect the issue is a corrupt Calendar entry, I am not able to locate the troublesome entry in order to delete it.