CalDAVWriteEntityQueueableOperation

Van,

When I said that iCloud/MobileMe settings could have nothing to do with it, I was assuming that people were having trouble with Google Calendar (like the original question said). Obviously, if you were having these error messages for an iCloud calendar, it's a different story. Interesting that you had to apply such a complicated procedure, iCloud definitely does not appear to be very robust yet if it can't recover from a simple power outage on your computer. No user should ever be forced to use the command line for such a problem.

This post is a bit late, but for weeks I had the same problem as the OP. I tried deleting / re-adding the google account and many other things, but nothing worked. Finally, I went into my google calendar in a web browser and clicked settings, then calendars.

I found that I had created a new calendar a few months earlier. Then, a few weeks earlier, I had chosen not to display it in the web version of the calendar. This seemed to have caused the problem. Deselecting this calendar in iCal didn't help, and it was still giving me the 500 error. So, I just deleted the calendar in the web browser (since I didn't need it anymore).

I then went to the "Mail, Contacts, and Calendars" area in the System Preferences and unchecked and rechecked the "calendars" box for my google account. I don't know if that was actually necessary or not.

Now, when I click the "calendars" button in iCal, it only shows my main calendar and no more 500 errors.

I had the same problem using Calendar/iCloud only calendars.

I googled the solution and found this

• Go to system setttings and switch off “Calendar” in the iCloud Settings.

• Open “iCal” and close it on your Mac.

• Then switch on “Calendar” in the iCloud and open iCal again.

Problem solved.

I had similar/same problem and after a lot of searching - found the answer on another thread:

John Maisey London

Re: iCal cache is corrupted

Quit iCal. In Finder, from the Go menu select 'Go to Folder...'. Enter the path ~/Library/Calendars/ . A new Finder window should open. From that window move the file Calendar Cache to your Desktop. Re-open iCal.

If you try and manually find the folder you can't find it - so you have to copy and past the path from above.

It worked for me and now no error messages popping up every 30 seconds!

If it works, then you can delete the calendar cache file you've just put on the desktop as it will have already made a new uncorrupted one as you reopen ical again.

Hope that helps - John's answer certainly solved my problem.

I have the same problem and tried your solution.

When I removed the cache file, all the calendars were gone. Not wanting to lose all my calendars, I put the file back, overwrote the new cache file, but the calendar program continued to crash repeatedly until finally it worked again, with my calendars restored. Original issue not solved...

Yes, thanks Genjoke, this worked for me. But folks should be aware that this will revert your Mac calendar to the last successfully backed-up version. If you’re like me, almost always adding to my iCal on the computer, then this could mean losing a lot of items. I had to redo a few items, but it was worth getting rid of the every-10-minute error messages. Perhaps this could also work another way, which would be to do a similar thing on the iPhone or iPad, or whichever device isn’t your primary calendar?

Persisting with macOS 10.12.2 + Server 5.2 CalDAV. How to resolve? I do not know.

The error message has identical structure and seems may have identical root cause. I am not using Google or iCloud calendar services. This is just CalDAV running on Apples Server software.

This AskDifferent thread addresses this problem as of 10.12.2. But so far I was unable to resolve it here following some of the suggestions.

http://apple.stackexchange.com/questions/47484/why-does-ical-often-say-the-serve r-responded-403-to-operation-caldavsetpropert

Resolved. This was my own stupidity. I run server.app on an imac and had enabled wifi. thus the ip had changed and port forwarding was no longer working correctly. stupid me.