Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Subscribing to Team Calendars from Microsoft Outlook Does Not Work

Buki Main Long
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 11, 2018

Hi there,

I've been trying to connect our Confluence Team Calendar from Confluence to my Microsoft Outlook 2016 app. I've followed the step-by-step instructions listed here:

https://confluence.atlassian.com/teamcal/subscribe-to-team-calendars-from-microsoft-outlook-251005307.html

It has you download and install a plugin for Outlook called the CalDAV Synchronizer. I’ve installed this and followed the instructions, but keep getting met with errors.

 

The included screenshot shows the settings I choose when using the subscribe button in confluence:

 1.png

The https://uisapp2.iu.edu/ is the url that you are directed to input into the CalDAV Synchronizer settings.

Here is a screenshot of my settings in CalDAV. When I press “Test or discover settings” I should be met with a list of available calendars with this connection info, but instead I get “No resources found”.

2.png

If I go ahead and hit “Ok” and save the profile, an error report is generated. Here’s a screenshot of that and I’ve included a raw text version of that report as well in case you would like it. It is below this screenshot.

3.png

<?xml version="1.0" encoding="utf-16"?>
<SynchronizationReport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<ProfileName>KSB Team Calendar</ProfileName>
<ProfileId>f407b25f-8d03-4855-bcc3-15fa6676a843</ProfileId>
<StartTime>2018-10-10T17:22:39.5788132Z</StartTime>
<LoadErrors />
<EntitySynchronizationReports />
<ExceptionThatLeadToAbortion>CalDavSynchronizer.DataAccess.WebDavClientException: Response status code does not indicate success: '405' ('Method Not Allowed'). Message:
&lt;!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"&gt;
&lt;html&gt;&lt;head&gt;
&lt;title&gt;405 Method Not Allowed&lt;/title&gt;
&lt;/head&gt;&lt;body&gt;
&lt;h1&gt;Method Not Allowed&lt;/h1&gt;
&lt;p&gt;The requested method REPORT is not allowed for the URL /.&lt;/p&gt;
&lt;/body&gt;&lt;/html&gt;

at CalDavSynchronizer.DataAccess.HttpClientBasedClient.WebDavClient.&lt;EnsureSuccessStatusCode&gt;d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at CalDavSynchronizer.DataAccess.HttpClientBasedClient.WebDavClient.&lt;ExecuteWebDavRequest&gt;d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at CalDavSynchronizer.DataAccess.HttpClientBasedClient.WebDavClient.&lt;ExecuteWebDavRequestAndReadResponse&gt;d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at CalDavSynchronizer.DataAccess.CalDavDataAccess.&lt;GetVersions&gt;d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at CalDavSynchronizer.DataAccess.CalDavDataAccess.&lt;GetVersions&gt;d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at CalDavSynchronizer.Implementation.CalDavRepository`1.&lt;GetAllVersions&gt;d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at GenSync.EntityRepositories.VersionAwareToStateAwareEntityRepositoryAdapter`4.&lt;GetFullRepositoryState&gt;d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at GenSync.Synchronization.Synchronizer`11.&lt;Synchronize&gt;d__27.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at GenSync.Synchronization.ContextCreatingSynchronizerDecorator`7.&lt;Synchronize&gt;d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at CalDavSynchronizer.Scheduling.SynchronizationProfileRunner.&lt;RunAndRescheduleNoThrow&gt;d__22.MoveNext()</ExceptionThatLeadToAbortion>
<ConsiderExceptionThatLeadToAbortionAsWarning>false</ConsiderExceptionThatLeadToAbortionAsWarning>
<Duration>00:00:00.1229901</Duration>
</SynchronizationReport>

 

I noticed there are several questions similar to this, but I have tried everything I can think of, including the step-by-step walkthrough. Just a few specific questions...

Is it possible the base url that we are being provided by confluence is incorrect?

Is it possible that our CAS authentication is causing a problem? If so, what would the work around be?

 

The two-way sync would be great to utilize if possible would simplify things greatly for us.

Thank you for your help!

-Buki

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events