When you configure SAS® Web Application Servers for FIPS mode, the update in place to SAS 9.4M8 fails during SAS® Web Application Server Configuration. The following error occurs in the SAS® Deployment Manager error window:
Timeout for Application Server startup has reached before port opened.
The following is a screenshot of the error:
When this issue occurs, the server.log file for SAS Web Application Server (which is located in the SAS-configuration-directory/Levn/Web/WebAppServer/SASServern_m/logs directory) contains the following error:
YYYY-MM-DD hh:mm:ss,ms FATAL (main) [org.apache.catalina.core.AprLifecycleListener] Failed to enter FIPS mode
java.lang.Error: Failed to enter FIPS mode
java.lang.Error: Failed to enter FIPS mode
To work around this issue, complete the following steps:
- Leave SAS Deployment Manager running.
- From a shell command line, stop all SAS Web Application Servers SASServern_m with the following command:
SAS-configuration-directory/Levn/Web/WebAppServer/SASServern_m/bin/tcruntime-ctl.sh stop
- Once you stopped all the SAS Web Application Servers, start them sequentially one after the other beginning with SASServer1_1 up to SASServerN_M using by using the following command:
SAS-configuration-directory/Levn/Web/WebAppServer/SASServern_m/bin/tcruntime-ctl.sh start
Note: Wait for all the SAS Web Application Servers to start. Monitor their server.log to determine whether the server startup is successful and whether the server enters FIPS mode.
- Once the SAS Web Application Servers start successfully, click Yes (not Retry) in the SAS Deployment Manager error window to continue.