RSA Authentication Manager Prime services fail to start after Java update on a Windows server: Error Failed creating java

[#1]

Article Number

000030993

Applies To

RSA Product Set: SecurID
RSA Product/Service Type: Authentication Manager, Authentication Manager Prime
RSA Version/Condition: 8.1, 1.x
Platform: Windows 2008 or WIndows 2012
Platform (Other): Tomcat

Issue

Java was updated on the Windows 2008 or 2012 Server where the AMIS framework, SSP or HDAP is installed.  Now Tomcat services fail to start.

The tomcat commons-daemon.date.log for each service report the following error:

[2015-08-17 10:34:08] [info]  [ 1812] Commons Daemon procrun (1.0.15.0 64-bit) started
[2015-08-17 10:34:08] [info]  [ 1812] Running 'Tomcat7-AMIS' Service...
[2015-08-17 10:34:08] [info]  [ 2736] Starting service...
[2015-08-17 10:34:08] [error] [ 2736] Failed creating java C:\Program Files\Java\jre1.8.0_45\bin\server\jvm.dll
[2015-08-17 10:34:08] [error] [ 2736] The system cannot find the path specified.
[2015-08-17 10:34:08] [error] [ 2736] ServiceStart returned 1

Logs for Tomcat are typically going to be in C:\RSA\Tomcat7-AMIS\Logs. Note for each AMIS item there is a different Tomcat7 folder instance. In this case, refer to the commons-daemon.<date>.log which will contain the current date in place of the word date. 
 

Image description

Cause

The error is due to the version number change which causes the file to not be found, just as the log noted. When Java is updated on the Windows side, the update deletes the old Java folder contents. All that is left is the folder with a few empty sub folders. In this case the updated version is now jre1.8.0_51 as compared to jre1.8.0_45, as shown:

Image description

When Tomcat starts it looks for the Java Virtual Machine path defined in the Tomcat configuration and can no longer find the jvm.dll file it needs to start. The path started out as C:\Program Files\Java\jre1.8.0_45\bin\server\jvm.dll which causes the error during startup. 
 

Image description

Resolution

To resolve the issue simply change the path so it points to the updated Java directory and services should start without issues. 

1. Right click the first Tomcat icon for the AMIS framework service, then click Configure...

Image description

2. Check the Java path details by going under C:\Program Files\Java\ and making note of the newer folder with the higher end number. In this case it's 51, but in the future it may be 52 or above. 

Image description

3. Set the path under the Tomcat Config > Java.
4. Click Apply or OK.

Image description

5. Repeat steps 1 - 4 for any other AMIS Prime Tomcat services you have on the server such as for the Self-Service Portal or Help Desk Admin Portal currently.
6. Right click and stop/start each Tomcat instance.  All services should now be running as expected.