Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

Failed upgrade process for module com.liferay.dynamic.data.mapping.service - Nested exception: Content is not allowed in prolog.

Written By

Csilla Novak

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • After a seemingly successful upgrade to Liferay DXP 7.1 the following error is showing up in the logs while starting the DXP bundle:
Failed upgrade process for module com.liferay.dynamic.data.mapping.service 
com.liferay.portal.kernel.upgrade.UpgradeException: com.liferay.portal.kernel.exception.PortalException: com.liferay.portal.kernel.xml.DocumentException: Error on line 1 of document : Content is not allowed in prolog. Nested exception: Content is not allowed in prolog.

Environment

  • Upgrade from Liferay Portal 6.2 to Liferay DXP 7.1

Resolution

  • You may get the "prolog" exception because the process tries to convert into JSON the already converted document types.

  • Doublecheck the database table DDMStructure
    • If the StorageType is still on xml (while the individual structures can already converted to json) change the column StorageType to json and the portal can start successfully. 
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?