Previous 1 2 Next 27 Replies Latest reply: Apr 16, 2012 8:41 AM by Psi
Joyseeker Level 1 Level 1
here is the screenshot ......http://gallery.me.com/joyseeker/100217/Screen-20shot-202010-07-15-20at-2011-59-4 5/web.jpg?ver=12791918490001

My problem must have started last week when I did a restore on the iPhone to see if its speed would improve. I noticed this week events added to the iPhone calendar were not updating the Mac and vica versa via Mobileme.

I realised then I had to switch on Mobileme syncing on the iPhone. Bingo syncing works again but now I get this popup error message regularly.

What am I not doing or enabling kind sirs?

MacBook 2Hz core 2 Duo, Mac OS X (10.6.4)
  • dartagnan64 Level 1 Level 1
    I get this too. As well as multiple duplicates of events when syncing. But I have no answers. Tried a permissions verification and repair and that didn't fix it.
  • Joyseeker Level 1 Level 1
    you have suffered in silence a long time.

    I seem to get the message every 15 mins (the refreshment time) only in the last couple of days.
  • Joyseeker Level 1 Level 1
    The problem is not me being on the iCal beta.

    Downgraded from the iCal beta today and the error message still appears on every sync.... yet events in iCal are syncing from what I can see!
  • Fixnfly Level 1 Level 1
    I have had the same problem and I believe I finally fixed it.

    I had my MobileMe account set up under the 'Accounts' tab of the Preferences in iCal. This section is for CalDAV or Exchange accounts (as the verbiage states). I also Checked the check box "Synchronize iCal with all computers and devices using MobileMe" under the 'General' tab.

    I removed my MobileMe account under the 'Accounts' tab, left the MobileMe check box checked (under the 'General' tab) and that seems to have fixed the problem.

    Of course that assumes you have MobileMe set up to sync your calendars in the main MobileMe preferences.

    If it comes back I'll let you know!

    Hope it helps.

    Message was edited by: Fixnfly
  • Henry Fields Level 1 Level 1
    That makes perfect sense! I kept thinking I needed to add my me.com account in the "Accounts" tab....ends up that is redundant. Thanks, Fixnfly!
  • Ninja Taka Level 1 Level 1
    That doesn't work because I'm on the new ical caldav system. So you need to have the account set up on the accounts tab. I unchecked the general tab though. No luck. Anyone else?
  • Elisabeth Freeman Level 1 Level 1
    I just upgraded to the new CalDAV iCal and am getting this error too. It's really annoying. I don't know about removing the account to try to fix it; I'm a little afraid I'd lose all my calendars if I did that.

    I do notice on the accounts preference tab that under availability, it says: The server where this account is located doesn't allow you to see availability.

    There definitely seems to be some kind of permissions problem with the new calDAV implementation.
  • Pappasbike Level 3 Level 3
    There is another thread going about the following error message in the iCal forum :
    The server responded:
    “HTTP/1.1 403 Forbidden”
    to operation CalDAVWriteEntityQueueableOperation.

    I have found that this is occurring for me only when I set a future event and then try to set an alarm to occur a specific amount of time prior to the event time. I've found that as long as I set the alarm to occur at 7 days or less prior to the event I get no error message and everything sets up and syncs properly through MobileMe. However if I try to set the alarm for greater than 7 days the error pops up and the event won't be created.

    It's been a while since I've tried to set an alert longer than a week before so I don't know how long this has been going on. Does anyone have any information on this.

    Message was edited by: Pappasbike
  • wassimk Level 1 Level 1
    My issue was also fixed by changing the reminders to 7 days. Anything beyond 7 days before and it gave the error. Odd.
  • NiCOOo Level 1 Level 1
    Same here!

    Only happen with an alarm longer than 7 days before. Also, there is no problems on iPad or iPhone...
    What a bug! Really annoying...
  • gitarzysta Level 1 Level 1
    +1 - what a pathetic bug
  • D. Hoffmann Level 1 Level 1
    I get the same error, when I am importing a calendar into MobileMe (via CalDAV) with items that have alarms more than 7 days out. The calendar I am trying to import is 37 MB in size and goes back to 1999 (it started life on a Palm III).

    My solution, which is very time consuming, when this error occurs is to

    1. change the alarm lead time to less than seven days,

    2. re-export the calendar to an ICS file,

    3. disconnect iCal from MobileMe (Preferences->Accounts->"-"),

    4. delete the old destination calendar on www.me.com,

    5. create a new, empty calendar on www.me.com,

    6. reconnect to the MobileMe calendar in iCal (Preferences->Accounts->"+"), and

    7. import the ICS file into the empty MobileMe calendar.

    It's a real pain! I really do wish, Apple would fix the issue very soon. During a chat with a MobileMe support agent I was informed that Apple was working on the CalDAVWriteEntityQueueableOperation, although she didn't offer any details and didn't appear to be aware of a connection with the length of alarm lead times.
  • MacMnstr Level 1 Level 1
    Thanks a ton, Fixnfly... Your fix worked for me! Sure wish Apple would put some more effort into their iCal/Mail/Address Book apps.
  • rc61austin Level 1 Level 1
    It will happen after or before more than 7 days.

    Another solution is to set the reminder message to "date" this will eliminate getting the error. Why iCal can't calculate it correctly is beyond me.

    Notification after an event has passed and for a certain date is pretty common especially for a calendar app...it's just a pain to figure out the actual day say 45 days from a given day.

    A really handy site for calculating dates for situations like this is http://www.timeanddate.com/date/dateadd.html
Previous 1 2 Next