| Div | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
On this page
|
...
These are some generic tips and techniques to help resolve add-on installation or licensing problems. In many cases, installation problems are not specific to the add-on, but instead relate to general usage or issues with the Atlassian Universal Plugin Manager (UPM) or the underlying plugin system. Generally speaking, most recent versions of add-ons on this site are built using Atlassian's plugin 2 framework and all paid add-ons use Atlassian licensing support. Installation is provided by UPM. Licensing support is also provided by UPM except for older versions of UPM. If these tips don't resolve your issue, it is likely you will need to open an Atlassian support ticket.
If you see in product license errors, go to UPM and look at the details add-on information and license information. This is the information that needs to be reported to support.
License Problems
LICENSE_EXPIRED Error
Manage add-ons shows the add-on with the follow error:
License is for an older version and maintenance has expired.
This will show in situations where the installed add-on was built after the expiry date of your maintenance support. This is a valid error. You either need to get a more current license or un-install the add-on and install an earlier version that is within your maintenance window.
If this is not your situation, in some cases this error may show incorrectly on JIRA versions before JIRA 6.4 and Confluence versions before Confluence 5.7. This is a UPM bug UPM-4565.
Alternatives:
- Update JIRA or Confluence to a release where the bug is fixed. At least JIRA 6.4 or Confluence 5.7.
- Renew the maintenance for the add-on.
- Use a temporary evaluation license until you can resolve the issue.
...
Incompatible with Product License
After upgrading the Confluence license or upgrading the Universal Plugin Manager add-on, one or more add-ons stop working. When reviewing the add-ons in the Universal Plugin Manager, the text "Incompatible with Product License (wrong type)" is seen in the License Status field.
or functions report the following error message: Notify your Confluence administrator that "Bob Swift Atlassian Add-ons ..." requires a valid license. Reason: TYPE_MISMATCH.
- Update UPM to the latest level and retry - this will solve many cases (UPM-4783).
- Make sure you check all your other add-ons for similar problems!
- If you still have issues, contact sales@atlassian.com to have them generate compatible licenses for all the add-ons that need it. While you are waiting, consider:
- Reverting your Confluence license change until Atlassian generates new and compatible licenses.
- Get an evaluation license until a permanent license is available
- See this Confluence Knowledge Base item.
...
VERSION_MISMATCH Error
A license is invalid if the app's build date is greater than or equal to the license's maintenance expiration date. That is, if the license says that support is only available through 1/1/2012, then an existing installation of a app version with a build date of 1/1/2011 will continue working indefinitely, but if you install a new version built on 1/2/2012 or later it will not work with the old license.
...
- Go to UPM
- Enable all the add-ons that should be enabled
- If plugin still cannot be enabled:
- Uninstall the plugin
- Re-install the plugin
- You may need to re-install the license
- If plugin still cannot be enabled:
- Consider restarting the server
- Look in your server logs for installation errors and clues
- Depending on the information you find, either open a support issue with Atlassian support (UPM) or plugin vendor (something indicating it is specific to the plugin)
...
An error occurred while installing the add-on.
| No Format |
|---|
An error occurred while installing the add-on. Refer to the logs for more information. |
...
In some cases, the following Atlassian knowledge base item may help: How to Clear Confluence Plugins Cache.
LazyReference$InitializationException
After installing or removing add-ons in Confluence, there can be errors reported like:
| No Format |
|---|
com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.IllegalStateException: Cannot autowire object because the Spring context is unavailable. |
| Include Page | ||||
|---|---|---|---|---|
|
java.lang.LinkageError
This is a UPM/plugin framework issue with mismatched class versions of some license management code. Likely related to some other UPM or add-on upgrade or install that has occurred. Reference is UPM-3306.
| No Format |
|---|
javax.servlet.ServletException: Servlet execution threw an exception
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:313)
caused by: java.lang.LinkageError: loader constraint violation: when resolving interface method "com.atlassian.upm.api.license.PluginLicenseManager.getLicense()Lcom/atlassian/upm/api/util/Option;" the class loader (instance of org/apache/felix/framework/ModuleImpl$ModuleClassLoader) of the current class, com/atlassian/upm/license/storage/lib/ThirdPartyPluginLicenseStorageManagerImpl$1, and the class loader (instance of org/apache/felix/framework/ModuleImpl$ModuleClassLoader) for resolved class, com/atlassian/upm/api/license/PluginLicenseManager, have different Class objects for the type com/atlassian/upm/api/util/Option used in the signature
at com.atlassian.upm.license.storage.lib.ThirdPartyPluginLicenseStorageManagerImpl$1.call(ThirdPartyPluginLicenseStorageManagerImpl.java:61) |
...
Tables missing Common table capabilities expected from TBL, SQL, or similar add-ons.
Resolution Steps
Go to UPM and look for the TBLSORT as: Bob Swift Software - Table Sorter Library or Bob Swift Atlassian Add-ons - Table Library.
Make sure it is enabled! If not, enable it!
...