Previous 1 5 6 7 8 9 10 Next 148 Replies Latest reply: Feb 26, 2016 1:14 AM by Duckberg69 Go to original post
  • Seguerski Level 1 Level 1

    I get the same error, but it seems to be on iCal events sent to my @icloud email versus @me email...

    if the same event is sent to @me, i can accept, but it seems to me that deep-down in Apple's systems, that the MobileMe /iCloud convergence isn't really fully associated.  I have a Case that I'm actively in with Apple support.

     

    the weird part, in my case, is that the originating iCal events are from an iCloud account to another iCloud account.

  • dj ikhan Level 1 Level 1

    I am having this same error...any fixes?

  • nickschick Level 1 Level 1

    @baraktorvanThanks this simple approach worked for me

     

    I backuped my calendars (File-Export-Calendar Archive), quit Calendar, deleted the Calendar Cache, reopened Calendar,  then reimported my calendars (File-Import-Import and choose your file.

  • CassiusLeGrande Level 1 Level 1

    @Donald M. Filicetticthis helped me, thank you very much ;  )  But unfortunately when i try to add new entries it comes up with the same message...

  • MacSavvyIT Level 1 Level 1

    This worked for me after deselecting Calendars from my iCloud control panel. Re-enabling Calendars "Merged" the information in the cloud with information "On my Mac"

     

    All is well - Apple now *****.

  • nevotheeb Level 1 Level 1

    FWIW I receive this error whenever creating a new reminder in iCal on my Macbook Pro (mid 2010, OSX 10.7.5).  I only have one @me.com account syncing across the board, iphone to macbook.

     

    "Access to [new reminder in iCal] in [reminder category] in account [my @me.com] is not permitted."

     

    However I CAN create a new reminder on my iPhone, which syncs quickly to iCal via iCloud, then I can modify that reminder - with no error - in iCal on my macbook.

     

    I also can create new calendar events in iCal, as well as all other Mail items, on my macbook with no errors.  Only new reminders fail, regardless of how I try to apply changes, go offline, or any other variation of the process in iCal.

  • Jlw111 Level 1 Level 1

    Happens on my MacBook Pro (Retina, 13-inch, Late 2013, OS X 10.9.3)

    Just started today. No clue what caused it, but it might have been me changing my system time to five years in the future to get an achievement in stanley parable. I turned it back, but the issue still happens. The calendar still syncs, but I have to deal with the stupid notification everytime.

  • Jlw111 Level 1 Level 1

    fixed it. just deleted the event that was causing issues, quit ical, turned off icloud, restarted, turned icloud back on, and opened ical. Then i just made the event again manually

  • rowitech Level 1 Level 1

    Unfortunately this worked for a week or two, then started again with these annoying messages.

  • JJFlora Level 1 Level 1

    I posted the original request for help but I am still having the same issue - just happened again today. Disappointed in Apple's reponse - I ma not as confident that they address these types of issues - they would rather talk about the next device, the next app, the next ......

    I use this Mac for business and it is annoying to explain to customers that my calendar won't post meeting notices with recurring dates. Doesn't anyone at Apple attend meetings with recurring dates? Maybe they just play volley ball all day.

  • dsteele.net Level 1 Level 1

    Eureka!!!  It worked for me. Deleting the calendar cache solved the '403' error.  With my OS version, I couldn't find the path: ~/Library/Calendars/Calendar Cache, but I found it by doing a search for 'Calendar Cache' and removing it to Trash.  Thank you so much for posting the advice.

  • Harpmary Level 1 Level 1

    I am having similar problem with the “403 to operation CalDAVWriteEntityQueueableOperation." error message. I have no idea how to fix it - and it only happens when I get invites from Outlook via a PC. I find this frustrating because in my case, these are invites from clients at medium to large corporations  - so I can't easily ask them to fix the problem on their end. iCal has completely trashed and screwed up numerous invites from this client. I've read all the supposed fixes here - and either they're over my head in terms of my ability to apply the fix, or I simply don't have the time to screw around with the fixes. Too bad Apple doesn't care about this problem. The bottom line is that my clients and my income are more important than my loyalty to Apple. And if this problem continues (along with other crappy problems that seem to be happening with the Apple email client when it interacts with Outlook), I am just going to stop using my apple laptop. I am due for a new laptop anyway and will probably just buy a PC so I don't have to worry about my clients getting frustrated with me because I miss meetings, because the Apple iCal programmers are too incompetent, lazy, or petulant to fix a known problem.

  • Knightie Level 1 Level 1

    My solution was to create a new calendar. Change the entry that was giving me the problems to this calendar and then delete the new calendar with the problem entry. All fixed and all calendars sync properly.

     

    Hope this helps others.

  • Quickshot Level 1 Level 1

    lofro023 wrote:

     

    As some have suggested, deleting the calendar cache may work (it did for me).  It can be found at

    ~/Library/Calendars/Calendar Cache

    Of course, your results may vary.

    This worked for me. Very quick. Thanks.

  • 8383 Level 1 Level 1

    I have also experienced this 403 warning problem with Calendar App on Mabvericks. In my case with an incoming invitation from a non Mac user.  I found all the "solutions" on here confusing.  This is all I did.... 

    Accept the icoming invitation and select a calendar on your mac rather than in iCloud.  Then after it is showing on your mac open the event again by double clicking and change the calendar to whatever one you want in iCloud.  The "warning" just stops.

    That would tend to suggest it's an iCloud issue but I am sure some expert or other on here will disagree :-)

    Cheers

Previous 1 5 6 7 8 9 10 Next