After upgrade of windows OS OC wasp fails

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

After OS Upgrade of the OC server, the OC wasp does not start and PID is recycling. Port and address are never assigned. 

 

Caused by: java.lang.RuntimeException: Keystore initialization failed. Keystore properties couldn't be loaded using file:/<Nimsoft Install path>/probes/service/wasp/webapps/cabijs/WEB-INF/lib/js-crypto-3.1.2.jar!/keystore-configuration.xml
    at com.jaspersoft.jasperserver.crypto.KeystoreManager.<init>(KeystoreManager.java:178)
    at com.jaspersoft.jasperserver.crypto.KeystoreManager.<init>(KeystoreManager.java:85)
    at com.jaspersoft.jasperserver.crypto.KeystoreManager$InstanceHolder.<clinit>(KeystoreManager.java:142)
    ... 31 more
Caused by: org.apache.commons.configuration2.ex.ConfigurationException: Could not locate: FileLocator [basePath=C:\Windows\system32\config\systemprofile, encoding=ISO-8859-1, fileName=.jrsksp, fileSystem=com.jaspersoft.jasperserver.crypto.utils.Base64SynchronizingFileSystem@73b681e2, locationStrategy=com.jaspersoft.jasperserver.crypto.utils.JrsBasePathLocationStrategy@35078234, sourceURL=null, urlConnectionOptions=null]
    at org.apache.commons.configuration2.io.FileLocatorUtils.locateOrThrow(FileLocatorUtils.java:484)

Environment

DX UIM 23.4.*

Cause

The OC might not be able to start because CABI is installed on the same server, and the cabijs webapp is failing on startup, and it is therefore preventing the OC to start too. 

The CABI issue is described in this article: Unable to access CABI after Windows OS upgrade to CABI server

Resolution

To resolve this issue immediately (Have OC running immediately): 

1. in IM, Open the OC WASP (which would be the same as the CABI WASP in this scenario) -> Raw configure

2. Edit the following key from true to false. 

wasp > webapps > cabijs >   load_on_startup = false

eg.:
    <cabijs>
        load_on_startup = false
    </cabijs>

3. Start the WASP. 

 

To resolve the CABI issue see: 

Unable to access CABI after Windows OS upgrade to CABI server

NOTES:

• It is recomendable to move CABI on a other robot different from OC as CABI and OC cannot run on the same server starting DX UIM 23.4.5 (CU5). 
• CABI is announced to be EOS in October 2025: Deprecation Announcement for support of CABI JasperReports
• DX UIM CABI Replacement Plans after End of Support