Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

"Unknown product version" error

Written By

Viktória Gyömbér

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

  • I received "Unknown product version" error while I wanted to use my new hotfix.

Environment

  • Liferay DXP 7.3,dxp-2-7310,hotfix-2058-7310

Resolution

  • The reason for the Patching Tool to display the "Unknown product version" error is because this file got corrupted in your environment somehow: tomcat-9.0.37\webapps\ROOT\WEB-INF\lib\portal-impl.jar\META-INF\MANIFEST.MF. Normally this file should contain a lot of information about the environment, for example the "Liferay-Portal-Build-Number".
     
    In the provided environment however, this file only contains two lines, and because of this, the Patching Tool is not able to function properly:
    Manifest-Version: 1.0
    Created-By: 1.8.0_221 (Oracle Corporation)
    If you happen to have an older backup from the time you applied the previous hotfix (hotfix-2058-7310), you can check when this file got corrupted, otherwise it would be hard to determine how this issue happened.
     
    For a potential fix, there are propose two approaches:
    • You can recreate this environment by getting a clean Liferay 7.3 bundle, patching it with the dxp-2-7310 fix pack and hotfix-7907-7310, and deploying all your custom modules and configuration into it. I believe this is the clean solution, as we may not know if there are additional file corruptions in this environment.
    • If you are not able to recreate the environment for some reason, there is another approach to restore only this file, but I cannot guarantee that it will fix all file corruption related issues, and before proceeding please make sure to create a backup: you can get a proper MANIFEST.MF file by getting a clean Liferay 7.3 bundle, patching it with the dxp-2-7310 fix pack and hotfix-2058-7310. You can copy the MANIFEST.MF file from this environment to the affected environment (assuming that the current patch level in this environment is dxp-2-7310 + hotfix-2058-7310). If you do this, the Patching Tool will recognize the product version and you will be able to apply the new hotfix.

 

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