Upgrade Fails Due to 'Content is not allowed in prolog' Error
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
Symptoms
Upgrading JIRA to 4.3.x or later fails.
The following appears in the atlassian-jira.log:
1
2
3
4
5
6
7
8
9
2011-06-27 16:52:54,688 main ERROR [atlassian.jira.upgrade.UpgradeManagerImpl] Exception thrown during upgrade: Content is not allowed in prolog.
org.xml.sax.SAXParseException: Content is not allowed in prolog.
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124)
at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build601.doUpgrade(UpgradeTask_Build601.java:164)
at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeTaskSucess(UpgradeManagerImpl.java:578)
at com.atlassian.jira.upgrade.UpgradeManagerImpl.runUpgradeTasks(UpgradeManagerImpl.java:482)
...
Cause
The osuser.xml file contain invalid characters.
Resolution
Remove the invalid character from the osuser.xml file and redo the upgrade process.
ℹ️ You can clean the file by following the information contained in this page.
Was this helpful?