Important: This SAS KB article describes issues that occur in revisions of SAS 9.3 prior to Rev. 930_12w19. You have the option to perform the workarounds described here, or you can obtain SAS^® 9.3M1 (TS1M1) Rev. 930_12w19 or later. The issues should not occur with SAS 9.3M1 Rev. 930_12w19 and later, and therefore you would not need the workarounds described in this SAS KB article. In earlier revisions of SAS 9.3, you might encounter the issues described below.

During the final stages of the SAS 9.3 installation process, the last step, "Install Post Processing," might fail.

Here is an example of what you might experience:

 

 

After you click No above and then invoke SAS 9.3, a message such as the following occurs:

 

The resulting C:\Program Files\SASHome\InstallMisc\InstallLogs\IT_date-time.log file might contain this message or a similar message:

 > 2012-01-16 21:39:27    InstallationTask - preparing to execute [C:\Program Files\SASHome\SASFoundation\9.3\sas.exe,
-setinit, -sysin, C:\Program Files\SASHome\InstallMisc\setinit.55069c56-8d3d-4eb3-91d3-1f90d6a61995.sas,
-log, C:\Program Files\SASHome\InstallMisc\InstallLogs\setinit.log, -nodms, -noterminal, -noautoexec,
-nodate, -nostimer, -unbuflog, -icon, -nosplash, -msg, !SASROOT/core/sasmsg, -config, C:\Program

Files\SASHome\SASFoundation\9.3\nls\en\sasv9.cfg]
> 2012-01-16 21:39:55    InstallationTask - Reading output is done.
> 2012-01-16 21:39:55    InstallationTask - Waiting for process to signal done.
> 2012-01-16 21:39:55    span style="background-color: #ffff00"> InstallationTask - execution complete with exit value 111
> 2012-01-16 21:39:55    InstallationTask - core.sas7bcat (1143808 bytes) has been successfully Changed
> 2012-01-16 21:39:55    InstallationTask - Invocation of SAS returned 111
> 2012-01-16 21:39:55    Controller - An error occurred during processing:
> 2012-01-16 21:39:55    Controller - There is a problem that seems to be an issue with the installer:
                         Could not invoke public int com.sas.tools.installs.it.tasks. ApplySASLicenseTask.postInstall()

This "Install Post Processing" failure has been reported in more than one installation scenario. One scenario is that of quiet deployment installations that use provisioning software products such as SCCM, Altiris, Tivoli, and others. The other installation scenario does not involve provisioning software but rather occurs when end users or technical personnel perform installations manually.

Quiet Installation with Provisioning Software

The provisioning software scenario uses the SYSTEM account to perform installation work in installation packages. The installation failure occurs because of an issue in SAS 9.3 in which the SASUSER location becomes undetermined and the installer cannot perform the post-processing steps correctly.

Workaround

The workaround for this scenario is to implement the provisioning software installation package routine to use an account that is a local administrator account rather than use the SYSTEM account. For example, you can have an installer account that is an account on every machine in the Administrator group. Also, you can have a domain administrator account with the domain admins group included in the local administrator group. Using either of these accounts resolves the installation failure issue.

Within SCCM 2007, the task sequence supports a run-as account option. The command line can be specified there in the task sequence and the run-as user account specified.

Manual Installation

The scenario in which the end user or technical personnel encounters the same installation failure could be due to any of the following:

• The end user has designed a method to run as the SYSTEM account and perform the installation.
• The end user's Windows profile is problematic.
• The end user's account does not have the full administrative privileges that it should have.

Workaround

The workaround in this scenario would be one of the following:

• Use another account other than SYSTEM.
• Use another administrator account so that a different Windows profile is used.
• Verify that your account is truly Administrator with no restrictions such as those imposed by Windows policies.

If you have taken steps to confirm that the above workaround is not applicable, complete the following steps to correct the problem.

1. First, correct the warning:

WARNING: One or more libraries specified in the concatenated library SASHELP do not exist. These libraries were removed from the concatenation.

Navigate to the sasroot\nls\en folder and create a folder called SASCFG (if it does not already exist). For sasroot, use the installation path for SAS 9.3. The following sample paths illustrate default 32-bit and x64 paths. Use the path that is applicable to your system and your SAS installation.

Examples of Paths

C:\Program Files\SASHome\SASFoundation\9.3\nls\en
C:\Program Files\SASHome\x86\SASFoundation\9.3\nls\en

Once you have created the SASCFG folder, the resulting path should resemble one of these examples, depending on which one is applicable to your system and SAS installation:

C:\Program Files\SASHome\SASFoundation\9.3\nls\en\SASCFG
C:\Program Files\SASHome\x86\SASFoundation\9.3\nls\en\SASCFG

 

