create event in iCloud calendar receives error 507

When I moved to iCloud I deleted my local calendars. Therefore I don't have any Home or Work calendar on iPhone.

Altwegg solution was good! I found out that during the transfer from iCal to iCloud, something went wrong and I have a few events long in the past (2003 and 2006) repeated over 6.000 times each.

As soon as I deleted a bunch of them, everything started to work!!

It confirms the fact that error 507 is an exceeding quota error. It is a bit disappointing Apple doesn't reserved a bigger quota to calendars. 20.000+ events or not, my local copy of them doesn't exceed 2.5 MB for each calendar.

It will take ages to delete all of the copies, since I can't select more than one event at a time on iCloud. I can do it on iCal, but it slows down the app and it takes over 2 mins to delete about 60 of them.

I tried to re-import the .ics files locally, in order to do it without a parallel connection to the cloud and save time, but iCal get stuck with a rainbow wheel (I force quit after 25 mins). I guess it doesn't put up with the thousand copies in a day.

Anyhow, I am glad I solved the problem.

Thanks Chris anyway.

Hey Chris and Ascanio

Obviously we had different problems but got the same error "507" code. I have had duplications of my calendars from transfering from one computer to the other over the years. But when I solved the problem for myself it synced the calendars with the duplications so obviously, at least for me, it wasn't a quota problem.

It still doesn't make sense to me because whatever is used my iCal doesn't use up that much space, even if there are 20,000 entries. Think about how many words you would need to fill 1 gb?

I once tried Mobile me. I had so many problems with iCal that I dropped it. I thought Apple worked out the glitches in iCloud but obviously, they didn't.

It should be fairly simple to add a merge events option to iCal. If they did that, all the duplications would be taken care of.

At any rate I had a different problem then both of you. Am glad, everyone, at least found a way to work them out.

Hope Apple is listening. For people with little computer experience, iCloud could become very frustrating although it should be seamless.

They should definitely give you and option to sign out without deleting your calendar. They do for contacts but not for calendars. Why?

Obviously, to keep you signed in. It is not Apple like. I have been working with Macs for 25 years. I repaired them, troubleshot them and ran over 200 out of a school with very few major problems.

There is no reason for this kind of stuff. They do this with iTunes etc.too. Their defaults are usually to automatic which deletes whole libraries for no reason.

Their defaults should always be manual or at least give you that option. But they want you locked in. Again this is not Apple like.

Well guys, my calendars crashed after working this afternoon. Got the "507" message. Before I try Chris's solution, I will download a dupe deleter and see if this cleans up my calendars enough. I will post if it works. If not I will try Chris's solution. Why it worked perfectly this afternoon and not now, I have no idea. Just goes to show you what I wrote above probably has no relevance now. But why did it work?

Well guys, my iCal just got another "507" message. So before trying Chris's solution I am downloading an iCal Dupe Deleter from the web. So far I deleted my Work Calendar that had nothing much in it because I basically kept all the info in my Home calendar. Out of about 20,000 entries the deleter found 16,000 duplicates. Which it deleted and I restored. So far it looks like it is doing the trick. Anyway, if everything is working tomorrow I will post again.

Anyway, the upshot is that the "507" error code must relate to too much data. But it still makes no sense given what I said a few posts ago. But if this works then iCal has a data limit. If that's the case then Apple should post it so people know before they begin the process.

To be continued. If you want the dupe deleter in any case, let me know and I will post the site if everything is working.

OK guys. This seemed to have worked. Now all three of my devices are syncing again. I guess getting rid of the duplicates did the trick. I still think it is necessary to have the same Default calendars on all devices. It just makes sense. But the "507" error must be over quota entries as Chris found out. Apple should definitely post this or warn people before they sign on to get their calendars in order. Although, it really isn't that much data. icloud should be able to handle that. Imagine if you have purchased 5,000 songs in itunes. What would icloud do then?

I got the same "507" error. I've had massive problems with iCal dupes since "upgrading" to Lion many of which I think originated with Lion, Outlook for Mac 2011, Exchange Server, and my company "Bumbleberry" not playing nice. I've not found any Apps that I felt confident enough with to clean my iCal so I'm doing the "brute force" method and manually cleaning dupes from iCal on the iCloud server. It is slow and tedious but seems to work, the "507" error has gone away and now my MBP, MacPro, iPad, and iPhone seem to be syncing properly.

