Hi,

We’d need more information to diagnose this issue. Since you are filing a bug 
about Server.app, we’re going to send you through the non-opensource route so 
we can leverage diagnostic tools present in Server and OS X. Can you please 
file a bug at http://bugreporter.apple.com (doing this requires a 
developer.apple.com account - the non-paid kind is sufficient), and do the 
following:

1) Please run: sudo serverloggather

2) Please run: sudo sysdiagnose

Both of these tools will produce a diagnostic archive. The path to the archive 
is printed after the tool completes. Please attach both archives to your bug 
report. If you like, you can reply here with the bug number once you have filed 
the bug, so we can pluck it directly from the incoming ADC queue.

Thanks,
-dre

> On Mar 25, 2015, at 11:55 AM, Sean McBride <s...@rogue-research.com> wrote:
> 
> Hi all,
> 
> I had calendar working great on OS 10.9 / Server 3, but ever since 
> "upgrading" to OS 10.10 / Server 4 it periodically goes into a death spiral 
> where clients receive the following:
> 
> --------------
> Access to account “User Name” is not permitted.
> 
> The server responded:
> “403”
> to operation CalDAVAccountRefreshQueueableOperation.
> --------------
> 
> Stopping/Starting the calendar services fixes this for a day or so then I 
> must repeat.
> 
> Any suggestions on how to debug this?
> 
> Thanks,
> 
> -- 
> ____________________________________________________________
> Sean McBride, B. Eng                 s...@rogue-research.com
> Rogue Research                        www.rogue-research.com 
> Mac Software Developer              Montréal, Québec, Canada
> _______________________________________________
> calendarserver-users mailing list
> calendarserver-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/calendarserver-users

_______________________________________________
calendarserver-users mailing list
calendarserver-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/calendarserver-users

Reply via email to