67691 Views Previous 1 2 3 4 5 6 … Next 128 Replies Latest reply: Feb 13, 2014 11:48 AM by quinncom Go to original post
This afternoon issues I had yesterday, besides the 403 Forbidden error, have gone away. I previously could not create new MobileMe calendars in iCal and have them stay there for more than 2 s, but can now.
An import into a new MobileMe calendar from an archive is currently progressing. This is the third time I am trying it. I aborted the previous attempt, because I got the
The calendar https://cal.me.com:8443/principals/users/n.nnnnnn/ could not be accessed. It may be in use by someone else. Try again later.
error. A second call to AppleCare resulted in the agent advising me not to change the calendar I am importing during the import in either iCal or on me.com. I had in fact done so.
Let's hope that this import proceeds without errors. I just have to be patient. This particular calendar archive is 5.1 MB in size and therefore might take a while.
The import finished, but I did get that CalDAVWriteEntityQueueableOperation for one of the imported events. I chose "Revert to Server", which caused the offending event to not be imported.
I checked in the source calendar, and, sure enough, the alarm for this event was set to go off 15 days before the event. Since the event is from 2003, I simply deleted the alarm and put it into a different calendar, which will go through the export from ON MY MAC, import into MobileMe, cycle later. We'll see, whether this is, for me also, the issue.
I just got off the phone with MobileMe support and learned that Apple acknowledges the issue and is working on a fix server-side.
In the meantime, when doing an import of an ICS file into MobileMe, the best way to deal with this is to "go offline," isolate the offending event by moving it to an "ON MY MAC" calendar specifically created for events causing the error, quitting and relaunching iCal, and doing this for all events that cause the error. When the import has completed successfully, the thing to do is to either change the alarm lead time of the problem events to something 7 days or less and moving them back to MobileMe, or to do so with out changing anything after Apple has provided a fix.
I did a test with iCal connecting to the calendar from a Gmail account. Those can be accessed via CalDAV, too. The interesting thing was that, when I set the alarm to 20 days out in iCal, once it had been synced up with the Google server again, the alarm lead time had been changed to 14 days (2 weeks). Likewise a lead time set to 10 days was changed by Google to one week.
Could it be that the CalDAV specification doesn't support lead times that reach into the range of the next higher unit of time? I.e., could it be that I can't, for example, set the lead time to 28 h, because that's in the range of days?
I am getting this error after upgrading a client's Calendar to the new iCal. Every birthday in his calendar is returning this error and I can't just quarantine the birthdays as they are mixed in with other events. It has also created multiple instances of events.
Impossible. If this is not sorted asap I will be moving everyone over to gmail caldavs.
Based on all the advice to date in this forum, (thanks everyone), I tried a couple of relatively simple approaches; one worked for a while, but the second one seems to be more lasting.
(A) Setting alarm e-mails on To Do Items to be a shorter time in advance of the event helped for a while. At first it seemed 7 days was the border between working and not working, but this did not always seem to be the case.
(B) The approach that is working (for me) at present is as follows:
(1) Whenever you get a 403 error, select the offline choice.
(2) Remove the alarm from the offending To Do Item.
(3) Do Calendar, Refresh All
(4) Repeat (1) to (3) until you get no more 403 errors. In my case, there were 6 To Do Items, (out of about 30), causing the problem.)
(5) Add alarms back to the offending To Do Items. (So far, I have only made these alarms an e-mail the day before the event.)
(6) Keep your fingers crossed…
If this does not work for you, then I can only suggest asking Apple for help; they used to be quite good at this type of support, but the competence level seems to have fallen. (As apparently has the competence level in making high quality software releases; they no longer seem to understand how to do an effective regression test, which is very troubling.)
Why don't you wanna follow my work around?
I posted a lot of time ago and I am using it from a moth: it seems to work fine.
Just in case you missed it, here it is:
"Ok! I think i got it!
let's download the busysync calendar free trial; then upload your data with it on MobileMe; then (if you really need) revert to the use of iCal.
I suggest instead to buy BusySync that offer many more option of iCal and works properly.
On the website you can find a couple of friendly guide to sync and use it.