Not responding at 85%

If the SAS install stops responding at 85% completion, make sure that the Filetypes dialog box is not waiting for a response from you. It might be hidden behind another window, especially if you have or had another program running during the installation. You must make a selection in this dialog box for the installation to continue. Press Alt+Esc or Alt+Tab to make sure there is not a dialog box waiting for a response. In some cases you might need to move the windows to find hidden dialog box waiting to be answered.

Not responding at 90%

At 90% in most cases this has been caused by the system being infected with spyware or adware. See SAS Note 12469, "Reboot Pending messages might appear when installing SAS 9.1 due to spyware or adware" for more information.

Not responding at 96% or greater

At 96%-98% completion of installation, the SAS registry and the SAS Installation Data (SID) are being built. A common cause of the SAS Installation at these percentages is not logging in as the administrator of the machine. See SAS Note 5055 , "Administrator of the machine versus being part of the administrator group" for an explanation of being the administrator of the machine versus being part of the administrator group.

Note: Before you select Cancel during the installation, go to the C:\Documents and Settings\<USER_ID>\Local Settings directory and copy the sassetup.log file to another directory. You can perform a search for a copy of the sassetup.log file located in the following directory: C:\Documents and Settings\<USER_ID>\Local Settings. For example on WinXP: C:\Documents and Settings\<USER_ID>\Local Settings\Temp\ {68624FB8-2512-46B5-9664-64366DCCB3EB}.

To correct the installation

1. Note the percentage of completion before you cancel the SAS Installation. This is very important for troubleshooting purposes.
2. Copy the sassetup.log file from C:\Documents and Settings\<USER_ID>\Local Settings
3. Click on Cancel to end the installation.
4. Reboot your system.
5. Log in as the administrator of the machine.
6. Close all applications, including anti-virus software.
7. Reinstall SAS 9.1 or 9.1.2.

   Note: It is not always be necessary to uninstall first. You can try to reinstall over the current SAS 9.1 or 9.1.2 image.

Solution not working?

If this solution does not work and this error message appears

go to SAS Note 12774,"Error: The SASHELP Portable Registry is missing or corrupted" for more information and a solution on using the SAS Registry Rebuild utility.

Still encountering a problem?

If you are still encountering a problem, open a track with Technical Support. Send as much of the following information as possible to troubleshoot this issue quickly:

1. The sassetup.log, that is, the one from C:\Documents and Settings\<USER_ID>\Local Settings that you saved to a different location.
2. The percentage of completion on the second installation.
3. The new sassetup.log file from the second attempt at installing. Rename this file to sassetup2.log.
4. What types of video card and driver are on your machine?
5. What is the anti-virus software (and version) that is on your machine?
6. Which type of installation did you perform?
   1. Personal install from CDs
   2. Admin/Personal install from a network image
   3. Admin/Client install from a network image
   4. Quiet install
7. If you are installing from CDs, are they the original or copied CDs?
8. Which operating system and service pack are you running with? To find out, click Start ► Run, type winver, and select OK.
9. Were you logged in as the administrator of the machine?
10. What language or languages were you installing?
11. Is this happening on other machines or just yours?
12. Is SAS 8.2 installed on your system and/or other releases of SAS? If yes, which type of installs were they?
    1. Personal install from CDs
    2. Admin/Personal install from a network image
    3. Admin/Client install from a network image
    4. Quiet install
13. What messages or errors do you receive when you try to start SAS?
14. When you installed SAS, did you have all SAS processes closed? To check this, open the Task Manager and look for any SAS servers that might be running (for example: SAS Lev1 MS, SAS Job Spawner, and so on).
15. Check the Event Viewer for any errors indicated with a red circle). The Event Viewer can be found by clicking on Start ► Settings ► Administrative Tools ► Event Viewer.
16. If any messages appear during your installation or when you start SAS, capture these (Alt+Prnt+Scrn) and then paste them into a Word file (Ctrl+V) to help in troubleshooting.
17. Click on Start ► Run and type winmsd. Then click on File ► Export and export the contents to a file called machine.txt.

Some additional tips to try:

1. Run a thorough defragmentation program.
2. Run a thorough scandisk program.
3. Scan your entire system for viruses.
4. Run an anti-spyware and -adware program on your system.
5. Boot into safe mode and install SAS:
   1. When the machine is booting before the Windows logo appears, press F8. If it boots normally, try rebooting the machine and pressing F8 earlier.
   2. Or if you have permissions to, click Start>Run and type msconfig which starts the System Configuration Utility. On the General Tab select "Diagnostic Startup - load basic devices and services only" and click OK.

Operating System and Release Information

Product Family	Product	System	SAS Release
			Reported	Fixed*
SAS System	Base SAS	Microsoft Windows 2000 Server	9.1 TS1M0
		Microsoft Windows Server 2003 Datacenter Edition	9.1 TS1M0
		Microsoft Windows Server 2003 Enterprise Edition	9.1 TS1M0
		Microsoft Windows Server 2003 Standard Edition	9.1 TS1M0
		Microsoft Windows NT Workstation	9.1 TS1M0
		Microsoft Windows XP Professional	9.1 TS1M0
		Microsoft Windows 2000 Advanced Server	9.1 TS1M0
		Microsoft Windows 2000 Datacenter Server	9.1 TS1M0
		Microsoft Windows 2000 Professional	9.1 TS1M0

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

---

When installing SAS® 9.1, 9.1.2 and 9.1.3 the installation might stop responding anywhere between 85% and 99% of completion.

Type:	Usage Note
Priority:
Topic:	System Administration ==> Installation

Date Modified:	2008-09-29 14:53:07
Date Created:	2004-07-06 08:45:04