i have the same exact problem

had a calendar that was set up just fine, worked properly for months,
and then all of a sudden the error message i get is:
Request for account "Google:Bills" failed.

The server responded with
"HTTP/1.1 400 missing body in REPORT request"
to operation CalDAVAccountRefreshQueueableOperation.

i have 4 other calendars set up to sync with my iCal - they were set
up at the same time as the problematic calendar, and they all still
work.  i've tried removing, and re-syncing the problem calendar using
Calaboration, and still the same error - any advice?? is this
something i can fix with some direction, or is it a problem on
Google's end that is being worked on?

On Feb 11, 7:46 am, killerdemouches <[email protected]> wrote:
> Same issue here:
>
> Here is what i got in the console:
>
> 11/02/09 13:42:42 iCal[4968] CalDAV CalDAVCalendarRefreshOperation
> failed: status 'HTTP/1.1 400 missing body in REPORT request' request:
>
> <?xml version="1.0" encoding="UTF-8" ?>
> <x0:calendar-multiget xmlns:x0="urn:ietf:params:xml:ns:caldav"
> xmlns:x1="DAV:"><x1:prop><x1:getetag/><x0:calendar-data/></
> x1:prop><x1:href>/calendar/dav/
> [email protected]/events/
> 6755BFF6-5D71-11D9-90AB-000D93ADD41E.ics</x1:href><x1:href>/calendar/
> dav/[email protected]/events/
> 42A2857D-833D-11D9-B454-000D93ADD41E.ics</x1:href><x1:href>/calendar/
> dav/[email protected]/events/
> 6755FFE2-5D71-11D9-90AB-000D93ADD41E.ics</x1:href><x1:href>/calendar/
> dav/[email protected]/events/
> 6C608BF2-318B-11D9-A182-000D93ADD41E.ics</x1:href><x1:href>/calendar/
> dav/[email protected]/events/
> 675585BC-5D71-11D9-90AB-000D93ADD41E.ics</x1:href><x1:href>/calendar/
> dav/[email protected]/events/
> 6755810A-5D71-11D9-90AB-000D93ADD41E.ics</x1:href><x1:href>/calendar/
> dav/[email protected]/events/
> B08F5EE9-81B5-11D9-827A-000D93ADD41E.ics</x1:href><x1:href>/calendar/
> dav/[email protected]/events/
> 13D6CB02-833E-11D9-B454-000D93ADD41E.ics</x1:href><x1:href>/calendar/
> dav/[email protected]/events/
> A725E579-79F9-4E68-8EAC-32297AA5D7BB.ics</x1:href><x1:href>/calendar/
> dav/[email protected]/events/
> 58344E28-833C-11D9-B454-000D93ADD41E.ics</x1:href><x1:href>/calendar/
> dav/[email protected]/events/
>
> I don't know if it's normal, but the XML seems cut...
>
> Vincent
>
> On 12 jan, 20:20, dsm <[email protected]> wrote:
>
> > The client is ical(V. 3.0.6) on a Mac (V. 10.5.6)
>
> > The link you provided leads to the "Calaboration" tool which is what I
> > used to create the link between my calendar and Google in the first
> > place (i.e. it created the URLs to Google).  The calendars synched the
> > first time, but since then I am repeatedly getting this error.
>
> > Is there any way to fix this?
>
> > Thanks,
> > Dave.
>
> > On Jan 9, 7:03 pm, Trevor Johns <[email protected]> wrote:
>
> > > On Jan 8, 2009, at 10:00 PM, dsm wrote:
>
> > > > I'm having the same problem with the same error message.   How do I
> > > > unsubscribe and when I re-subscribe, what address should I use?
>
> > > > The CalDAV URL is /calendar/dav/[email protected]/events/
> > > > The account URL 
> > > > ishttps://www.google.com/calendar/dav/username%40gmail.com/user
>
> > > > Please let me know if there is a fix for this.
> > > > Thanks!
>
> > > The process to unsubscribe depends on which CalDAV client you're using.
>
> > > The URLs you should be using are documented at:
>
> > >        
> > > http://www.google.com/support/calendar/bin/answer.py?hl=en&answer=99358
>
> > > One thing that looks odd is that your CalDAV URL doesn't have a  
> > > protocol or hostname (https://www.google.com), so you may want to add  
> > > that.
>
> > > --
> > > Trevor Johns

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Calendar Data API" group.
To post to this group, send email to 
[email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/google-calendar-help-dataapi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to