After you install Hot Fix J2L001, the middle-tier configuration in SAS® Deployment Wizard or SAS® Deployment Manager fails at the Load Content / Update Content, Web Infrastructure Platform Configuration step. This issue occurs when you perform a new installation and configuration of SAS^® 9.4 M7 by using SAS Deployment Wizard or when you upgrade to SAS^® 9.4 M7 by using SAS Deployment Manager.

The container for Hot Fix J2L001 resides in the SAS Software Depot hot-fix folder. The J2L001 container consists of the following member hot fixes: 

• J2K001: This fix updates SAS^® 9.4M7 Foundation Services.
• I8P001: This fix updates the SAS^® Grid Manager plug-ins for SAS^® 9.4M7 Management Console.
• J2J001: This fix updates the SAS^® 9.4M7 Platform Object Framework.
• I9F001: This fix updates SAS^® 9.4M7 Web Infrastructure Platform.

When this problem occurs with a new installation, the following error is displayed in the webinfpltfm_loadContent_datetime.log and webinfpltfm_updateContent_datetime.log files: 

When this problem occurs with an upgrade to SAS 9.4M7, the following error appears in the webinfpltfm_updateContent_datetime.log:

If you test the the SASLogon URL( http(s)://host-name:port/SASLogon) in your browser, it returns the error HTTP 404 - Not Found.

In addition, the following error is displayed in the SASLogon9.4.log file:

To avoid this problem, you can choose whichever of the following workarounds that best suits your situation. 

Workaround 1 (Recommended)

1. Leave SAS Deployment Wizard or SAS Deployment Manager as it is.
2. Stop SASServer1_1, as follows:
   • In UNIX operating environments, submit the following command:
     SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/bin/tcruntime-ctl.sh stop
   • In Microsoft Windows operating environments, stop the server by using the Services window.
3. Locate the jboss-logging-3.3.2.Final.jar file that resides this folder: SASHOME/SASWebInfrastructurePlatform/9.4/Static/wars/sas.svcs.logon/WEB-INF/lib/
4. Manually copy jboss-logging-3.3.2.Final.jar to SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/sas_webapps/sas.svcs.logon.war/WEB-INF/lib.
5. Rename the validation-api-1.0.0.GA.jar file (which resides in SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/sas_webapps/sas.svcs.logon.war/WEB-INF/lib) to validation-api-1.0.0.GA.jar.bkup.old.
6. Rename the spring-ldap-core-1.3.1.RELEASE.jar file (which resides in SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/sas_webapps/sas.svcs.logon.war/WEB-INF/lib) to spring-ldap-core-1.3.1.RELEASE.jar.bkup.old.
7. Rename the spring-ldap-core-tiger-1.3.1.RELEASE.jar file (which resides in SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/sas_webapps/sas.svcs.logon.war/WEB-INF/lib) to spring-ldap-core-tiger-1.3.1.RELEASE.jar.bkup.old.
8. Start SASServer1_1, as follows:
   • Under UNIX, submit the following command:
     SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/bin/tcruntime-ctl.sh start
   • Under Windows, start the server from the Services window.
9. After SASServer1_1 starts, enter the SASLogon URL (http(s)://host-name:port/SASLogon) in your browser to verify that the HTTP 404 error no longer occurs and that the logon-credentials dialog box is displayed.
10. After you confirm that the SASLogon URL works, retry the failed step in SAS Deployment Wizard or SAS Deployment Manager.

Workaround 2

1. Remove the current configuration and restore the system to the state it was before you started the middle-tier installation and configuration.
2. Remove any remaining data in config directory on the middle-tier machine and clean it up. If you cannot delete the data or clean up the directory, rename it. (Note:This step applies only if a new installation and configuration of  SAS^® 9.4 M7  is being performed using SAS Deployment Wizard. Ignore this step , if this is an upgrade in place to SAS^® 9.4 M7 performed using SAS Deployment Manager)
3. Remove Hot Fix J2L001 from the SAS-software-depot-path/hotfix directory and the hot_fix_index.xml file. 
4. Re-install the middle tier by using SAS Deployment Wizard or SAS Deployment Manager. (By re-installing it this way, Hot Fix J2L001 is not installed in the SASHOME directory.)
5. Configure the middle tier by using SAS Deployment Wizard or SAS Deployment Manager

Note: You can install Hot Fix J2L001 after you successfully configure the middle tier. Remember to follow the post-installation steps that are available on the SAS Middle Tier 9.4_M7 - Hot Fix Downloads page when you install this hot fix.

A fix for this issue is planned for a future date. 

Operating System and Release Information

A fix for this issue for SAS Management Console 9.4_M7 is available at:

A fix for this issue for SAS Middle Tier 9.4_M7 is available at: