Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

Upgrade failed with no logs, certain modules are not upgraded

Written By

Rita Schaff

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

  • We do not have anything in our upgrade logs after we tried to upgrade from 6.2 to DXP 7.3.
  • We ran this command in gogo shell (7.3), upgrade:check , and found these modules that have not been updated yet, e.g.: 
    There are upgrade processes available for com.liferay.portal.workflow.kaleo.designer.web from 0.0.1 to 1.0.2
    There are upgrade processes available for com.liferay.calendar.service from 1.0.5 to 4.1.2
    There are upgrade processes available for com.liferay.layout.service from 0.0.1 to 1.2.1

Environment

  • DXP 7.3

Resolution

  • This happens when the database upgrade does not finish successfully. Not having anything in the logs after an upgrade is usually not a good sign.
  • If you plan on trying the upgrade again, please make sure to save those logs. 

Solution Steps

  1.  Shut down the portal and the upgrade process was run again, it should have the layout and the workflow.
  2. The calendar is not upgraded because of a NoSuchRoleException. This exception happens when there are orphan calendar-related entries in the database.
  3. Please check them with the queries below: 
    select * from calendar where companyid not in (select companyid from company);
    select * from calendarresource where companyid not in (select companyid from company);
  4. The solution is to delete those entries using the API.

Additional Information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?