Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Upgrade Fails: Error after upgrading using the Database Upgrade Tool (MS SQL Server)

Written By

Emma Carr-Gardner

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 running `db_upgrade_client.bat` my upgrade failed with no explanation in the logs.
  • Upgrade failed, when it was attempted again it was successful but Liferay won't start
  • After upgrading, Liferay has an error in the logs: 
    • ERROR [SCR Component Actor][ROOT:47] bundle com.liferay.portal.properties.swapper:5.0.25 (160)[com.liferay.portal.properties.swapper.internal.DefaultCompanyNameSwapper(11645)] : The activate method has thrown an exception
      java.lang.IllegalStateException: Unable to get default company ID

Environment

  • Liferay DXP Quarterly Release 2023.Q4

Resolution

  • There is a known issue with the Database Upgrade Tool generating incorrect `jdbc.default.url` for SQL Server when using prompts. 

    When upgrading with the Database Upgrade Tool, the script asks a number of questions like: home location, server details, etc. Then it created entries in portal-upgrade.properties or portal-upgrade-database.properties

    • Expected Result : `jdbc.default.url=jdbc:sqlserver://localhost;databaseName=lportal`
    • Actual Result: `jdbc.default.url=jdbc:sqlserver://localhost;databaseType=lportal`

  • Inspect the value for the property: `jdbc.default.url` in the generated: portal-upgrade-database.properties and update to `databaseName` to resolve this behavior.

Additional Information

 

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