Assets not accessible via drop down menu due to unfinished upgrade tasks
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
After fresh installation (or upgrade) the Assets application is not available via the drop down menu.
When checking the atlassian-jira.log the following entries can be found
1
2
3
4
5
2023-01-16 12:52:57,838+0100 JIRA-Bootstrap ERROR [c.r.j.p.i.s.c.d.dao.sql.AbstractAOService] Unable to get database configuration with LocalHomePath, trying with HomePath instead
com.riadalabs.jira.plugins.insight.common.exception.ConnectionInsightException: ConnectionInsightException: nested exception is: null
javax.xml.bind.UnmarshalException
- with linked exception:
[org.apache.xerces.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence.] and
1
2023-01-16 13:00:30,868+0100 InsightLauncherThread WARN anonymous [c.r.j.p.i.services.launcher.InsightLauncher] Waiting for Assets upgrade tasks. Current upgrade task number is 47 Environment
JSM 5.x, 4.x
Cause
Jira is unable to run the upgrade tasks related to the Asset installation. The first error indicates an issue when trying to read the dbconfig.xml. This can be caused by invalid characters inside that file.
⚠️ NOTE: This invalid character could also be part of the password for the database.
Invalid characters are for example: \, €, @
Solution
If the invalid character is part of the password, change the password
Update / Remove the invalid characters from the dbconfig.xml
Restart Jira
Confirm that the assets upgrade tasks are completing now without error by checking the atlassian-jira.log file
Was this helpful?