Team Calendars Plugin disabled after update
Asked by Talal C:

Hi Team,

|------------------------|--------|
| **Confluence Version** | 5.10.7 |
| **Build Number**       | 6441   |

After updating Team Calendar in confluence, plugin is disabled and there is a message saying to look at the logs.

Uninstalling, re-installing doesn't do anything.

Thanks.

here are the log exceptions:

2019-05-21 11:18:47,935 ERROR \[ThreadPoolAsyncTaskExecutor::Thread 178\] \[internal.dependencies.startup.DependencyWaiterApplicationContextExecutor\] fail Unable to create application context for \[com.atlassian.confluence.extra.team-calendars\], unsatisfied dependencies: none  
-- url: /rest/plugins/1.0/ \| referer: https://xxxx/plugins/servlet/upm/marketplace/search?q=team%20calendar \| traceId: 8d897a133c14b8b7 \| userName: xxxx  
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'calendarContentForRemovedSpacesCleanUpWatchDogTask' defined in URL \[bundle://248.0:1/com/atlassian/confluence/extra/calendar3/watchdog/impl/CalendarContentForRemovedSpacesCleanUpWatchDogTask.class\]: Unsatisfied dependency expressed through constructor argument with index 0 of type \[com.atlassian.confluence.extra.calendar3.contenttype.CalendarContentTypeManager\]: Error creating bean with name 'calendarContentTypeManager' defined in URL \[bundle://248.0:0/META-INF/spring/spring-components.xml\]: Bean instantiation via constructor failed; nested exception is java.lang.NoSuchMethodError: com.atlassian.confluence.core.DefaultSaveContext.builder()Lcom/atlassian/confluence/core/DefaultSaveContext$Builder;; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'calendarContentTypeManager' defined in URL \[bundle://248.0:0/META-INF/spring/spring-components.xml\]: Bean instantiation via constructor failed; nested exception is java.lang.NoSuchMethodError: com.atlassian.confluence.core.DefaultSaveContext.builder()Lcom/atlassian/confluence/core/DefaultSaveContext$Builder;  
at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:749)  
at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:185)  
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1143)  
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1046)  
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:510)  
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)  
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)  
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)  
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)  
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)  
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:772)  
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:839)  
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.access$1600(AbstractDelegatedExecutionApplicationContext.java:60)  
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:325)  
at org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)  
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:290)  
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:137)  
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)  
at java.lang.Thread.run(Thread.java:745)  
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'calendarContentTypeManager' defined in URL \[bundle://248.0:0/META-INF/spring/spring-components.xml\]: Bean instantiation via constructor failed; nested exception is java.lang.NoSuchMethodError: com.atlassian.confluence.core.DefaultSaveContext.builder()Lcom/atlassian/confluence/core/DefaultSaveContext$Builder;  
at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:275)  
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1143)  
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1046)  
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:510)  
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)  
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)  
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)  
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)  
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)  
at org.springframework.beans.factory.support.DefaultListableBeanFactory.findAutowireCandidates(DefaultListableBeanFactory.java:1192)  
at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1116)  
at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1014)  
at org.springframework.beans.factory.support.ConstructorResolver.resolveAutowiredArgument(ConstructorResolver.java:813)  
at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:741)  
... 19 more  
Caused by: java.lang.NoSuchMethodError: com.atlassian.confluence.core.DefaultSaveContext.builder()Lcom/atlassian/confluence/core/DefaultSaveContext$Builder;  
at com.atlassian.confluence.extra.calendar3.contenttype.DefaultCalendarContentTypeManager.\<clinit\>(DefaultCalendarContentTypeManager.java:50)  
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)  
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)  
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)  
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)  
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:147)  
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:122)  
at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:267)  
... 32 more


Answers:
author: Talal C
body: Hi Shannon,

re-indexing did not fix it either.

We will drop Team Calendar for now, until we either upgrade or find an alternative solution.

Thanks

comments: author: Shannon S
body: Talal,

Thank you for the follow-up. If you are still having issues and wish to proceed further, please let me know, as my next step is to create a support ticket for you so we can get a look at your logs.

Keep in mind, however, for this to happen, you will need to make sure you are on a supported version of Confluence.

Let us know if you have any trouble with that.

Regards,

Shannon


author: Shannon S
body: Talal,

I'm so sorry to hear that your Team Calendars application isn't starting as expected, and I'd love to help get you up and running.

Can you confirm with me the version of Team Calendars you upgraded to?

I would recommend the following steps found on this article, [Unable to Enable Team Calendars](https://confluence.atlassian.com/confkb/unable-to-enable-team-calendars-for-confluence-after-upgrading-plugin-to-version-2-5-0-or-higher-306350366.html).
> Update the plugin manager (`Confluence Admin >> Plugins >> Update` - the blue bar notification that requests you to update your plugin manager) and update **all** outdated plugins. Then clear the plugin 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**  
> After that, restart Confluence, and try to either enable or install the Team Calendars for Confluence 2.5.0 or higher again.

I wanted to also point out that your Confluence version has been End of Life for a few years now, and was recently the victim of a few security exploits:

* [Confluence Security Advisory - 2019-03-20](https://confluence.atlassian.com/doc/confluence-security-advisory-2019-03-20-966660264.html)
* [Confluence Security Advisory - 2019-04-17](https://confluence.atlassian.com/doc/confluence-security-advisory-2019-04-17-968660855.html)

**You are advised to upgrade Confluence as soon as you possibly can to avoid your instance being compromised.**

For more information, please review the FAQ my colleague has put together:

* [Confluence CVEs and common questions](https://community.atlassian.com/t5/Confluence-articles/Confluence-CVEs-and-common-questions/ba-p/1062634)

Once you've run through the advised fix and upgraded Confluence, if you're still having issues, please let us know, and we can look a bit further into the case.

Regards,

Shannon

comments: author: Talal C
body: Hi Shannon,

I tried your suggestions and same error.

Team Calendar version is 6.0.27

Thanks


author: Shannon S
body: Talal,

Thank you for confirming that.

The next step here would be to reindex Confluence from scratch. This can take a few hours and cause performance issues while it is running, so please make sure to schedule this during maintenance hours.

* [How to Rebuild the Content Indexes from Scratch](https://confluence.atlassian.com/confkb/how-to-rebuild-the-content-indexes-from-scratch-on-confluence-server-110035351.html)

Once you've completed that, if you are still having the issue, I would ask that you ensure that your Confluence instance has been completely upgraded to the latest version per my suggestion earlier.

If you have not yet upgraded, I wouldn't advise proceeding further on this until you are on a supported version of Confluence which is not part of a security advisory.

This will ensure that it isn't a past bug that is causing the issue, if it has since been resolved.

Thank you for your understanding!

Regards,

Shannon


Tags: confluence-server

server

team-calendars-for-confluence