The SAS Installation Qualification Tool (W83001 Update) might fail to install. In the IT_DDMMMYYYY.log, you might see the following error:

2016-10-12 16:06:13    InstallationTask - notifyProgressStart notification broadcast.
	description:  Executing C:\windows\system32\cmd.exe from working directory C:\Program Files\SASHome\InstallMisc\utilities\installqual\9.4
2016-10-12 16:06:14    Controller - An error occurred during processing:  
2016-10-12 16:06:14    Controller - There is a problem that seems to be related to the system running the install:  C:\windows\system32\cmd.exe with args /C ""C:\Program Files\SASHome\InstallMisc\utilities\installqual\9.4\updateconfigpicklists.bat" "C:\Program Files\SASHome"" exited with non-zero return code:  1
2016-10-12 16:06:14    Controller - com.sas.tools.installs.it.InstallException
	at com.sas.tools.installs.it.tasks.RunApplicationTask.executeProcess(RunApplicationTask.java:254)
	at com.sas.tools.installs.it.tasks.RunApplicationTask.launchApplication(RunApplicationTask.java:144)
	at com.sas.tools.installs.it.tasks.RunApplicationTask.execute(RunApplicationTask.java:107)
	at com.sas.tools.installs.it.Controller.executeScript(Controller.java:2922)
	at com.sas.tools.installs.it.ExecutionThread.run(ExecutionThread.java:80)

If you see this error message, perform the following workaround.

Workaround

1. Using a text editor, open the sassw.config file that is located in sashome.
2. Check the path specified for PRIVATEJREHOME. The path for PRIVATEJREHOME should point to the full path of java.exe and should have the same path as JREHOME. If it is incomplete, it appears as PRIVATEJREHOME=\jre\bin\java.exe. Correct the path by putting in the full path. You can get the full path by looking at JREHOME.
   Example: PRIVATEJREHOME=C:\Program Files\SASHome\SASPrivateJavaRuntimeEnvironment\9.4\jre\bin\java.exe
3. Save the file.
4. Now, in the SAS Deployment Wizard, click Retry.

Note: In the instructions above, if your sashome directory is not C:\Program Files\SASHome, substitute the appropriate value for your installation.

If this workaround does not fix the issue, do the following and provide the resulting information to SAS Technical Support.

Use the SAS^® Installation Log Assistant to gather SAS installation logs and send the logs to the track. For more information, see SAS Note 52654: "Using the SAS^® Installation Log Assistant to gather SAS^® installation logs."

If you have an existing track with SAS Technical Support, you can use the SAS Installation Log Assistant to FTP the logs. If you do not have an existing track, email them to support@sas.com along with the following items.

• All copies of the updateconfigpicklists_DDMMMYYYY.log file that is located at sashome\InstallMisc\utilities\installqual\9.4.
  If these files do not exist, skip this step.
• The cd.id file that is located in sashomeSASDeploymentManager\9.4.
• The DeploymentRegistry.txt file that is located at sashome\deploymntreg. To create DeploymentRegistry.txt, double-click the sas.tools.viewregistry.jar file. This action creates a copy of DeploymentRegistry.txt in the sashome\deploymntreg directory.
  If the DeploymentRegistry.txt file is not created, send the registry.xml file instead.
• The sassw.config file that is located in sashome.

For information about how to contact SAS Technical Support, see Contact SAS Technical Support.

Operating System and Release Information

A fix for this issue for SAS Web Application Server 9.42 is available at:

A fix for this issue for SAS Environment Manager 2.3 is available at:

A fix for this issue for SAS Web Application Server 9.41 is available at:

A fix for this issue for SAS Environment Manager 2.1_M1 is available at:

A fix for this issue for SAS Web Server 9.4_M1 is available at:

A fix for this issue for SAS Environment Manager 2.1 is available at:

A fix for this issue for SAS Web Application Server 9.4 is available at:

A fix for this issue for SAS Web Server 9.4 is available at: