In SAS 9.4M9 (25w25), a change to the naming convention of standard deployment plans introduced an issue where multiple unique standard deployment plans are displayed with shared and incomplete names in SAS Deployment Wizard. This issue might affect the ability to clearly identify and select the correct deployment plan during the installation of SAS 9.4M9 software.
When you launch SAS Deployment Wizard and reach the Specify Deployment Plan prompt, several standard deployment plans might be displayed with truncated or identical names. As a result, it is difficult to distinguish between the deployment plans.
Here is an example screenshot of this issue:
This issue mainly impacts plans that include multiple SAS solutions, such as plans with combinations of the following solutions:
- SAS® Enterprise Miner™
- SAS® Factory Miner
- SAS® Text Miner
List of Affected Plans
The following table contains a complete list of impacted standard deployment plan names:
|
Plan Name Shown in SDW |
Correct Plan Name |
|
SAS Educational Analytical Suite |
SAS Education Analytical Suite, 2 machines |
|
SAS Enterprise BI Server, Connect, Share |
SAS Enterprise BI Server, Connect, Share, 3 machines |
|
SAS Enterprise Model Management, SAS Forecast Server, SAS Text Miner, Enterprise Miner, Factory Miner |
SAS Enterprise Model Management, Forecast Server, Text Miner, Enterprise Miner, Factory Miner, 1 machine |
|
SAS Enterprise Model Management, SAS Forecast Server, SAS Text Miner, Enterprise Miner, Factory Miner |
SAS Enterprise Model Management, Forecast Server, Text Miner, Enterprise Miner, Factory Miner, 3 machines |
|
SAS Enterprise Miner, SAS Factory Miner |
SAS Enterprise Miner, Factory Miner, Text Miner, 1 machine |
|
SAS Enterprise Miner, SAS Factory Miner |
SAS Enterprise Miner, Factory Miner, Text Miner, 2 machines |
|
SAS Enterprise Miner, SAS Factory Miner |
SAS Enterprise Miner, Factory Miner, Text Miner, 3 machines |
|
SAS Enterprise Miner, SAS Factory Miner |
SAS Enterprise Miner, Factory Miner, 1 machine |
|
SAS Enterprise Miner, SAS Factory Miner |
SAS Enterprise Miner, Factory Miner, 2 machines |
|
SAS Enterprise Miner, SAS Factory Miner |
SAS Enterprise Miner, Factory Miner, 3 machines |
|
SAS Enterprise Miner, SAS Factory Miner |
SAS Enterprise Miner, Factory Miner, Forecast Server, 1 machine |
|
SAS Enterprise Miner, SAS Factory Miner |
SAS Enterprise Miner, Factory Miner, Forecast Server, 3 machines |
|
SAS Enterprise Miner, SAS Text Miner |
Enterprise Miner, Text Miner, 1 machine |
|
SAS Enterprise Miner, SAS Text Miner |
Enterprise Miner, Text Miner, 2 machines |
|
SAS Enterprise Miner, SAS Text Miner |
SAS Enterprise Miner, Text Miner, 3 machines |
|
SAS Visual Analytics and SAS Enterprise BI Server |
SAS Visual Analytics, EBI, 1 machine, wx6 |
|
SAS Visual Analytics and SAS Enterprise BI Server |
SAS Visual Analytics, EBI, 2 machines, lax and wx6 |
|
SAS Visual Analytics and SAS Enterprise BI Server |
SAS Visual Analytics, EBI, 2 machines, wx6 |
|
SAS Visual Analytics and SAS Enterprise BI Server |
SAS Visual Analytics, EBI, 3 machines, lax and wx6 |
|
SAS Visual Analytics and SAS Enterprise BI Server |
SAS Visual Analytics and Enterprise BI Server, 3 machines, wx6 |
Workaround
To locate and specify the correct deployment plan, complete the following steps:
- Download the correct standard deployment plan from https://support.sas.com/downloads/package.htm?pid=2778.
- In the SAS Deployment Wizard Specify Deployment Plan prompt, select the Specify the full path to a customized or non-customized deployment plan option.
- Navigate to the deployment plan that was downloaded.
This issue will be fixed at 25w38.
Recommendations
- Avoid silent installs using the affected plans until a resolution is provided.
- Complete the workaround above to verify that the correct plan is used during interactive installations.
- If you are unsure whether your deployment plan is affected, consult the provided list, or contact SAS Technical Support.
Important Note for Silent Installs
You should not use affected plan files for silent installations of SAS software using a response file. This is a known limitation and should be avoided until the issue is resolved in a later ship event of SAS 9.4M9.