Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

Unable to validate Social Office license due to failed server ID matching

Written By

Justin Mann

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 restarting one of the nodes in a Liferay 6.2 cluster set up, the following error stating the Social Office license could not be validated appeared.
  • 13:28:51,947 ERROR [localhost-startStop-1][LicenseManager:?] Social Office EE license validation failed
    java.lang.Exception: Server id matching failed. Allowed server ids: rO0ABXVyAAJbQqzzF/gGCFTgAgAAeHAAAACINB78L1ujwxe8pFuzEwUD71c2SMHeAe7dim4x3Hc/hAk7bIykqy8Pq89SDr2CYthxr2WJhLRPIjuTGaeDNu4eU3R9fmMp97Y0FrBIzdU3DVE6+LIluPzcHsHyKV2boymar2ymbGChFy1m2flcrkzN8WjsgkjuiGOniR6uxW5BlkFe40WU3L4ncg==
  • The cause appears to be the server ID does not match what is on the license. This issue causes Social Office features on that node to not work
  • Restarting Liferay after deleting tomcat_home/temp and tomcat_home/work folders does not appear to have any affect and the error still occurs.

Environment

  • Liferay Portal 6.2 EE
  • Social Office

Resolution

  • A workaround for this issue was found to resolve the issue, with the following steps:

    1. If there is a proxy, shut off the proxy that serves the affected node. This provided a guarantee that no matter what, live users will not be connected to the faulty node Liferay instance.

    2.  Start up Liferay on the affected node. This produced errors due to the Social Office license not validating. However, The Liferay logs for the affected node showed that, despite the aforementioned errors, the instance still joined the cluster with the unaffected node.

    3.  Log into the Liferay on the unaffected node as normal.

    4.  Navigate to Control Panel -> License Manager.

    5.  Enter the Order ID for Social Office provided by Liferay, select the affected node instance from the list, and activate Social Office on the instance.

    6. This will generate a new valid license for Social Office and it will work as normal on both instances
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?