8 Replies Latest reply: Sep 20, 2012 1:43 PM by rocky209
JRDuncan Level 1 Level 1 (0 points)
I have a Snow Leopard server running the iCal server. I have set up one account to host corporate calendars, and allowed all users to access and make changes to these calendars as delegates.

This setup has been working great for a few months now. Yesterday we suddenly stopped being able to modify the calendars. If anyone attempts to modify or add an event (including the host account) we get the error:

The server responded with an error.

The request for "event title" in "Calendar Name" in account "Account Name" failed.

The server responded with
“HTTP/1.1 400 Bad Request”
to operation CalDAVWriteEntityQueueableOperation.

Go Offline Revert to Server

I have backed up all of the calendar data. So, I could just delete the account and recreate it. However, I am not comfortable doing this without understanding the cause to we can prevent it from happening again.

Until now the iCal server has been a great productivity tool. I hope this will not become an ongoing problem.

If anyone has insight or an explanation please respond.

Thanks,

Rusty

MacBook Pro 2.33, Mac OS X (10.6.6)
  • 1. Re: “HTTP/1.1 400 Bad Request” to operation CalDAVWriteEntityQueueableOperation
    harry @ pmsi Level 3 Level 3 (535 points)
    Hi,
    You could look at the last post by Willhaus at http://discussions.apple.com/thread.jspa?threadID=1541735&start=15&tstart=0

    The problem seems to appear when there are multiple user accounts on the server with the same username. The Open Directory should be the only user database in use otherwise permissions and associations get confused. There can only be one user shortname in use on the system. Ensure a shortname is not associated with more than one user.

    HTH,
    Harry
  • 2. Re: “HTTP/1.1 400 Bad Request” to operation CalDAVWriteEntityQueueableOperation
    JRDuncan Level 1 Level 1 (0 points)
    Unfortunately my users are only in the Open Directory... If I open System Preferences and go to the Accounts pane, there is only one for the Administrator. (and a disabled Guest Account).

    I created the accounts using Workgroup Manager. I can also see them if I open the Server Preferences application and go to Users. But I don't use that program to manage them.

    The odd thing is that this setup has been working fine for months now and its a very active group...
  • 3. Re: “HTTP/1.1 400 Bad Request” to operation CalDAVWriteEntityQueueableOperation
    glev1 Level 1 Level 1 (15 points)
    I have just started having the same problem. The only difference is our users access the iCal Server calendar with one account and everyone using that same username/password. Has worked fine for a year and this started happening today.
  • 4. Re: “HTTP/1.1 400 Bad Request” to operation CalDAVWriteEntityQueueableOperation
    Jay Sayers Level 1 Level 1 (5 points)
    I've had this problem with my Snow Leopard server for awhile now. The problem most frequently occurs when accepting a notification from another user and the party doing the accepting attempts to place the event into a calendar other than the "default" calendar. Example:

    when accepting the invitation by clicking down the "OK" button, the user gets a popup listing the available calendars on the server. When simply clicking "OK", the problem doesn't appear, but when the user attempts to accept the item and indicating a particular calendar ( Personal vs Work ), the error pops up.

    Anyone experience the same occurrence?
  • 5. Re: “HTTP/1.1 400 Bad Request” to operation CalDAVWriteEntityQueueableOperation
    eyeless Level 1 Level 1 (35 points)
    Yes. THat finally made me realise that iCal cannot be used for sharing a calendar.
  • 6. Re: “HTTP/1.1 400 Bad Request” to operation CalDAVWriteEntityQueueableOperation
    °Bernz° Level 1 Level 1 (10 points)

    Hi everyone,

     

    If it can help anyone, I've had this error 400 for over a year on a single user account. Tried everything on the net, until I stumbled on this great thread:

     

    http://answerpot.com/showthread.php?3332921-Users+suddenly+unable+to+write+(Erro r+400+CalDAVWriteEntityQueueableOperation+)

     

    Turns out that by starting iCal in "debug mode" with this command:

     

    • /Applications/iCal.app/Contents/MacOS/iCal -LogHTTPActivity YES

     

    I was able to pinpoint my 400 error.

     

    Turns out that it was a very-very-simple error (or bug?) in the naming of a file. It had a "#" in the file name, and it was not converted on interpreted correctly by iCal.

     

    The error was the following (in the iCal log file):

     

    2012-05-02 00:42:37.980 iCal[21100:707] <html><head><title>Bad Request</title></head><body><h1>Bad Request</h1><p>URL may not contain a query or fragment: /calendars/__uids__/58CE709B-F0D5-4EF9-9BC8-CE1D2B0CC43D/dropbox/8860D75D-63B3- 4A72-A9D4-C105B1F12C61.dropbox/Your%20Reservation%20Confirmation%20at%20Holiday% 20Inn%20Hotel%20%26%20Suites%20-%20Confirmation%20# 64998111.pdf</p></body></html>

     

    I noticed that the space after the "#" was not converted to "%20", meaning that something was wrong...

     

    So I did the following:

     

    • Loggued in as root: sudo -s
    • Browsed to the user's dropbox folder: cd /Library/CalendarServer/Documents/calendars/__uuid__/.../dropbox/8860D75D-63B3- 4A72-A9D4-C105B1F12C61.dropbox
    • Renamed the file to remove the "#" from the file name

     

    Voilà! Now, no more error 400 for my user!

     

    Strangely enough, this file posted a year ago in my user's calendar blocked the ENTIRE calendar... Very strange.

     

    Hope this helps any other folks with this same strange issue! Good luck!

  • 7. Re: “HTTP/1.1 400 Bad Request” to operation CalDAVWriteEntityQueueableOperation
    awesomity Level 1 Level 1 (0 points)

    I have the same problem. All of a sudden, I can't write or delete events unless I go offline. I've also tried doing so on icloud.com and I got nowhere. I've also tried deleting the iCloud account off iCal then adding it again, nothing. I then saw Bernz' reply and was able to access the root profile but then had no idea how to access the files themselves...their path, I mean.

     

    I'm kind of in desperate need for iCloud at these times of finals and exams all around so I'd really appreciate it if someone had the time to help. The error part of the debug log is here:

     

     

    2012-05-15 19:43:10.104 iCal[1124:707]

    >>>>>

    2012-05-15 19:43:10.105 iCal[1124:707] PUT https://p05-caldav.icloud.com/278480740/calendars/AADD2181-D7CD-47F1-B2C3-04F8A8 38D8F2/DBF835BF-8870-4493-9033-F8D39C763D35.ics

    2012-05-15 19:43:10.105 iCal[1124:707] Content-Type: text/calendar

    2012-05-15 19:43:10.105 iCal[1124:707] If-None-Match: *

    2012-05-15 19:43:10.105 iCal[1124:707] Content-Encoding: gzip

    2012-05-15 19:43:10.105 iCal[1124:707] User-Agent: CalendarStore/5.0.2 (1166); iCal/5.0.2 (1571); Mac OS X/10.7.3 (11D50d)

    2012-05-15 19:43:10.106 iCal[1124:707] Content-Length: 392

    2012-05-15 19:43:10.106 iCal[1124:707] Cache-Control: no-transform

    2012-05-15 19:43:10.106 iCal[1124:707] X-Apple-Client-Info: <MacBookPro8,2> <Mac OS X;10.7.3;11D50d> <com.apple.coredav/1.0.1 (com.apple.iCal/5.0.2)>

    2012-05-15 19:43:10.106 iCal[1124:707]

    2012-05-15 19:43:10.106 iCal[1124:707] [compression: gzip]

    BEGIN:VCALENDAR

    VERSION:2.0

    PRODID:-//Apple Inc.//iCal 5.0.2//EN

    CALSCALE:GREGORIAN

    BEGIN:VTIMEZONE

    TZID:Africa/Cairo

    BEGIN:STANDARD

    TZOFFSETFROM:+0300

    DTSTART:20041001T000000

    TZNAME:EET

    TZOFFSETTO:+0200

    RDATE:20041001T000000

    RDATE:20050930T000000

    RDATE:20060922T000000

    RDATE:20070907T000000

    RDATE:20080829T000000

    RDATE:20090821T000000

    RDATE:20100811T000000

    RDATE:20101001T000000

    END:STANDARD

    BEGIN:DAYLIGHT

    TZOFFSETFROM:+0200

    DTSTART:20100910T000000

    TZNAME:EET

    TZOFFSETTO:+0300

    RDATE:20100910T000000

    END:DAYLIGHT

    END:VTIMEZONE

    BEGIN:VEVENT

    CREATED:20120515T174308Z

    UID:DBF835BF-8870-4493-9033-F8D39C763D35

    DTEND;TZID=Africa/Cairo:20120512T170000

    TRANSP:OPAQUE

    SUMMARY:New Event

    DTSTART;TZID=Africa/Cairo:20120512T160000

    DTSTAMP:20120515T174308Z

    SEQUENCE:1

    END:VEVENT

    END:VCALENDAR

    2012-05-15 19:43:10.106 iCal[1124:707]

    2012-05-15 19:43:10.106 iCal[1124:707] >>>>>

    2012-05-15 19:43:12.652 iCal[1124:707]

    <<<<<

    2012-05-15 19:43:12.652 iCal[1124:707] HTTP/1.1 400 (Bad Request)

     

    2012-05-15 19:43:12.653 iCal[1124:707] Content-Length: 124

    2012-05-15 19:43:12.653 iCal[1124:707] Content-Type: text/html;charset=utf-8

    2012-05-15 19:43:12.653 iCal[1124:707] Date: Tue, 15 May 2012 17:43:12 GMT

    2012-05-15 19:43:12.654 iCal[1124:707] DAV: 1, access-control, calendar-access, calendar-schedule, calendar-auto-schedule, calendar-managed-attachments, calendarserver-sharing, calendarserver-subscribed, calendarserver-principal-property-search

    2012-05-15 19:43:12.654 iCal[1124:707] Server: iCloudCalendarServer 1J59

    2012-05-15 19:43:12.654 iCal[1124:707] X-Responding-Server: st11p05me-caldav003 2

    2012-05-15 19:43:12.654 iCal[1124:707] X-Transaction-Id: 71200eba-9eb5-11e1-ad9b-78e3b51ce344

    2012-05-15 19:43:12.654 iCal[1124:707]

    2012-05-15 19:43:12.655 iCal[1124:707] <html><head><title>Bad Request</title></head><body><h1>Bad Request</h1><p>BADARG: Bad argument to function</p></body></html>

    2012-05-15 19:43:12.655 iCal[1124:707]

    <<<<<

    2012-05-15 19:43:14.861 iCal[1124:707] CalDAVOperationQueue tried to dequeue operation <CalDAVWriteEntityQueueableOperation: 0x7f871f049450; Sequence: 260> but it was not at the front of the queue.

    2012-05-15 19:43:14.864 iCal[1124:707]

    >>>>>

    2012-05-15 19:43:14.864 iCal[1124:707] GET https://p05-caldav.icloud.com/278480740/calendars/AADD2181-D7CD-47F1-B2C3-04F8A8 38D8F2/DBF835BF-8870-4493-9033-F8D39C763D35.ics

    2012-05-15 19:43:14.864 iCal[1124:707] User-Agent: CalendarStore/5.0.2 (1166); iCal/5.0.2 (1571); Mac OS X/10.7.3 (11D50d)

    2012-05-15 19:43:14.864 iCal[1124:707] X-Apple-Client-Info: <MacBookPro8,2> <Mac OS X;10.7.3;11D50d> <com.apple.coredav/1.0.1 (com.apple.iCal/5.0.2)>

    2012-05-15 19:43:14.864 iCal[1124:707] Content-Length: 0

    2012-05-15 19:43:14.864 iCal[1124:707]

    2012-05-15 19:43:14.864 iCal[1124:707]

    2012-05-15 19:43:14.864 iCal[1124:707] >>>>>

    2012-05-15 19:43:15.292 iCal[1124:707]

    <<<<<

    2012-05-15 19:43:15.292 iCal[1124:707] HTTP/1.1 404 (Not Found)

     

    2012-05-15 19:43:15.293 iCal[1124:707] Content-Length: 299

    2012-05-15 19:43:15.293 iCal[1124:707] Content-Type: text/html;charset=utf-8

    2012-05-15 19:43:15.293 iCal[1124:707] Date: Tue, 15 May 2012 17:43:15 GMT

    2012-05-15 19:43:15.293 iCal[1124:707] DAV: 1, access-control, calendar-access, calendar-schedule, calendar-auto-schedule, calendar-managed-attachments, calendarserver-sharing, calendarserver-subscribed, calendarserver-principal-property-search

    2012-05-15 19:43:15.293 iCal[1124:707] Server: iCloudCalendarServer 1J59

    2012-05-15 19:43:15.293 iCal[1124:707] X-Responding-Server: st11p05me-caldav026 16

    2012-05-15 19:43:15.293 iCal[1124:707] X-Transaction-Id: 72d48bc8-9eb5-11e1-8ced-78e3b51263b0

    2012-05-15 19:43:15.293 iCal[1124:707]

    2012-05-15 19:43:15.293 iCal[1124:707] <html>

              <head>

                  <title>404 Not Found</title>

              </head>

            <body>

                <h1>Not Found</h1>

                The resource /278480740/calendars/AADD2181-D7CD-47F1-B2C3-04F8A838D8F2/DBF835BF-8870-4493-90 33-F8D39C763D35.ics cannot be found.

            </body>

        </html>

    2012-05-15 19:43:15.293 iCal[1124:707]

    <<<<<

  • 8. Re: “HTTP/1.1 400 Bad Request” to operation CalDAVWriteEntityQueueableOperation
    rocky209 Level 1 Level 1 (0 points)

    Hi All-

     

    I did the following:

     

    1. Zimbra
    2. Preferences
    3. Calendar
    4. Scrool to the bottom of the page
    5. Click "enable delegation for apple iCal CalDAV Client"

     

    I can now create appointments/meetings, acceptmeeting invitations, etc.

     

    --rocky