When you run setup.exe from the SAS^® Software Depot to install SAS^® 9.2, SAS^® 9.3, or SAS^® 9.4, the initial page appears but then closes, and the installation does not proceed. The same behavior can occur when you start the SAS Deployment Manager or the SAS Depot Check Utility. The resulting SAS 9.2 bootstrap.log file or SAS 9.3 or SAS 9.4 deploywizdate-time.log or sasdmdate-time.log or depotcheckerdate-time.log might contain the following error messages:

or

Another symptom is a lack of activity after you run setup.exe, or start the SAS Deployment Manager (sasdm.exe), or start the SAS^® Depot Check Utility (SASDepotCheck.exe). That is, no prompt or splash screen appears.

The problem is associated with memory allocation in the Java heap space. Sometimes the behavior is circumvented by restarting the machine. If the behavior persists after a restart, you might need to use one of the following applicable workarounds:

 

Workaround for the SAS^® Deployment Wizard

To work around this issue for the setup.exe file, reduce the amount of heap space that Java is allocated to use, which is the recommended best practice.

OPTION 1: Change deploywiz.ini file in the SAS Software Depot

1. Navigate to the SAS Software Depot in the Products folder.
2. In the deploywiz__99999__prt__xx__sp0__1 folder (99999 varies, depending on the SAS release), find deploywiz.ini.
   For example, the default path is path-to-your-depot\products\deploywiz_99999_prt_xx_sp1.
   Your deploywiz folder might have a different name.
3. Make a copy of the deploywiz.ini file and then open it for editing. Note: WordPad works well to edit the deploywiz.ini. In the file, locate the host sections ([win] for 32-bit and [wx6] for x64).
4. In the LAUNCHERARGS= parameter for both host sections, change the value from -Xmx1024M to -Xmx512M.
5. Save the file and then run setup.exe again to restart the installation.

Important: For either issue with the SAS Deployment Wizard, the SAS Deployment Manager, or the SAS Depot Check Utility, it might be necessary to temporarily disable your anti-virus software, including but not limited to Norton, Symantec, McAfee, Trend, Microsoft, VIPRE, Kaspersky, and AVG.   

OPTION 2: In SAS^® 9.4M4 (TS1M4) and later

If you are using SAS 9.4M4 or later, a new command-line method is available. Here is an example:

Note: The above -javaoptions parameter "-Xmx512M" is case sensitive. Also, "-Xmx256M" is a valid option, if the same error occurs with  "-Xmx512M".

Workaround for the SAS^® Deployment Manager

The issue might also occur when you try to start the SAS Deployment Manager (sasdm.exe) in order to perform Administration Tasks, such as the Renew SAS Software, Update SID file in Metadata, or Uninstall SAS Software options. The error noted above occurs in the sasdmdate-time.log. To fix this issue when you are using the SAS Deployment Manager, use a command-line option to alter the heap space that is allocated to Java. Here are some examples.

Note: The below -javaoptions parameter "-Xmx512M" is case sensitive. Also, "-Xmx256M" is a valid option, if the same error occurs with  "-Xmx512M".

SAS^® 9.4:

SAS^® 9.3:

SAS^® 9.2:

Note: The above -javaoptions parameter "-Xmx512M" is case sensitive. Also, "-Xmx256M" is a valid option, if the same error occurs with "-Xmx512M".

Important: You might need to temporarily disable your anti-virus software, including but not limited to Norton, Symantec, McAfee, Trend, Microsoft, VIPRE, Kaspersky, and AVG.

Workaround for the SAS^® Depot Check Utility

SAS^® 9.4:

Note: Replace <SAS Software Depot> above with the drive letter and folders, or UNC path to your SAS Software Depot folder.

Note 2: The above -javaoptions parameter "-Xmx512M" is case sensitive.  Also, "-Xmx256M" is a valid option, if the same error occurs with  "-Xmx512M".

Locate SAS^® Logs for Viewing

Depending on your settings for Windows File Explorer, you might have to change the viewing options for folders in order to navigate to the log files. To change the viewing options, follow these steps:

1. Open Windows File Explorer.
2. Click the View tab at the top.
3. On the right, check the boxes for File name extensions and Hidden items.
4. Navigate to the SAS 9.3 or SAS 9.4 deploywizdate-time.log, sasdmdate-time.log, or depotcheckerdate-time.log location to view the log.

To View the SAS^® 9.3 or SAS^® 9.4 deploywizdate-time.log, sasdmdate-time.log, or depotcheckerdate-time.log File

Navigate to one of the following locations, depending on your operating environment and the supported SAS release:

    C:\users\your-user-ID\appdata\local\sas\sasdeploymentwizard\

      Note: On Microsoft Windows XP:

    C:\Documents and Settings\your-user-ID\Local Settings\Application Data\SAS\SASDeploymentWizard\

To View the SAS^® 9.2 bootstrap.log File

Depending on your settings for Windows Explorer, you might have to change the viewing options for folders in order to navigate to the bootstrap.log. To change the viewing options on Windows XP or Windows VISTA, follow these steps:

1. In Windows Explorer, select Tools ► Folder options to open the Folder Options dialog box.
2. Click the View tab.
3. In the Advanced settings field, under Hidden files and folders, select the Show hidden files, folders, and drives radio button.
4. Make sure that Hide extensions for known file types and Hide protected operating system files are not selected.
5. Click OK.
6. Navigate to the SAS 9.2 bootstrap.log location.

Navigate to one of the following locations, depending on your operating environment:

    C:\users\your-user-ID\appdata\local\sas\sasdeploymentwizard\9.2

      Note: On Microsoft Windows XP:

    C:\Documents and Settings\your-user-ID\Local Settings\Application Data\SAS\SASDeploymentWizard\9.2