„403” CalDAVAccountRefreshQueueableOperation.

I have the same issue. It started when I clicked to switch to iCloud drive when I updated my iPhone and iPad, not realizing that I shouldn't have done it until Yosemite was available for my computers. I thought it would stop once everything was up to date but I was wrong. All my devices are not updated and I can't use my calendar on my computer because every 30 seconds this pops up.

Access to account “iCloud” is not permitted.

The server responded:

“403”

to operation CalDAVAccountRefreshQueueableOperation.

I hope someone comes up with the answer soon.

For everybody who might be concerned or wants to become a hero of customer service. Those affected: Keep posting. Thanks.

iCal is not working for a number of iCloud users for more than a month. The annoying 403 error (of September 2014 and later) is very clearly on the iCloud server side - and only there.

For me personally it's not that much of a disaster but I am really glad that those professionals without any computer skills for whom I admin their iMacs are not affected yet.

A calendar is a critical feature.

After one month of rising frustration it would be very helpful IF APPLE WOULD WAKE UP and give this issue no rest until it is really solved, not only for any telephone agent who is probably not even aware of these forums here.

Yosemite iCal iCloud 403 error CalDAVAccountRefreshQueueableOperation - a minority of iCloud users get annoying error response every few seconds when using iCal or other calendars on Mavericks, Yosemite. This annoying 403 error message pops up every few seconds - even when the synchronization works fine.

Has anybody found a solution yet ?

I fixed mine! Hopefully, this helps others. Even though I kept receiving the "403 CalDAVAccount RefreshQueueableOperation" error when in Calendar or iCal, the problem was due to an issue with Reminders. Initially, I unchecked iCloud syncing for calendar and deleting my calendars folder in my library to no avail. After a few more days of frustration, I unchecked syncing for Reminders for iCloud in System Preferences and the error message went away. I ended up logging into the iCloud website and deleting all my reminder lists, including shared ones. I have since turned iCloud back on for Reminders and the error message is still gone from Calendar.

For the love of Steve, the 403 error has gone for now. This morning I still had the 403 error.

This is what I did most recently, I am not sure - at all - if this has something to do with the good news of today.

I am member of a "Family", I am not the organizer, but I logged in as the organizer and removed the Family-calendar-writing-rights for myself.

I logged in on the iCloud.com webpage into calendars and there I removed everything what was possible to remove.

At one remarkable moment (in my account) only the Family-calendar and two normal calendars of mine were left. I couldn't delete any of the two, both claiming to be the very last one and I needed at least one. Then I created a third and a fourth one which allowed me to delete calendar number 1 and 2. With number 3 and 4 left I was able to delete another one to have really only one in the end.

Then I figured out how to use Google with two-way verification (at Google) enabled on the Macs and I just switched over to the Google calendar cloud because I had enough of the iCloud calendars.

Then I read your comment and once more (I did this several times in the last 33 days) I re-enabled iCloud and suddenly the error 403 is gone for now.

I would like to marry Yosemite as it is now but I am still careful you know. 😍

After tearing my hair out, including quitting calendar on the Mac and waiting a while, I took the Micro$oft approach and closed the Mac down, went and made tea, came back, restarted it, and, as if by magic, all worked again. All I can assume is a gremlin in my connection to iCloud, which I use to synch my calendar between Mac and iPhone. Gremlin was at the Mac end.

I'm running 10.10.2 with all products up to date

I read loads of detailed technical solutions, even understood a few. Bu I decided to close down and wait a while before attempting them