If you try to apply a setinit.sss file to SAS 8.2, the installer might not start.

This might be seen for one of the following reasons:

1. sas.exe has not been added to DEP.
2. The setinit.sss file is corrupted.
3. The installation is corrupted.
4. The SAS registry might be corrupt.

To fix these issues, try the following one at a time:

1. if sas.exe has not been added to DEP:

   Adding sas.exe to the list of excluded (excepted) processes prevents DEP from blocking the code generation done by SAS processes. To add a process to the list in Microsoft Windows:

   1. Right-click My Computer and select Properties.
   2. Select the Advanced tab.
   3. Under Performance, click Settings
   4. Select the Data Execution Prevention tab
   5. Click Add. Locate the sas.exe file to include it in the list. The default location for SAS 8.2 is C:\Program Files\SAS Institute\SAS\V8.

      For detailed information on DEP, see the following Microsoft Knowledge Base articles:

      A detailed description of the Data Execution Prevention (DEP) feature in Windows XP Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows Server 2003

      The Data Execution Prevention tab in System Properties does not show hardware-based DEP support information in x64 or Itanium-based versions of Windows Server 2003 or Windows XP

   
   
2. if setinit.sss file is corrupted:

   If this happens, contact your SAS Installation Site representative to see if they have another setinit.sss file for you to try. If they do not, the SAS Installation Site representative can contact Contracts to request a new copy.

3. if installation is corrupted:

   Reinstall SAS 8.2. If you have a network location that you are installing from, make sure you install using a current setinit.sss file.

   If you are installing from media, make sure the media that you are installing from has a current setinit.sss file on the SAS Setup CD. To check this, insert the SAS Setup CD, go to <CD-ROM drive letter>:\sas\core\sasinst. Open the setinit.sss file and verify the expire= date. If this is not current, check with your SAS Installation Site representative to see if they have a SAS Setup CD with a current setinit.sss file.

4. if the registry is corrupted:

   Fix the SAS Registry. SAS Note 9998: "After installing SAS 8.2 you might receive the error: The current date of xxxxx is past the final expiration date for your SAS System, which is Sunday, xxxx, 2003" provides instructions for continuing the installation.

In some cases, when you go to start SAS 8.2, you might get the following message:

Error: The current date of Thursday, July 11, 2002, is past the final
expiration date for your SAS system, which is Sunday, August 1, 1993.
Please contact your SAS Software Representative to obtain your updated
SETINIT information.
ERROR: Initialization of SETINIT information from SASHELP failed.
FATAL: Unable to initialize the options subsystem
{SASXKINI}: PHASE 3 KERNEL INITIALIZATION FAILED.
UNABLE TO INITIALIZE THE SAS KERNEL

If this happens, highlight the current setinit.sss file in Windows Explorer, right-click and run Apply Authorization Code.

Operating System and Release Information