Jira Service Desk app fails to load on startup

Still need help?

The Atlassian Community is here for you.

Ask the community

This article only applies to the Atlassian server platform. Learn more about the differences between cloud and server.

This Knowledge Base article was written specifically for the Atlassian Server platform and may be self applied.


ServiceDesk Application is installed but it is not enabled.

The following appears in the atlassian-jira.log, which shows ServiceDesk tries to load, but due to dependencies on different plugins it fails and disables.

2016-01-21 16:14:59,094 UpmAsynchronousTaskManager:thread-4 INFO <USERNAME> 969x32794x1 1doziyt /rest/plugins/1.0/installed-marketplace [c.a.plugin.manager.DefaultPluginManager] Found dependent enabled plugins for plugin 'com.atlassian.servicedesk.project-ui': [].  Disabling...


Looking at project administration, we can notice the project type is ServiceDesk, but the project does not have ServiceDesk items and behaviour per image below:


ServiceDesk Application requires several plugins to load prior to its loading process. Therefore if they fail, ServiceDesk will fail to load as well. 

pocketknife needs to be loaded first and after that client-resourcechaperone and email-processor. This can happen due to disabling plugins on earlier version of JIRA and after upgrade to JIRA 7, it can cause this issue.

Using below query we can figure out if mentioned plugins are disabled or not:

 select * from pluginstate;

If the result is as below:

                     pluginkey                   | pluginenabled
 com.atlassian.jira.jira-email-processor-plugin  | false
 com.atlassian.plugins.atlassian-chaperone       | false
 com.atlassian.plugins.atlassian-client-resource | false
 com.atlassian.pocketknife.api.commons.plugin    | false


Run below queries to enable the plugins:

  1. update pluginstate set pluginenabled='true' where pluginkey='com.atlassian.pocketknife.api.commons.plugin';
  2. update pluginstate set pluginenabled='true' where pluginkey='com.atlassian.jira.jira-email-processor-plugin';
  3. update pluginstate set pluginenabled='true' where pluginkey='com.atlassian.plugins.atlassian-chaperone';
  4. update pluginstate set pluginenabled='true' where pluginkey='com.atlassian.plugins.atlassian-client-resource';
  5. Restart JIRA after any database changes.
tip/resting Created with Sketch.

If you face any issue on browsing the project please refer to ServiceDesk, Existing Project Fails To Load, 500 error, RuntimeException.

Last modified on Sep 25, 2019

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.