When you try to update the license by using the Renew SAS Software
utility, the following error might appear: 

For SAS 9.1 at Step 3 - Specify Product location:

   Renew SAS Software pop-up box appears - sas91_xxxxxx.txt

   An error occurred applying the setinit file. The log file was not
   created.  Please verify that no other SAS applications are running
   and that you have sufficient permissions for the following folder:

   C:\Program Files\SAS\SAS 9.1\core\sasinst
   C:\Program Files\SAS\SAS 9.1\core\sashelp

   Ok

For SAS 9.2 at Step 2 - Specify Product location:

   Error pop-up window

   The following item is Read-Only. Verify the path is correct and
   you have write access.

   C:\Program Files\SAS\SASFoundation\9.2\core\sashelp\core.sas7cbat
   or
   C:\Program Files\SAS\SASFoundation\9.2\core\sasinst\setinit.sss
   or 
   C:\Program Files\SAS\SASFoundation\9.2\core\sasinst\sid.txt

For SAS 9.2 at Step 2 - Renew 



   

If this happens check the following items:

   1. The userID that is updating the license is a member of the local
      administrators group, with full access to the above two folders.

      To perform this do the following:
      Go to C:\Program Files\SAS\SAS 9.1\core\sasinst, highlight the
      directory, right click and select permissions.  If Read-Only is
      checked, uncheck this and select Archive if it is an option. Also,
      make sure there are no Hidden attributes set. If Read-Only is not
      checked, try to create a directory or a file in this directory.
      Perform the same steps for the sashelp directory.

      For SAS 9.2 go to: 
      C:\Program Files\SAS\SASFoundation\9.2\core\sasinst\

   2. Make sure there are no sas.exe processes running by performing
      the following:

      Press Ctrl+Alt+Del and select Task Manager, press the Processes
      tab, and click on the Image Name on the bar - this will sort the
      order.  Look for any SAS processes that might be running and end
      that Process or Processes. For example: sas.exe, objspawn.exe,
      spawner.exe, and so on.

   3. Check Services for any SAS Services that are running.  Services
      are located under:
      Start>Settings>Control  Panel>Administrative Tools>Services.
      Some of the services you might see include SAS Lev1 CS, SAS Lev1
      MS, and SAS Lev1 OB. Make sure to stop these services before you
      update your license.

   4. Make sure the icons in the Taskbar are closed, including
      anti-virus software.

   5. In some cases, log in as another user and apply the
      license corrects the problem, pointing to a permission issue.

   6. Are you running the update through a Terminal Windows?  If you
      are, perform the update at the actual server itself.

   7. If you are on a Windows x64 operating system, depending on the version 
      of SAS Software you have installed, you need to point to the correct SAS 
      Installation Data file. For example, if you have installed a x64 version
      of SAS, you need to run the Renew SAS Software tool from Start>Programs>
      SAS>SAS 9.2 License and Renewal Utilities>Renew SAS Software and point to 
      a SID file with the x64 operating system (for example: 
      SAS92_0123456_000000000_Win_X64_Wrkstn_Srv.txt). If you point to a 32-bit
      SID file you will receive an error and the setinit.log will NOT be created.

      The same is true if you have installed a 32-bit version of SAS, you need
      to run the Renew SAS Software tool from Start>Programs>SAS>
      SAS 9.2 (32) License and Renewal Utilities>Renew SAS Software and point to 
      a SID file that does not contain the x64 operating system in the name of the 
      file (For example: SAS92_0123456_000000000_Win_Wrkstn_Srv.txt).
      If you point to a x64 SID file you will receive an error and the setinit.log 
      will be NOT be created.

Rerun the SAS Software Tool.

If this does not work, SAS probably did not finish registering
during the SAS installation. Try running regbld as noted in the
following
SAS Note:

    #012774 

If a problem occurs registration, send Tech Support the RegJob.log file
for further analysis.

Operating System and Release Information