Team Calendars for Confluence displays 500 Error When using Export to iCalendar

Related content

  • No related content found

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

When using Team Calendars for Confluence built in function to Export to iCalendar, the export fails and a 500 Server Error is Displayed in the browser.

Oops - an error has occurred
logo System Error
A system error has occurred — our apologies!
For immediate troubleshooting, consult our knowledge base for a solution.
If you would like to receive support from Atlassian's support team, ask your Confluence administrator to create a support issue on Atlassian's support system with the following information:
a description of your problem and what you were doing at the time it occurred
a copy of the error and system information found below
a copy of the application logs (if possible).
Your Confluence administrator can use the support request form to create a support ticket which will include this information.
We will respond as promptly as possible.
Thank you!
Return to site homepage…
Cause
Stack Trace:hide
Referer URL https://xxxxxxx/calendar/mycalendar.action

 

The following appears in the atlassian-confluence.log:

2014-08-05 12:55:34,550 ERROR [http-8090-106] [common.error.jersey.ThrowableExceptionMapper] toResponse Uncaught exception thrown by REST service
– url: /rest/calendar-services/1.0/calendar/export/subcalendar/private/xxxxxxxxxxxxxx.ics | userName: <username>
javax.ws.rs.WebApplicationException: java.lang.NullPointerException

Cause

This issue normally occurs when an interruption of read and write permissions in the cache folder happens due to a connection issue or performance.

Workaround

Clearing the Plugins Cache will resolve this issue. You can clear the cache, by doing the following:

  1. Shutdown Confluence
  2. Ensure the user running Confluence has full read/write privileges to the confluence-home directory.
  3. Remove the following directories
    (warning) This will remove the plugin cache files only and will not permanently remove any plugins. These directories will be recreated during the next Confluence startup.  However, some third-party plugins may store metadata in these directories, so we recommend creating a temporary backup of the directories.
    • <confluence-home>/bundled-plugins
    • <confluence-home>/plugins-cache
    • <confluence-home>/plugins-osgi-cache
    • <confluence-home>/plugins-temp
    • <confluence-home>/bundled-plugins_language
  4. Start Confluence

Last modified on Mar 30, 2016

Was this helpful?

Yes
No
Provide feedback about this article

Related content

  • No related content found
Powered by Confluence and Scroll Viewport.