The SAS 9.1 installation does not automatically request the location of the SAS installation data (SID) file in installations after the admin/personal image has been created. This is because the SID file is stored in the admin/personal image when it is created. However, you can force the installation procedure to request the SID file or to use a new one. This enables you to replace an expired SID file or to change the SID file and provide the new name to only a select number of users.

To force the SAS 9.1 installation to stop and request a SID file when installing from an admin image:

1. Go to the root location where the admin/personal installation is stored on the Windows server.
2. Select Disk1 ► SAS ► Core ► sasinst.
3. Rename the sid.txt file in the sasinst folder as sid.txt.old. Now, the setup will not find the internally stored SID and it will request that the user supply a valid SID file.
4. Rename the sid.txt.old file back to sid.txt after the installation.

To replace the original SID file and force the SAS 9.1 installation to use the new file without stopping and requesting the file name:

1. Go to the root location where the admin/personal installation is stored.
2. Select Disk1 ► SAS ► Core ► sasinst.
3. Rename the sid.txt file in the sasinst folder as sid.txt.old, or remove the file.
4. Then place the new SID file in that same directory. The new SID file needs to be named sid.txt.
5. Open the setinit.sss file with Notepad.
6. Replace the SETINIT procedure information in the file with the new PROC SETINIT information that is found in the SID. Note that this is not the entire contents of the SID file, only the PROC SETINIT code that is found in the SID file.

Operating System and Release Information