Sync iCal with Yahoo calendar give a CalDAVAccountRefreshQueueableOperation error

@Nautipneu

I'm all for Google buying Yahoo (or Apple for that matter), but I don't want them to change my @yahoo.com address and don't want Google to impose their yucky gmail interface on me. Yahoo!'s webmail UI is far more friendly and elegant. It's just too bad they seem to go down the drain.

js

It seems Yahoo! solved the problem! I just tryed and CalDav sync worked fine.

Yep. Right this minute, it works for me too. But I'm not gonna say it's fixed until I see it stable for at least a week. I've had that same problem in the past too.

Same problem with google calendar... it appears to be something with iCloud and not Yahoo or Google.

Today 10/27/11 Both Google and Yahoo calendars working with iCal!

Sorry but it has nothing to do with iCloud even if I tought the same at first...

I see many posts already informing of this problem, but the last post was October 2011. I'm posting today to show that the problem is happening once again.

I have a MacBook Pro that runs the latest version of SnowLeopard. I can't install Lion on my laptop due to potential software incompatability issues. I've switched my calendar to Yahoo so that my laptop, iPhone & iPad can share a calendar. I did this on 4/11. Since then, I've been receiving this message after opting to go offline (going online was not allowed).

The server responded with

“HTTP/1.1 500 INKApi Error”

to operation CalDAVAccountRefreshQueueableOperation.

So whatever the problem was in October, it's baaaaaaack.

Is there anything I can do to make this message cycle stop?

I just quit using Yahoo CalDav: too unstable! I use my iCal at work as well as for personnal use, so it must work 24/7!

iCloud works 24/7... Thanks to Apple great job!

Same here. Not using Yahoo Cal anymore. Sync'ed my iCal on all my devices with my new iCloud account. And works great.

However, these days (for a little over a week I think) I do have problems with Mail accessing my IMAP Yahoo mail account (it keeps asking for my Yahoo Mail account pwd). Dunno if it's all related but it's getting really annoying. And I don't feel like changing email address.

Ditto - on the same

The server responded with an error.

The request for account “Yahoo!” failed.

The server responded with

“500”

to operation CalDAVAccountRefreshQueueableOperation.

iCal

Version 5.0.2 (1571)

Mac OS X

Version 10.7.3

Build 11D50b

I'm one of the people who wrote in about this problem last October, and—just to confirm—yes, as of this morning it's back. 😟

David

Interestingly, I have had this problem off and on for the last year, but it's not occurring this time as it seems to be with others. For me, it doesn't really matter as it became so frustating that I moved my Yahoo calendar over to Google calendar, which works flawlessly. I still have the Yahoo calendar account but don't use it.

I'd really recommend transitioning your calendars off of Yahoo and onto Google if this is a continuing problem for you.

And just on case you would like to migrate your Yahoo calendar to Google, it's easy and fast. Here's how:

1. In your Yahoo! Calendar account, go to Options, then select Import/Export.
2. Click the Export button in the Export to Outlook section. (Note: When your calendar contains more than one year's worth of data, divide the file into multiple, one-year segments and import them separately; otherwise, you may encounter errors.)
3. Save the CSV file to the desired location.
4. In Google Calendar, ensure that you've created the calendar that you'd like to migrate events to. Then, at the bottom of the calendar list on the left, click the Add down-arrow button and select Import Calendar.
5. Click Browse and select the appropriate file, then select Open.
6. From the drop-down menu, select the calendar to which you'd like to import events.
7. Click Import to complete the import.

My Yahoo calendar and iCal are now syncing properly again. 🙂

Right....until next time..... 😉

I am having the same problem with Google calendar - very odd - I have 2 computers and it happens on 1 or both of them, seems random. iOS devices don't have this problem - in my experience.