critical : cannot activate Service Desk afeter Core setup

Question

Licence:SEN-9697068

Refer to previous bug number #JSP-400348  in Jira Core. Disabling service desk addon made the Create project working. It also disabled SD application.

Now when trying to enable SD again i have the following message:

An unexpected error occurred. Refer to the logs for more information.

In Logs :

2017-10-19 21:28:13,901 UpmAsynchronousTaskManager:thread-3 INFO ]1079x810x4 ivdn3r 52.17.41.117,10.0.2.71 /rest/plugins/1.0/available/featured [c.a.plugin.loaders.ScanningPluginLoader] No plugins found to be installed
2017-10-19 21:28:14,135 UpmAsynchronousTaskManager:thread-3 INFO ludovik.lacroix 1079x810x4 ivdn3r 52.17.41.117,10.0.2.71 /rest/plugins/1.0/available/featured [c.a.plugin.manager.DefaultPluginManager] Updating plugin 'com.atlassian.servicedesk.application' from version '3.8.2' to version '3.8.2'
2017-10-19 21:28:14,223 UpmAsynchronousTaskManager:thread-3 INFO 1079x810x4 ivdn3r 52.17.41.117,10.0.2.71 /rest/plugins/1.0/available/featured [c.a.plugin.loaders.ScanningPluginLoader] Removed plugin 'com.atlassian.servicedesk.application'
2017-10-19 21:28:17,128 UpmScheduler:thread-4 WARN ludovik.lacroix 1079x585x2 ivdn3r 52.17.41.117,10.0.2.71 /rest/plugins/1.0/ [c.a.upm.pac.PacClientImpl] Update check request may take longer because of the number of add-ons

Andy Heinzer · Answer

Hi,

These particular logs do not tell us any more information about why this might be happening.  I was able to take a look at the existing JSP-400348 and it appears that our support team is requesting more information from you there in order to continue to troubleshoot this issue.

I know that you previous encountered the steps in the KB hmm... we couldn't create your project due to an unknown error.  However with the current error we see in the only support zip provided on that cause, it would still seem to indicate the problem is in regards to a single user account having been added to a permissions scheme and that user account no longer existing in Jira.

I would recommend trying to run through the Jira data integrity checker to see if this can identify/resolve any data inconsistencies that might be causing this problem.   If this does not help, and the KB does not help, I would recommend generating a fresh support zip from this instance and post that to the JSP-400438 issue.

Regards,
Andy