Since you noticed that there are service desk modules disabled, that likely is the cause here. What is not clear here though is why those are disabled.
I would recommend making sure that your Jira instance has a sufficient amount of JVM memory allocated to it per the JIRA Sizing Guide - Atlassian Documentation and from there if need be follow the steps in Increasing Jira application memory - Atlassian documentation in order to make sure that Jira has sufficient resources to load this plugin and all of it's modules on your server.
That is the most common cause for this kind of problem. However after to do this and restart Jira, it's possible these modules might have been flagged as disabled in the database. If that happens you will see entries for this when running the SQL query:
select * from pluginstate;
It might be necessary to Stop Jira once more, and remove the entries from that table so that these modules/plugins can startup again when Jira starts.
Try these steps first. If this does not resolve this problem please let me know. It might be necessary for us to generate a support ticket for this case in order to get more logs from you to better understand the cause here.
Regards,
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.