Error Page 500 when opening projects after migrating to jira software 7.13.0

[Simon Kälberer]

Dear Community,

we upgraded to our Jira 6.4.11 instance to jira 7.13.0 via jira 7.0.11. After migration I received an unknown error when I tried to create a new project.

Accessing an existing project causes following error:

Verweiser-URL: http://localhost:8080/secure/project/BrowseProjects.jspa?s=view_projects

java.lang.reflect.UndeclaredThrowableException

java.lang.reflect.UndeclaredThrowableException

caused by: java.lang.reflect.InvocationTargetException

Caused by: com.atlassian.activeobjects.internal.ActiveObjectsInitException: bundle [com.pyxis.greenhopper.jira]

Caused by: java.lang.IllegalStateException: Could not find column 'KAN_PLAN_ENABLED' in previously parsed query!

Unfortunately I cannot insert the complete error log. Therefore I stick to the main topics. If you need further information let me know.

Thanks,

Simon

[Andy Heinzer]

Hi Simon,

I believe what has happened here is that the 7.13 upgrade did not complete successfully the entire way.   I say this because of the column name.  Kanplan was a feature added to the 7.4 version of Jira.  We have seen similar cases in support where users still were trying to utilize older database versions with Jira that were not compatible with Jira 7.4 and higher. 

In the past I have seen users that had a Microsoft SQL 2008 database encounter a very similar error when trying to upgrade.    That database version was supported in Jira 6.4 and 7.0, but not in 7.4 and higher.  Please take a look at the Jira 7.13 supported platforms documentation.  You will want to make sure you have a supported database in use before trying to do this latest upgrade. 

I'm not sure from the errors you posted exactly what database type/version you are using with Jira, but from the symptoms you have I believe you are likely seeing the same problem. 

It might be possible to migrate your Jira data in the current 7.13 state to a new supported database, and in doing so this might be able to complete the upgrade successfully and correct this error.  If this was a test upgrade on a staging system, it might be best to go back to the 7.0.11 version, and then migrate your database by following the instructions in Switching databases once you have selected a new supported database. 

Please let me know if you have any questions about these steps.

Andy

[Simon Kälberer]

Hi Andy,

we are currently using SQL 2014 Express. Although I know that it is not supported we haven't experience any problems before. We will try jira upgrade again using a supported SQL Server version. If there those problems still occur I let you knwo.

Thanks you very much for your answer,

Best regards,

Simon