Skip navigation

Mountain Lion Server calendar service not working after upgrade

4883 Views 12 Replies Latest reply: Sep 21, 2012 5:41 AM by no1tmorrow RSS
einord Calculating status...
Currently Being Moderated
Jul 30, 2012 2:17 AM

I bought Mountain Lion Server yesterday, and since then my calendar service is not working.


Everyting seems nice in the server app and when I try to connect any other mac to the calendar service via the system preferences (adding a OS X Server account and checking the calendar service).


But when I start calendar on the client I get the following error:

"The server responded with '500' to operation CalDAVAccountRefreshQueueableOperation".


If i try to open the calendar via the web server, I can login but only the message "Unable to access calendar, because an error occurred." is shown over the calendar view.


Any ideas of what the issue can be?

All other services is working properly (contacts, dns, file sharing and websites)

  • Critforce Calculating status...

    I am getting that same message and when I check the iCal Server error log it's throwing the following exception:


    2012-08-07 08:33:01-0600 [-] [caldav-1]  [-] [twext.web2.server#error] [Failure instance: Traceback: <class 'twistedcaldav.instance.InvalidOverriddenInstanceError'>:

    2012-08-07 08:33:01-0600 [-] [caldav-1]           /Applications/ edcaldav/method/

    2012-08-07 08:33:01-0600 [-] [caldav-1]           /Applications/ edcaldav/method/

    2012-08-07 08:33:01-0600 [-] [caldav-1]           /Applications/ edcaldav/method/

    2012-08-07 08:33:01-0600 [-] [caldav-1]           /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/twis ted/internet/

    2012-08-07 08:33:01-0600 [-] [caldav-1]           --- <exception caught here> ---

    2012-08-07 08:33:01-0600 [-] [caldav-1]           /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/twis ted/internet/

    2012-08-07 08:33:01-0600 [-] [caldav-1]           /Applications/ edcaldav/method/

    2012-08-07 08:33:01-0600 [-] [caldav-1]           /Applications/ edcaldav/datafilters/

    2012-08-07 08:33:01-0600 [-] [caldav-1]           /Applications/ edcaldav/datafilters/

    2012-08-07 08:33:01-0600 [-] [caldav-1]           /Applications/ edcaldav/

    2012-08-07 08:33:01-0600 [-] [caldav-1]           /Applications/ edcaldav/

    2012-08-07 08:33:01-0600 [-] [caldav-1]           /Applications/ edcaldav/

    2012-08-07 08:33:01-0600 [-] [caldav-1]           /Applications/ edcaldav/

    2012-08-07 08:33:01-0600 [-] [caldav-1]           /Applications/ edcaldav/

    2012-08-07 08:33:01-0600 [-] [caldav-1]           /Applications/ edcaldav/

    2012-08-07 08:33:01-0600 [-] [caldav-1]           ]


    And the Web Server Error Log is showing:

    [Tue Aug 07 08:29:47 2012] [error] [client] (70014)End of file found: proxy: error reading status line from remote server localhost:8443, referer: https://xxxx/wiki/projects/employeeresources/calendar

    [Tue Aug 07 08:29:47 2012] [error] [client] proxy: Error reading from remote server returned by /calendars/__uids__/wiki-employeeresources/, referer: https://xxxx/wiki/projects/employeeresources/calendar


    Message was edited by: Critforce

  • Mark Dannau Calculating status...

    @ Critforce and Einord.


    I was having the same problem, my wiki wasn't even recognized by the new ML server. So I did a full clean install, reconfigured everything and finally realized that calendar was not in the wiki anymore but a standalone that should be configured as a Webdav (actually Caldav).


    I do not know if there is some way to migrate the old calendar (wiki) in it and hope we will find some answers to that in the (very) near future.

  • aef5023 Calculating status...

    I had the same problem when I upgraded from Snow Leopard to Lion ( Nothing that I tried fixed the situation. There were 88 comments and counter comments to my question, but nothing resolved the issue. I gave up and reinstalled the server with a clean install from scratch. After the clean install everything worked perfectly fine, I did nothing whatsoever to "customise" the new server. Two weeks ago I upgraded to Mountain Lion, with exactly the same result. Everything is working except addressbook and calendar (I do not use much more).

    My suggestion, based on this previous experience, would be to roll back, if you can, find a way to export your contacts, calendar entries, other stuff and do a clean install. How to export / import what you need, I have no idea, the address book seems simple as there are vcard files saved somewhere on the server.

    Last time the upgrade also screwed up time machine so a roll back was not possible either.


    I guess an option would be to try the clever suggestion the experts had at the time, they might actually help this time, who knows.


    I hope things work out for you or a neat solution is coming forward.

  • aef5023 Level 1 Level 1 (5 points)

    as a matter of fact, there is another thread discussing the same Mountain Lion upgrade problem. There is a solution presented that work formthem (even, if no language problem is present, it might do the trick).

    I will try it out and see what happens

  • John Dasher Calculating status...

    I have this same problem after upgrading to Mountain Lion Server - the wikis work fine, but our Calendar yields the following error:


    Unable to access calendar, because an error occured.


    Also, I now have to enter my credentials twice to get to our wiki. Once on the main page, then after I select a wiki from the list I'm asked for the login credentials again.





  • no1tmorrow Calculating status...

    I am getting the same error as you John Dasher. Here is another weird caveat about this. My mac users that use Ical and Iphone works still. It is only on the wiki web page.




  • no1tmorrow Level 1 Level 1 (10 points)

    Update. I can access it via Ical, Iphone, and https it only gives me the error on http.




  • Critforce Level 1 Level 1 (10 points)



    Short of it: I used iCal to migrate all the appointments to a new Wiki calendar.  Did not reinstall.  Deleted old wiki and the error messages went away.


    1.  Add existing shared wiki calendars to iCal

    2.  Backup each shared calendar to it's own file.

    3.  Hide all but one original shared calendar at a time.

    4.  Shift-Click all the appointements for a single month or week.

    5.  Use the drop down menu to swtich them over to a new shared calendar on the new wiki.

    6.  Go do something else and give the server plenty of time to move the appointments, and they iCal to download the new appointments so you see them in the new calendar.

    7.  Rinse and repeat.


    I think the whole process took about 3 hours but the procedure is pretty quick so move some, work on other stuff for a while, move some more, work on other stuff etc...


    I couldn't afford to reinstall the server, too much setup to go through.  So to solve the problem I created a new Wiki with it's own calendar.  To move the millions of appointments, I added each of the shared calendars to iCal and created the same number of shared calendars on the new wiki.  Then in iCal I did a shift click on the existing schedules and just switched them to one of the new shared calendars.  There were five calendars with appointments scheduled every day up through December 31, 2012.  So it took quite a while for the appointments to synch with the server but they did eventually all move over.  I moved them from one calendar to the next a month at a time.  iCal will tell you that it is updating, so don't get impatient or else you will end up with duplicate or triplicate appointments.


    Warning: I had a few minutes of panic when all the old appointments dissapeared from one of the shared calendars but did not appear in the new calendar.  They weren't in the wiki calendar or my iCal so I was freaking out a bit, but eventually they started showing back up in iCal.  It just took longer than I thought it should.


    Message was edited by: Critforce

  • no1tmorrow Level 1 Level 1 (10 points)

    So instead of rinsing and repeating I added an redirect to the web server to force everyone to use https automatically. This has seem to resolve my problem for now.





  • John Dasher Level 1 Level 1 (5 points)

    We have the problem using https, unfortunately.

  • no1tmorrow Level 1 Level 1 (10 points)


    Well enabling the SSL fixed most everything except.....

    Now some Windows users when they login to the web calendar they get the usual login but then I get more of an Apache web login screen that the username and passord does not work. Then the calendar will not load. It is almost like the webserver is requiring authentication. I went to the Websites server control and SSL site allows Anybody to access it.






More Like This

  • Retrieving data ...

Bookmarked By (0)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.