Unable to upgrade Team Calendars for Confluence to 4.2 or above. Migration to Active Objects failed.
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
Cannot upgrade to Team Calendars for Confluence 4.2 or above. The Active Objects (AO) tables do not contain data.
You may be unable to enable the Team Calendars for Confluence, or you may simply see empty calendars, or no calendars at all.
Cause
The migration task may not be automatically re-run if it fails. This is being tracked here: CONFSERVER-48585 - If the migration to Active Objects fails, it is not re-run on subsequent upgrade attempts
You may also have incorrect database configuration that is causing the migration to fail.
Resolution
- Check your database is configured correctly, with the rights roles/permissions. This varies between databases, see here for the docs for each database system.
- Run the migration again by going to
<your-confluence-url>/admin/calendar/migratetoactiveobjects.action
If you are still having trouble at this point, enable some extra logging and get in touch with Support:
- Go to Admin > Logging and Profiling
- Add
com.atlassian.confluence.extra.calendar3.upgrade.task
and set it to DEBUG level - Go to
<your-confluence-url>/admin/calendar/migratetoactiveobjects.action
and force the migration again - Disable the DEBUG logging
- Create a Support Zip and raise a Support Request