After installing a hot fix for SAS Infrastructure for Risk Management, the SAS Infrastructure for Risk Management (SASIRM) application no longer functions in a browser. The following error occurs in the browser immediately after logging on to the SAS Infrastructure for Risk Management application:
Server Error
An error occurred on the server. Please contact your system
administrator.
In the SASIRMServer.log file, the following two errors occur 794,726 times:
IRM [Catalina-utility-2] 14May24 15:13:45,574 ERROR com.sas.solutions.risk.irm.server.taskexec.SASHelper - ERROR: Could not find method FileUtils_mergedFileInfo at line 72 column 3.
IRM [Catalina-utility-2] 14May24 15:13:45,574 ERROR com.sas.solutions.risk.irm.server.taskexec.SASHelper - ERROR: An error has occurred during instance method OM_CALLSTRINGMETHOD(3278) of "DATASTEP.JAVAOBJ".
In the same SASIRMServer.log file, the following error occurs at the end of the previous errors 794,726 times:
IRM [Catalina-utility-2] 14May24 15:13:53,877 ERROR com.sas.solutions.risk.irm.server.io.WorkspaceServerWorker - An error(s) occurred executing file action "loadAllFederatedFiles" it had 794,726 errors in the execution log.
com.sas.solutions.risk.irm.server.io.remote.RemoteIOException: An error(s) occurred executing file action "loadAllFederatedFiles" it had 794,726 errors in the execution log.
at com.sas.solutions.risk.irm.server.io.WorkspaceServerWorker.executeSASCode(WorkspaceServerWorker.java:600)
at com.sas.solutions.risk.irm.server.io.FileUtils.loadAllFederatedFiles(FileUtils.java:1721)
at com.sas.solutions.risk.irm.server.utils.FederatedContentHelper.init(FederatedContentHelper.java:1553)
at com.sas.solutions.risk.irm.server.engine.ComputationServerEngine.start(ComputationServerEngine.java:218)
at com.sas.solutions.risk.irm.server.ComputationServer.start(ComputationServer.java:65)
at com.sas.solutions.risk.irm.server.ComputationServer.init(ComputationServer.java:92)
at javax.servlet.GenericServlet.init(GenericServlet.java:158)
at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1164)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1117)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1010)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4957)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5264)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:726)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:698)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:696)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:690)
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1889)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:750)
Cause of the Errors
When you install a hot fix, the hot fix post-installation steps instruct the user to run the SAS Infrastructure for Risk Management post-installation task automation tool. If you miss this step, the code of the SASIRM application will not match the code of the platform federated area, resulting in the errors described above.
Note: The SAS Infrastructure for Risk Management post-installation task automation tool is responsible for updating the code in the platform federated area.
For more information, see the SAS® Infrastructure for Risk Management Run the Hot Fix Post-installation Tool.
Troubleshooting
Complete the following steps to troubleshoot this issue.
1. On the mid-tier machine, review the sas.insuranceriskmanagementserver.war picklist file at the following location:
<SASConfig>/<Lev#>/Web/WebAppServer/SASServer8_1/sas_webapps/sas.insuranceriskmanagementserver.war/WEB-INF/picklist
2. Search for sas.solutions.risk.irm.server to identify the version number of the sas.solutions.risk.irm.server JAR file. Here is an example:
name=sas.solutions.risk.irm.server
version=306005.13.0.20240229114600_f0irm36p
Note: The sas.solutions.risk.irm.server JAR file configured in the picklist file should exist with the same name and size at the following locations:
On the mid-tier: <SASHome>/SASVersionedJarRepository/eclipse/plugins/sas.solutions.risk.irm.server_<version>.jar
On the compute-tier: <SASConfig>/<Lev#>/AppData/SASIRM/fa.0.<IRM_version>/source/java/lib/sas.solutions.risk.irm.server_<version>.jar
If the correct sas.solutions.risk.irm.server JAR file exists on the mid-tier machine, but not on the compute-tier machine, this discrepancy suggests that the post-installation task automation tool did not run correctly.
Workaround
To circumvent this issue, run the SAS Infrastructure for Risk Management post-installation task automation tool as documented in the hot fix installation instructions, and complete the remainder of the post-installation steps. Correct any errors that occur when running the post-installation task automation tool.