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

Hi All,

I disabled Calendar syncing in iCloud preferences then restarted Calendar about 5 times. Then I re-enabled syncing and so far it works for me.

I THINK this worked. AMAZING........THANK YOU..........

Anytime!

NOTHING WORKS to get rid of this error in Yosemite. What is going on with Apple. Why can't they fix this. #2

Apple is the new Microsoft???

I have corrected the issue FOR THE MOMENT. It does reappear but for the most part it is working.

Here is what I did.

Deleted iCloud in Calendar including deleting everything from my mac when it asked to "delete from mac". I also did the same thing on my laptop concurrently.

I closed calendar and reopened it several times to make sure it was blank on both computers.

Then I added the iCloud account back on both computers and it seems to be working fine for the moment.

I did all of the above only on my desktop the first time and not my laptop and as soon as I opened calendar on my laptop all the errors reappeared. BUT......when I deleted iCloud on both my laptop and my desktop and then added iCloud back in it seems to be working.

I don't know WHY Apple is not fixing this issue. They are looking more and more like Microsoft all the time. Release software and let the customer pay for it and work out the bugs for them. Unfortunately they aren't fixing the bugs very quickly.

This issue can have so many causes, which is why it is hard to fix. My particular version of this issue is caused by an invite sent by someone else using outlook/entourage etc. I haven't asked the person concerned yet to try deleting the appointment because it's a business contact and I don't want them to think I'm inept! But I would like some help on this issue. Any Apple software developers in this thread?

I had this same issue from someone sending me an appointment from another computer. I had them delete it and it didn't help at all. The only thing that has worked......and fortunately is still working at the moment.......is deleting iCloud from my calendars on ALL my computers, restarting calendar a few times with nothing in it.......and then adding iCloud back in. So far so good but Apple needs to address this issue. They just seem to ignore it for some reason.

That's the best solution I could come up with too (MikelusAngelus). At least it's quick.

In my case (somewhat ironically) this was an appointment sent to me from Apple Support, and being saved to one (any) of my iCloud calendars on my Mac.

Select [Ignore] from the error box (Access to “Appointment with Apple Support” in “Work” in account “iCloud” is not permitted.) This puts the event on the local calendar but it can't be sync'd to the server - iCloud (web) does not show the event.

Then Duplicate the event on the Mac and edit it (change the title slightly so you can tell the two events apart).

Delete the invitees (Apple Support in my case) otherwise they will get sent an invitation to your duplicate event.

Delete the original event (or select [Revert to Server] next time the error pops up - e.g. by clicking the /!\ icon).

Pretty much the same happens if I try to read the invitation e-mail and open the .ics on my iPhone, except no error message. The appointment shows on my iPhone Calendar but is not sync'd to iCloud, whereas the Duplicate event is sync'd across all devices and iCloud.

I don't know if the inviter (Apple Support) got any kind of acceptance, or worse, might see it as declined when I deleted the original event?

(Yosemite 10.10.2 / iOS 8.1.3)

I've finally, after much deliberation, taken a different approach. I've grown weary of spending more time trying to fix Apple software than enjoying productivity with it. Seriously - manual repairing, with Terminal, no less, a problem that's plagued iCal since 2012? And, you'll notice, the fix is temporary. I've just found better solutions and abandoned the Apple Beta train, because, let's face it, current Apple software is simply horrid.

I've been a Mac enthusiast and evangelist since I first started using Apple products in 1986, but the company, on the software side, has completely lost its way. The list of apps that either simply don't work (Come on down, AirPlay and iWork!) is too long for this to be a minor or incidental problem. It's pervasive. And the calendar function on my computer and mobile devices is too important to trust to a faulty and bug-ridden application.

This isn't a rant - it's a solution - abandon the Apple offerings and go with third party solutions, spend your time getting things done, rather than wishing iCloud would just work. Like it's supposed to.

I have the same problem. The server responded: “403” to operation CalDAVWriteEntityQueueableOperation."

None of the many fixes mentioned in this thread fix the problem permanently. Most work temporarily but the problem always returns. I believe this problem is definitely related to iCloud and not OS X Yosemite.

My problem began when I tried to upload a series of NASCAR 2015 events to an iCloud calendar. I have done previously for many years without a problem. I created a .ics file containing all the NASCAR events using the iCalendar Specification protocol and TextWrangler. Then I import the .ics file into an iCloud calendar and I get the error every time. Importing the .ics file to a local calendar on my Mac (non-iCloud) works perfectly - no error.

So, until Apple quashes this bug I am using the following pathetic work-around. In order to get the faulty iCloud cloud calendar to appear on every one of my iOS devices, I export the offending calendar (from Mac: Calendar > File > Export), save it to my desktop, then email it to myself. From each iOS device I open the email and import the calendar. Again, I do this on each iOS device. Stupid but works for me. Back on my Mac, I just create and use a local calendar rather than iCloud.

YES. My issue was with a webinar "add". I edited the info down to just the link, deleted the original and manually added the event back in. Worked.

Thanks for the tip on how to make sure that I found the error in Console. I managed to find a work around by opening the *.ics in an different copy of Calendar than the one associated with iCloud. Then I dragged-dropped the instance into my iCloud calendar. I still got the error but the instance stuck.

Here's my error:

2/16/15 11:23:07.364 AM mdworker[57868]: code validation failed in the process of getting signing information: Error Domain=NSOSStatusErrorDomain Code=-67062 "The operation couldn’t be completed. (OSStatus error -67062.)"

2/16/15 11:24:41.954 AM Finder[335]: Layout still needs update after calling -[TListScrollView layout]. TListScrollView or one of its superclasses may have overridden -layout without calling super. Or, something may have dirtied layout in the middle of updating it. Both are programming errors in Cocoa Autolayout. The former is pretty likely to arise if some pre-Cocoa Autolayout class had a method called layout, but it should be fixed.

2/16/15 11:24:45.538 AM Console[57883]: Failed to connect (_consoleX) outlet from (NSApplication) to (ConsoleX): missing setter or instance variable

I noticed that I can create events manually and they are added correctly, but trying to add an ics file (supplied with the genius bar confirmation email no less) fails with this error and keeps failing until I hit "revert to server".

Annoying.

I found it could happen with an email mismatch.

Did you receive the ics file in an email account which is different to the account for ical? I think this happened when I was looking into it but can't remember if this was the cause.

This just worked for me. When clicking on an ICS file, I would get the 403 error. Another post in here got me thinking about what happens when I double click the .ics file. I did a get info on the .ics file and Yosemite was using CalendarFileHandling. I changed it to Calendar and no more 403's so far.