Request workflow error in RSA Identity Governance and Lifecycle with Workpoint server license when editing workflows
Originally Published: 2017-02-21
Last Modified: 2023-09-25
Article Number
Applies To
RSA Product/Service Type: Enterprise Software
RSA Version/Condition: 7.0.1
Application Server: WebSphere
Issue
The server login was denied because there is a problem with the Workpoint server license
The <WAS_HOME>/profiles/<Profile_Name>/installedApps/<Node_Name>/aveksa.ear/aveksa.war/log/workpoint.log shows the following error message:
2017-01-27 13:01:53,466 [server.startup : 1] ERROR com.workpoint.server.WPServerController - LicenseException:
The Workpoint license version 3.5 does not match the current Workpoint server version 4.1. Please upgrade your license.
2017-01-27 13:01:53,467 [server.startup : 1] ERROR com.workpoint.server.WPServerController -
An error occurred while accessing the license file License.xml
com.workpoint.common.exception.LicenseException:
The Workpoint license version 3.5 does not match the current Workpoint server version 4.1. Please upgrade your license.
at com.workpoint.server.WPServerController.loadLicenseFile(Unknown Source)
at com.workpoint.server.ServerProperties.A(Unknown Source)
at com.workpoint.server.ServerProperties.<init>(Unknown Source)
at com.workpoint.server.ServerProperties$_A.<clinit>(Unknown Source)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:236)
at com.workpoint.server.ServerProperties.getInstance(Unknown Source)
at com.workpoint.server.pojo.ServerConfigPvtBean.<clinit>(Unknown Source)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:236)Cause
aveksaWFArchitect.ear\APP-INF\lib\acmConfig.jar\license.xml.
The above situation would come up if:
- You don't have the latest version of either the aveksa.ear or the aveksaWFArchitect.ear.
- The aveksa.ear is customized and an older version of the acmConfig.jar was copied.
The Workpoint license in the aveksa.ear (in the aveksa.ear\APP-INF\lib\acmConfig.jar\license.xml) shows version 3.5:
Resolution
- Download fresh RSA Identity Governance and Lifecycle 7.0.1 installation files from the RSA Identity Governance and Lifecycle 7.0.1 Download page.
- Explode the downloaded aveksa.ear and aveksaWFArchitect.ear.
- Make sure the license.xml file under aveksa.ear\APP-INF\lib\acmConfig.jar and aveksaWFArchitect.ear\APP-INF\lib\acmConfig.jar are pointing to the same version.
- Redeploy both the .ear files in WebSphere and restart the applications.
Related Articles
'ORA-01722: invalid number' or 'Non supported SQL92 token at position: XXX' errors in the aveksaServer.log when rendering … 84Number of Views Can't edit workflows on production without using AveksaAdmin 8Number of Views Validation URI JSP files do not work when uploaded to the secured JSP Pages section in RSA Identity Governance & Lifecycle 212Number of Views There was a problem processing your request error when trying to edit Date and Time Settings on RSA Authentication Manager… 201Number of Views 'There was a problem processing your request' error when attempting to delete expired tokens in RSA Authentication Manager… 462Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.1 Quick Setup Fails with "Failed to Attach Replica Instance" User Application Portal The RSA Identity Governance & Lifecycle AD Collector and AD ADC authentication source fail to establish a TLS 1.2 SSL conn…
Don't see what you're looking for?