000031931 - Admin GUI not available after server restart in RSA Via L&G

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000031931
Applies ToRSA Product Set: RSA Via Lifecycle and Governance
RSA Product/Service Type: Aveksa UI
RSA Version/Condition: 6.9.1 P07
Platform: WebSphere

After restarting the Websphere server, the Aveksa UI is no longer accessible.   Attempting to access the page displays a 404 error.
Error messages similar to the example below are found in the Websphere SystemOut.log error log.

11/20/15 17:47:59:380 CET] 0000005b SystemOut     O 2015-11-20 17:47:59,378 [server.startup : 0] ERROR com.wo
rkpoint.server.pojo.ServerConfigPvtBean  - Unable to use the user specified Security Module class
        at com.aveksa.server.authorization.WpAveksaEncryptionModule.initSecurityManager(WpAveksaEncryptionModu

[11/20/15 17:48:03:883 CET] 00000070 SystemOut     O 2015-11-20 17:48:03,883 [Timer-8] ERROR com.workpoint.server.WpLoginHandler  - Login failed for user -1
        at com.aveksa.server.workflow.authentication.WpAveksaLoginModule.authenticate(WpAveksaLoginModule.java:259)
        at com.aveksa.server.workflow.authentication.WpAveksaLoginModule.login(WpAveksaLoginModule.java:113)

ResolutionThis error suggests permission issues with the Aveksa.ear file that were caused due to an improper restart or any other changes done by the user during server restart.
Therefore it is advisable to redeploy the aveks.ear file in Websphere followed by a WAS restart.