Team Calendars 4.0.1 export to ICS fails
Asked by Chuck Gould:

Confluence 5.1.3 - Team Calendars 4.0.1  
=========================

After upgrading **Team Calendars** to **4.0** , 9 of the 11 calendars we had in use prior to the upgrade export successfully to an ICS file (as a backup mechanism), 2 of the calendars faile to export generating a **System Error** with the:

**Cause: Stack Trace:\[hide\]**

**Referer URL:** <https://wiki.iso.ksu.edu/calendar/mycalendar.action>

Any ideas why this is occurring?


Answers:
author: Chuck Gould
body: All,

For some reason 2 calendars that would successfully export and import before upgrading **Team Calendars** to **4.0** , coupld be imported, but not exported after the upgrade. As noted I was able to create a new calendar and move all events to that calendar and get to a point where I could export it. This procedure did not work with the second calendar.

Ultimately I had to manually recreate the second calendar from scratch. Fortunately it was one where there was little need for appointment history and few future events. By creating a calendar, moving one event at a time and testing the export feature I was able to narrow the problem down to repeating meetings that has a different repeating schedule than was offered by Team Calendars. The meetings were set to repeat on the first or second Thursday of each month with no end date in sight. Once one of these meetings was placed on the new calendar I could no longer export it.

So my problem is solved, but it was essentially a manual process of recreating the offending calendar with non-repeating events.


author: Chuck Gould
body: All,

I solved one of the calendar problems by creating a new calendar and then moving all the events from the calendar that does not export to the new calendar. After moving all the events, I have been successful in exporting the new calendar. I then deleted the original calendar.

I repeated this process with the second calendar and the new iteration of the second calendar still does not export. The only difference is it does have several repeating appointments with no end date. When I get time I will close those appointments with a specific future date and see if that helps. If not, the only recourse I see is to create a new calendar from scratch again and re-enter the appointments.

Any better ideas? This is frustrating....


author: Chuck Gould
body: I can easily reproduce the error. 9 out of 11 calendars export fine after the upgrade. 2 consistently fail to export. No specific event seems to cause the problem, I suspect somehow when it was converted it failed. The error is non-descript and has no detail that I can expand.

I have since created new calendars and successfully exported them so I think the issue is when the calendar was converted during the upgrade (if it was).

![](../../upfiles/Team_Calendars_error.png)


author: Chuck Gould
body: Both calendars exported to ICS fine before the upgrade. I added an event to one that was failing, saved teh event and exported it. The next time I tried it, the export failed. Both fail consistently now.

How do I provide a full stack trace? Need some guidance in that area.


author: hsuhailah
body: Can you easily reproduce the problem still? If so, reproduce the problem and paste the error that you're seeing in the UI here. What is the detail of the created event that seems to be the cause of the problem? Perhaps you can share the screen shot of the event setting here.


author: hsuhailah
body: Hey Chuck,

We can't see the error. Can you please provide the full strack trace? Did the two calendars were able to be exported to ICS without issue before the upgrade? Possibly, some/part of the contents in the calendar caused the export to be failing.


Tags: export

team-calendars-for-confluence