Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >
Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >
Looks like no oneâs replied in a while. To start the conversation again, simply
ask a new question.
I ignored it, took two aspirin and it went away. đ Seriously, it did disappear, but not because of the aspirin.
What happens if you go to iCal>Preferences...>Accounts, then either delete the MobileMe CalDav account listed and create a new account, or re-enter the correct password?
I ignored it, took two aspirin and it went away. đ Seriously, it did disappear, but not because of the aspirin.
What happens if you go to iCal>Preferences...>Accounts, then either delete the MobileMe CalDav account listed and create a new account, or re-enter the correct password?
I tried the elimination of the CalDAV account listed and created a new one and the same thing happened...; however, I only had to click the Revert to Server button once this time... FWIW. Odd bug tho. At the bottom of my Account settings, it says, " The server where this account is located doesn't allow you to see availability..." Isn't it my account? Oh well... I don't use iCal that much but for those who do, I bet it's a real hassle.
I'm also getting this error message multiple times a day. I click on Go Online and MobileMe syncs properly until the next time it pops up. I tried deleting my account in iCal and recreating it, but that didn't help. I participated in the CalDAV beta a few months ago, so I don't know if MobileMe is confused when it authenticates to sync to the new production server, but this error message is definitely becoming annoying.
I have three Macs, and all are experiencing this error message repeatedly daily. At this point, it seems to be happening hourly when it checks with MobileMe to see if anything has changed, even through Push is activated. At this point, I have no idea how to fix this. My MobileMe credentials are correct, but the server is apparently rejecting them until I tell it to try again when the error message pops up.
This just started happening over the past couple of weeks, more frequently as each day has passed, now happening hourly.
Does anyone have any ideas why this is happening, or how to fix it? An Apple Advisor suggested that I have a corrupted repeating event, but iCal doesn't give me any way to find out if that's true by identifying a bad event.
Me:
I get 2011-01-02 22:25:15.024 defaults[3457:903] There is no (CalMobileMeMigrationToCalDAVRequestUpgradeAfterDowngrade) default for the (com.apple.iCal) domain.Defaults have not been changed.imac-van-ons:~ Vink$
NOLAN:
That's fine, go ahead and close out of Terminal.
Then re-open iCal and your account should automatically re-add itself.
I have the same problem (frequent "Bad Gateway" errors).
I just tried the solution posted by Jeroen Vink.
When I came to the two "defaults delete ..." commands, I had neither key present, so I got "Defaults have not been changed" twice.
When I restarted iCal, it did NOT automatically add my MobileMe account. (But perhaps it's relevant that I already had a Google CalDAV account present.)
I had previously deleted and re-added my MobileMe CalDAV account and the problem continued. But I had not quit & restarted iCal in between. Now it has been an hour and the error has not recurred.
Tried all the solutions here and none worked. Used Apple chat and we finally figured out the problem (which may help any old legacy .mac members).
When we deleted my Mobile Me account (iCal > preferences > accounts > delete Mobile Me) and the screen came up when I went to add a new account, it defaulted to my .mac address. When I changed that to .me, everything sync'd. Unfortunately, it only took an hour to figure that out đ
I stumbled on the .mac problem after I had tried the nicely posted solution and it didn't work. The calendar has now refreshed and I will check my other computers to see if they too are getting the same glich. Thanks.