Clarity PPM Jaspersoft error - Keystore initialization failed. Keystore properties couldn't be loaded

Products

• Clarity PPM On Premise

Issue/Introduction

You are trying to access Advanced reporting, but receive a 404 error.

In the catalina log file there are a few errors.

• 19-Sep-2022 10:52:40.152 SEVERE [main] org.apache.catalina.startup.HostConfig.deployDirectory Error deploying web application directory [/clarity/Tomcat/apache-tomcat-9.0.37/webapps/reportservice]
   java.lang.IllegalStateException: Error starting child
• org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/reportservice]]
• java.lang.RuntimeException: Keystore initialization failed. Keystore properties couldn't be loaded using file:/clarity/Tomcat/apache-tomcat-9.0.37/webapps/reportservice/WEB-INF/lib/js-crypto-3.0.0.jar!/keystore-configuration.xml

Also, Clarity may also be affected and not start as a service (Error Starting Child)

Environment

Release : Any Supported Release with Jaspersoft

Cause

Jaspersoft is unable to find or use the Jaspersoft keystore files (placed typically in C:\Users\<jasperuser>). Possible causes: 

• Jasper keystore files missing from user's home directory.
• Jasper Keystore file's are different to Clarity Keystore files which are generated and these files are generated during installation of Jasper Server.
• Jaspersoft was installed with a different user account and trying to start the service using a different account.

Another possibility is that the Windows Service account doesn't have the ability to access the Keystore in the home directory, due to a server restriction. Ensure that the Windows Service account has rights to get to the home directory specified. As an alternative, the Windows service can be configured to start with a particular user who has rights, but you need to ensure the account's password will not expire, otherwise it will fail to work after a password change.

Resolution

1. Identify the user which was used during installation and login as that user
2. Check the user home directory to make sure the keystore files are there
3. Ensure OS permissions are set correctly - grant the Full rights explicitly to the user running the service
4. If there are 2 servers in cluster then all keystores should be the same so copy them from the other server
5. Start the service from this same user profile.