SUPPORT / SAMPLES & SAS NOTES
Problem Note 64017: A SAS® Web Application Server 9.45 instance that is configured for FIPS 140-2 compliance fails at startup with the error "Failed to enter FIPS mode"
 |  |  |  |  |
If you configure an instance of SAS Web Application Server 9.45 for FIPS 140-2 compliance in Microsoft Windows operating environments, that instance fails at startup. When the failure occurs, the following messages are displayed in the server.log file:
2019-02-22 10:59:16,724 INFO (WrapperSimpleAppMain)[org.apache.catalina.core.AprLifecycleListener] The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path:
[E:\SASInstall\SASConfig\Lev1\Web\WebAppServer\SASServer1_1\bin\winx86_64;E:\SASInstall\SASHome\SASWebServer\9.4\httpd-2.4.34\bin]
2019-02-22 10:59:16,724 FATAL (WrapperSimpleAppMain)[org.apache.catalina.core.AprLifecycleListener] Failed to enter FIPS mode
java.lang.Error: Failed to enter FIPS mode
at org.apache.catalina.core.AprLifecycleListener.lifecycleEvent(AprLifecycleListener.java:145)
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94)
[E:\SASInstall\SASConfig\Lev1\Web\WebAppServer\SASServer1_1\bin\winx86_64;E:\SASInstall\SASHome\SASWebServer\9.4\httpd-2.4.34\bin]
2019-02-22 10:59:16,724 FATAL (WrapperSimpleAppMain)[org.apache.catalina.core.AprLifecycleListener] Failed to enter FIPS mode
java.lang.Error: Failed to enter FIPS mode
at org.apache.catalina.core.AprLifecycleListener.lifecycleEvent(AprLifecycleListener.java:145)
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94)
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Web Application Server | Microsoft® Windows® for x64 | 9.45 | 9.4 TS1M6 | ||