When installing 32-bit SAS 9.3 TS1M2 revision 930_13w14 software for the 64-bit Microsoft Windows operating environment, an error occurs during the "Install Post Processing" step.

An error message similar to the following is written to the C:\Program Files\SASHome\InstallMisc\InstallLogs\IT_date-time.log file.

ApplySASLicenseTask - Failed to run SAS to apply the SAS License file. 
Cannot run program "C:\Program Files\SASHome\SASFoundation\9.3\sas.exe":
CreateProcess error=2, The system cannot find the file specified

WARNING: One or more libraries specified in the concatenated library SASHELP
WARNING: do not exist. These libraries were removed from the concatenation.
ERROR: The current date of Thursday, April 23,2013, is past the final
ERROR: expriation date for your SAS system, which is Monday, April 3, 2000.
.
.
.
ERROR: Initialization of setinit information from SASHELP failed.
NOTE:  Unable to initialize the options subsystem.
ERROR: (SASXKINI): PHASE 3 KERNEL INITIALIZATION FAILED.
ERROR: Unable to initialize the SAS kernel.

Perform the workaround described below to manually complete the post processing steps for your SAS 9.3 installation.

Workaround

1. First, correct the issue described in 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 a 32-bit installation of SAS 9.3 software on a 64-bit operating system, the default path for sasroot is

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

After you have created the SASCFG folder, the resulting path should resemble the following:

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. 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 Registry is missing or corrupted.

To correct this error, do the following:
1. Rename the regstry.sas7bitm file on your system. Navigate to the path shown below and rename regstry.sas7bitm to regstry_old.sas7bitm:

   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 co-workers has the same installation and system type that you do (for example: 64-bit 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 co-worker, you can get the regstry.sas7bitm file from the SAS FTP site.

• Use this file for x64 systems with 32-bit SAS 9.3: ftp://ftp.sas.com/techsup/download/pc/regstry.sas7bitm
3. When you are prompted with Do you want to open or save this file?, click Save and point to your sashelp directory. For example:
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. Download the ftp://ftp.sas.com/techsup/download/pc/93regbld_32-bit.zip file.
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. For 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. Navigate to:


C:\Program Files\SASHome\x86\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"

And change it to this:

/* -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\x86\SASFoundation\9.3\core\sasmacro) and double-click deskdata.sas.

Operating System and Release Information