2. To correct the error about the expiration for your SAS system, run the SAS Renew utility to apply the license.

1. 1. Select Start ► Programs ► SAS ► Utilities.
      
      
   2. On Microsoft Windows 7, Windows VISTA, or Windows 2008 Server operating systems, right-click Renew SAS Software and choose Run as administrator. For other operating systems, just select Renew SAS Software.
      
      
   3. Complete the Renewal utility steps.

 

3. If you attempt to invoke SAS at this point, the following error occurs:

ERROR: The SASHELP Portable Regstry is missing or corrupted.

To correct this error, do the following:

1. 1. Rename the regstry.sas7bitm file on your system. Depending on your system type and SAS installation, navigate to one of the following paths and rename regstry.sas7bitm to regstry old.sas7bitm:
      
      C:\Program Files\SASHome\SASFoundation\9.3\core\sashelp
      C:\Program Files\SASHome\x86\SASFoundation\9.3\core\sashelp
      
      
   2. At this point, you need a valid regstry.sas7bitm file. If any of your coworkers has the same installation and system type that you do (for example, Windows 7 and SAS 9.3), you can copy their regstry.sas7bitm to your system in the same location where you just renamed your regstry.sas7bitm to regstry_old.sas7bitm.
      
      If you cannot obtain the regstry.sas7bitm file from a coworker, you can get the regstry.sas7bitm file from the SAS FTP site.
      
      Important: Be sure you use the correct file:
      
      • Use this file in this ZIP folder for a 32-bit system only: registry ZIP file.
        
        
      • When you are prompted with Do you want to open or save this file?, click Save and point to your sashelp directory. Here is an example:
        C:\Program Files\SASHome\SASFoundation\9.3\core\sashelp
        or
        C:\Program Files\SASHome\x86\SASFoundation\9.3\core\sashelp
        
        
      • Use this file in this ZIP folder for x64 systems with 64-bit SAS 9.3: registry64 ZIP file. 
        
        
   3. When you are prompted with Do you want to open or save this file?, click Save and point to your sashelp directory. Here is an example:
      
      C:\Program Files\SASHome\SASFoundation\9.3\core\sashelp
      or
      C:\Program Files\SASHome\x86\SASFoundation\9.3\core\sashelp
      
      Caution: You need to rename regstry64.sas7bitm to regstry.sas7bitm after you download the file.
      

4. Run the SASRegistryRebuildTool.

1. 1. Select the appropriate file below:
      
      Use the file 93regbld_32-bit.zip for a 32-bit system only.
      Use the file 93regbld_x64.zip for a x64 systems with 64-bit SAS 9.3.
      
      
   2. Unzip the file anywhere on your machine.
      
      
   3. Run the tool by right-clicking SASRegistryRebuildTool and selecting Run as administrator.
      
      
      .
      
      
   4. Click OK to complete the process.
      The log is placed in your temp folder as defined by your Windows TEMP environmental variable. Here is an example:
      
      On Windows XP, the default location is C:\Documents and Settings\your_userid\temp.
      On Windows 7 and Windows 2008, the default location is C:\Users\your_userid\AppData\Local\Temp\.
      
      If there is more than one user logging in to the machine, then the log is placed in a subdirectory of C:\Users\your_userid\AppData\Local\Temp\, such as C:\Users\your_userid\AppData\Local\Temp\1, C:\Users\your_userid\AppData\Local\Temp\2, or C:\Users\your_userid\AppData\Local\Temp\3.
      
      

5. At this point, you should invoke SAS 9.3.

Note: The following error might occur when you attempt to invoke SAS 9.3:

ERROR: Invalid physical name for library SASUSER.

If this error does occur, do the following:

1. 1. Navigate to one of these folders, depending on your system type:
      
      C:\Program Files\SASHome\x86\SASFoundation\9.3\nls\en
      or
      C:\Program Files\SASHome\SASFoundation\9.3\nls\en
      
      
   2. Using Notepad or another editor, open the sasv9.cfg file for editing.
      
      
   3. Locate this option in the file: -SASUSER "?CSIDL_PERSONAL\My SAS Files\9.3".
      Then, change it as follows:
      
      /* -SASUSER "?CSIDL_PERSONAL\My SAS Files\9.3" */
      -SASUSER c:\temp
      
      
   4. Select File ► Save to save the file, and then select File ► Exit to exit Notepad.
      
      
   5. Invoke SAS 9.3. If you have any errors, repeat the steps for the SASRegistryRebuildTool listed in Step 4c.
      
      

6. Run the deskdata.sas program to create the files that belong in the SASCFG directory (if it is empty) that you created in Step 1. To do this, navigate to the sasmacro directory (for example, C:\Program Files\SASHome\SASFoundation\9.3\core\sasmacro)and double-click deskdata.sas.