Lion, what a disaster, but I remain hopeful that Apple will get it sorted out. I've lost over 80 billable hours doing triage on my 2010 MBP so far. It seems that a "clean" factory Lion install is the solution. So for the price of a new MacBook Air I'm going to roll the dice that I can start with a clean slate and move forward, get my MBP wiped and do a clean install and gift it to my nephew. Let's hope it's a "win-win".

Hi Larry

This is the iCal dupe deleter that I used: http://download.cnet.com/iCal-Dupe-Deleter/3000-18512_4-196449.html

It worked very well and deleted all my dupes. Just make sure to back up you iCal just in case there is a glitch. It worked both on my iMac and Macbook Pro. It cleared up the problem easily and I already had Lion installed. Just be patient. I ended up with 16,000+ dupes. It will work but will take time. Was a seamless process.

What is your problem with Lion? It should have been seamless but there are certain things you should prepare prior to updating. Hear are some suggestions: 1. Before you update, check for updated drivers for your printers which you will install after updating. 2. If you use Photoshop or any of the Adobe Suite, Lion will only work with versions CS3 and higher 3. If you use MS Word or Office for Mac you need 2008 or higher 4. If you use Norton then they haven't updated yet for Lion. I suggest using Virus Barrier X6 which is a dedicated Mac product. It is cheaper and better in my Opinion. 5. If you use Quicken, it hasn't been updated either. I found another program which I like better called SEE Finance. Very user friendly and made for Mac.

There are some older apps that might not work but other than the ones I mentioned they were not significant. If you have any questions about Lion, let me know and I can see if I can help.

marksart,

Thanks for the suggestion, I'll give it a go.

I agree, Lion should have been seamless, I've had no problems with past OSX upgrades. I haven't had any of the problems you detail. Mine have been with iCal, address book, extreme system sluggishness, hangs, app crashes, and such. Still not sure I know the origin and frankly I shouldn't have to be that good with the guts of the OS, I don't get paid for debugging laptops.

On the finance side I dumped Quicken a long time ago and am using iBank which I like very much.

Larry

What kind of computer are you on? How old? Does it have intel chips? It could be a permission problem. Did you repair your permissions prior to the install? Did you update Lion as soon as you installed it?

Personally, I tried iBank and didn't like it. Had problems with it, contacted support which was of no help so I dumped it before the trial period was over.

No, you shouldn't have to debug a Mac but there might be a simple fix. You have just got to go through a troubleshooting procedure. Let me know how it goes.

Mark

I have also had the same 507 error. I spent an hour with the apple care person yesterday - with no useful solution.

The solution, for me, was:

• Exported all my calendars to my desktop
• Deleted all calendars from ical
• Shut down ical and icloud
• Opened ical
• Created new icloud calendars in ical to match my exported calendars
• Imported my calendars fom the desktop to the new ical/icloud calendars
• Calendars then reproduced in icloud

Have not had a 507 error since. This, for me, was a very easy solution with no risk.

It seems a good one. I have solved deleting a few duplicates (it took ages) directly on the iCloud calendars, but from iCal.

I wish I could use the Deduper or your method, at least to be able to delete the dupes.

I can't, simply because the dupes created during the transition to the cloud are so many (I have a few days of 2005 and 2006 with over 6.000 identical events on two different calendars) that I can't import the .ics file downloaded from iCloud.

Therefore, neither the Deduper (which just doesn't do the job even though i ran it three times, maybe because it works only on local calendar files) nor your procedure can be done. iCal just loops for hours, maybe struggling over the dupes.

Now I am stuck with cloud calendars, but luckily I got rid of the 507 error just by deleting a few tens manually on iCal.

Good luck everybody! 🙂

@

David

I put that solution in a while back. But after a while the 507 reappeared. The only solution then for me was the iCal dupe deleter that I mentioned a few posts ago. Meanwhile have not had the problem recur.

Ascanio

With the iCal dupe deleter you have to have patience. It deleted 16,000+ of my dupes. You have got to sign out of iCloud before you start the dupe deleter procedure. It sounds like you didn't do that.

Hi Mark,

No, I didn't sign out... but if I do, the calendars would disappear... so how could I run the deduper?