NoSuchMethodError: PrioritySchemeManager

[Patrick Löffler]

The change of the priority scheme fails.

2019-06-12 08:19:12,569 http-nio-8080-exec-21 ERROR [c.a.j.web.servlet.InternalServerErrorServlet] {errorId=e65e434d-6ebd-4a08-8db3-5ddb40c2843d, interpretedMsg=, cause=java.lang.NoSuchMethodError: com.atlassian.jira.issue.fields.config.manager.PrioritySchemeManager.assignProjects(Lcom/atlassian/jira/issue/fields/config/FieldConfigScheme;Ljava/util/Set;)V, stacktrace=java.lang.NoSuchMethodError: com.atlassian.jira.issue.fields.config.manager.PrioritySchemeManager.assignProjects(Lcom/atlassian/jira/issue/fields/config/FieldConfigScheme;Ljava/util/Set;)V
at com.atlassian.jira.issue.fields.config.DefaultPrioritySchemeService.assignProjects(DefaultPrioritySchemeService.java:98) [classes/:?]
at com.atlassian.jira.web.action.admin.priorities.AssociatePriorityScheme.run(AssociatePriorityScheme.java:128) [classes/:?]
at com.atlassian.jira.web.action.admin.priorities.AssociatePriorityScheme.doExecute(AssociatePriorityScheme.java:91) [classes/:?]

.... 

[Patrick Löffler · Accepted solution]

The problem was that our provider made a mistake during the update. Not all files were taken over from the new installation. So there was still an old Jira API in the installation directories.

[Adrian Stephen]

Hi @Patrick Löffler 

Please try the resolution here:

• https://confluence.atlassian.com/jirakb/jira-server-fails-to-start-or-functionality-fails-with-classnotfoundexception-in-logs-278069832.html