• Print |
• E-mail  |
• Bookmark

If SAS Release 8.2 is completely expired, beyond the warning and grace
periods, you will receive a message similar to the following when you
start SAS. The message you would receive in this instance would contain
the dates relevant for your installation.

   ERROR: The current date of Monday, October 8, 2007 is past the final
       expiration date for your SAS system, which is Sunday, May 29,
2005.
   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 SAS Release 8.2 is expired, follow these instructions to apply the
new setinit license:

1. Save the new setinit code in a file named setinit.sss. To accomplish
   this, do the following:
   a. Open Notepad.
   b. Click File > Open and open the existing setinit.sss file.
      The default location is
      c:\program files\sas institute\sas\v8\core\sasinst directory.
   c. Copy and paste the new setinit code, replacing the existing
      code.
   d. Click File > Save As and click to the c:\program files\sas
      institute\sas\v8\core\sasinst directory.
   e. Type in the following filename (including the quotes):

      "setinit.sss"

   f. Click Save and Exit Notepad.

2. Process the setinit file:
   a. In Windows Explorer or My Computer, right-click on the
      setinit.sss file and choose Apply Authorization code to SAS V8.
   b. Start SAS.

If you right-click setinit.sss and Apply Authorization code to SAS
V8 is not on the menu, do the following:

   a. Click Start > Run.
   b. Paste in the following command and run it (assuming that you have
      installed SAS in the default directory):

      "c:\program files\sas institute\sas\v8\sas.exe" -sysin "c:\program
      files\sas institute\sas\v8\core\sasinst\setinit.sss" -setinit

      Important: Make sure the preceding command is typed in as one
      line and is not broken into two or more lines.


   c. Start SAS.

3. If SAS does not start, check the setinit.sss.log file for errors.

Operating System and Release Information