A blank page or an error appears in SAS® Deployment Manager when you attempt to rebuild SAS® web applications in SAS® 9.2, 9.3, and 9.4


When you attempt to rebuild SAS web applications using the SAS Deployment Manager, the page on which you select the SAS web applications or on subsequent pages might be blank, as shown in the following examples.

Example 1: A blank Select Web Applications to Rebuild page in the SAS 9.2 Deployment Manager that contains the following message:

The specified configuration directory and level do not contain any Web Applications to rebuild.

Screen box showing error "The specified configuration directory and level do not contain any Web Applications to rebuild."

Example 2: The Select Web Applications to Rebuild page in the SAS 9.3 Deployment Manager, along with two blank pages that follow the page:

Deployment manager box showing product configuration and telling user to select the ones to rebuild

Deployment manager box showing blank page example 1

Deployment manager box showing blank page example 2

In SAS 9.4, you might also encounter the following error when you attempt to rebuild the SAS web applications:

The location of the configuration script for SAS-web-application- name could not be determined.

An example of the full message is shown below:

"The location of the configuration script for SAS Visual Analytics Explorer could not be determined. You should confirm that this configuration error will not lead to errors with other products before deciding to ignore the error by choosing "Yes" or "Yes to All" when asked if you want to continue with the remaining configuration steps. If you are uncertain, contact SAS Technical Support for guidance before continuing with this deployment. Would you like to continue with the remaining configuration steps?"

This problem occurs when the system is created using the SAS® Migration Utility. This problem can also occur when you install products from a depot subset and then try to run the SAS Deployment Manager to perform tasks on an existing configuration directory. The result is that there are multiple orders associated with the configuration and the wrong order number is found.

To determine the cause of the this issue, open a track with SAS Technical Support and provide the following items: