ical The server responded: “403” to operation CalDAVWriteEntityQueueableOperation., ical The server responded: “403” to operation CalDAVWriteEntityQueueableOperation.

Unfortunately this doesn't help…

Didn't change a thing for me either.

I too have automated created yearly ics files for NASCAR since they don't provide them for us on their site. 😟

This year under Yosemite (and I'm sure newer iCloud server software), same as you, they will not import without error into any calendar that is on iCloud. I cannot even move events one by one from a local calendar (where they import just fine!) into an iCloud-based calendar. If I Copy an event from a local calendar I can Paste it into an iCloud calendar but for more than just one or two events that would be impossible—and wouldn't help with meeting requests at all.

For those able to look, do the ics files that everyone is having trouble with on Yosemite include a ;TZID=something clause on either a DTSTART or DTEND line? And if so, what is your preference setting in Calendar for "time zone support" (under Advanced)?

After a long conversation with a senior Apple Support specialist where no resolution was given I continued to fiddle with this issue. I seem to have had complete success at getting around these "403 errors" by stripping out the ;TZID=something clauses from my ics file. That's not something that can be done for anyone having the issue with incoming meeting requests, etc., but I'd like to know if this theory holds up for anyone else that can manipulate their own ics file. If it does, it is possible that by enabling time zone support that ics files with this clause may work too—I haven't tried it.

BTW, I gave a sample ics file to the Apple Support specialist and it failed to import into his calendar too so we proved it wasn't something specific to my iCloud account. At the time I hadn't come up with the time zone idea so I didn't get a chance to ask him what his setting for that is.

I hope this helps someone else!

"by stripping out the ;TZID=something clauses from my ics file"

Well I did this, double-clicked and added it to my calendar with no server error but it exists nowhere in my calendar. It added the event to nowhere on no date at no time.

What I did (and now do) using TextWrangler (but TextEdit would probably work just fine) is highlight and DELETE all the (in this case) webinar description after the link, all the X_ALT_DESC and the subsequent HTML, save it, double-click and it worked fine.

Well, that's something @yalK. Perhaps without the timezone information for your entries they got scheduled for some portion of the day (or maybe even one day different than you had expected) that you don't see in Calendar. I'm guessing that you did a search for the event though and it didn't show up at all. If you'd be willing to share a sample event (with everything you want in it: nothing excluded) in an ics file I'll see what happens for me.

" I'm guessing that you did a search for the event though and it didn't show up at all. If you'd be willing to share a sample event (with everything you want in it: nothing excluded) in an ics file I'll see what happens for me."

Yep--that is exactly what I did. The reason I tried the editing is from an earlier post that indicated that iCal did not behave nicely with certain keyboard characters. I experimented and found that this rogue behavior occurred if the event contained keyboard-god-knows-what. So I started removing sections and adding the event until I found that by getting rid of all the irrelevent text under "DESCRIPTION" (keeping the link so I can use it) all the way to just before "BEGIN:VALARM" things seem to work. We really should not have to edit every invite but....whatever. Animated gifs inside of New Message should animate. Search box in Contacts should not have to be clicked twice to clear and search. Photo events on my iPhone should be alphabetized. But hey, "we'll get to it".

DropBox for orginal .ics:

http://tinyurl.com/nruebhs

You're right, @yalK!!! Having been a software developer in a prior life does remind me though that rarely does everything in a large system work perfectly… but it's not as if Apple can't afford more and/or more skilled developers. I bet they have thousands of "bugs" to work on and that must seem like it isn't worth it to even start.

I imported that ics file into an iCloud calendar without issue: http://web.myspecialdomain.com/mskinner/pics/Monosnap_2015-03-06_13-22-25.png and it synced to my iPhone intact. I do not know why it doesn't like you. 😉

Maybe time to write and applescript to clean these up before double clicking?

http://hints.macworld.com/article.php?story=20091215080321140

As several others contributing to this thread over the prior 9 pages of posts have done, I too had hope that I had stumbled onto something specific that could be "responsible". I found something that had kept my ics files from being usable in iCloud… @yalK found they had to do something else for theirs. Writing Automator actions isn't that difficult so for some people it would be an acceptable workaround but it may remain an exercise that fixes only very specific cases that aren't even universal to all users. Most users wouldn't try 😟 (nor should they have to!).

If we can collectively identify specific faults in iCloud's implementation of the ics file spec then Radars can be filed with Apple. Just the fact that I could not replicate the "403 error" using the exact same file that fails for @yalK points to the fact that nailing this down (from our outsider position) can be really hard to do. Of course even if we document what we consider bugs, Apple is free to implement the spec any way they like because they alone code the Calendar applications and iCloud's servers.

I also have this issue.

Had this issue today. Except the pop up window was coming up every couple seconds, I'd close the window and it would pop back up making Calendar virtually un-usable. Found a solution:

1. Go into Calendar and click Calendar - Preferences

2. Click Accounts

3. If you notice on the left an icon that says Google CalDAV; click on it and then un-check "Enable this account".

Totally solved the issue.

The only thing that worked for me is to drag the event from one calendar to another and then back to the original one. It was never being added to the server (iCloud) calendar. it was originally an Outlook invite sent to me which I accepted in iCalendar's inbox on my Mac but apparently couldn't sync to the server. When I logged into iCloud through Safari and checked my calendar, the event wasn't there. Once i moved it back and forth between two calendars on my Mac, it then worked and the error went away. This is the first time I've had that error message, but I have not been previously able to get updates (changes) from Outlook invitations to update my iCalendar events.

Spent more time than I care to admit trying fixes from this thread to no avail. What finally worked for me: edited the ICS file and removed a forward slash that was in the title of the meeting e.g. "Lunch: AC / DC" to "Lunch: AC DC." Problem instantly went away when Imported with the Calendar menu.

I have Yosemite and had this particular problem which started when I added a specific meeting to my calendar.

Let's call the event "Screwed Up Meeting" for the sake of example. Knowing this particular event was the cause of the problem, I brought up the Spotlight Search (clicking on the magnifying glass in the upper right hand corner of the screen, or pressing command + spacebar will do this).

In the Spotlight Search, I typed Screwed Up Meeting (the name of the event) and then selected the option to "show all in finder."

Now, I can't remember exactly what technical file directory it was in but I found the file named "Screwed Up Meeting" that looked like it was deep in the administrative bowels of the Mac, and moved it to the Trash (I didn't delete it, just in case totally deleting it REALLY screwed something up). (Note: if you have emails, attachments, or other calendar events with the same name, you might have to carefully determine which is the correct file to move - you can do this by looking at file extensions and other information to deduce which is the likely one that has to go - for instance one that ends in .jpg isn't likely to be the cause of your problem!)

After removing this file, I closed and re-opened Calendar and so far have not seen any recurrence of this error message.

You will note that I didn't have to delete or restore any accounts, or export or reimport the entire calendar, or anything like that. Those sorts of tactics would clearly be overkill. When it's clearly one event that's causing a problem then it's only that event that should have to be eradicated, and as demonstrated by the steps I took above, finding and eradicating that one event is made relatively simple through judicious use of Spotlight Search.

Of course, if you don't know what event is causing the problem, then you're on a goose chase. For that reason it's best to address this immediately as soon as the problem starts - by tracing it back to the last event that you added before the problem started.

Had the same problem when I was doing some freelance for a company and I was synced to the company email I was provided. I just went to: System Preferences/Internet Accounts.

From there I just deleted the Google account (under the iCloud icon) that had the temporary email and added my personal email.

FIXED!