Your SAS 9.2 (TS2M2) installation might run without an error. However, the installation process might become unresponsive during the configuration steps of the installation at Stage 3: Configure Metadata ► SAS Metadata Server Configuration.

If this problem occurs, here are some things to check:

1. Verify that the JRE is installed and working properly:
   1. Go to an MS-DOS command prompt. Click Start ► Run and type cmd.
   2. At the MS-DOS command prompt, type cd\.
   3. Change directory to the required JRE, for example:

      cd "Program Files (x86)\Java\jre1.5.0_12\bin"

      cd "Program Files\Java\jre1.5.0_15\bin"

   4. At the MS-DOS command prompt, type java -version

      You should see something similar to this:
      

         C:\Program Files (x86)\Java\jre1.5.0_12\bin>java -version
         java version "1.5.0_12"
         Java(TM) 2 Runtime Environment, Standard Edition 
             (build 1.5.0_12-b04)
         Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode)

   5. If you do not get these results, select Control Panel ► Add/Remove Programs and uninstall the JRE.
   6. Reboot the PC and then reinstall the JRE.
   
   
2. Make sure that the anti-virus software that is installed on your machine is disabled. This means checking the services, the processes, and the icons in the lower right corner. To do this, perform the following steps:
   1. Click Start ► Run and type services.msc to invoke the Services window. Scroll down to the anti-virus software that is installed on your machine and stop all the services that are running. It might also be good to stop other services such as following:
      • automatic updates
      • the Windows Firewall or the firewall that you are using
      • the Print Spooler
   2. In some instances, just stopping the service is not enough. You might have to completely uninstall the anti-virus software on order to complete the installation.
   
   
3. If this is a single-machine installation, check the hosts file. You can find this file for Windows in either of these directories:
   C:\WINNT\system32 \drivers\etc\

   C:\Windows\system32\drivers\etc\

   To update the hosts file, edit it in Notepad and check the following:

   1. Make sure there is a localhost entry:

         127.0.0.1     localhost

      Make sure you can contact localhost.

   2. Add the fully qualified host name and the short name to the default entry. For example:
      

         127.0.0.1     localhost     machine.domain.xxx  computername 
      
         127.0.0.1     localhost     Sandy.foo.sas.com     Sandy

   3. If you do not know the host name, at a command prompt type nslookup %COMPUTERNAME%. Then look at the "Name:" entry.

      You can also type set at a command prompt. Then look for computername and userdnsdomain. For example:

         COMPUTERNAME=Sandy
         USERDNSDOMAIN=foo.sas.com

   
   
4. Check whether the SAS Metadata Server service was created and verify what state it is in (for example, Started, Starting, or nothing). Click Start ► Run and type services.msc. Scroll down and look for the SAS SASMeta - Metadata Server entry (for example, SAS [EMTM-Lev1] SASMeta - Metadata Server). In this entry, EMTM is the name of your configuration directory.
   
   
5. Open the Task Manger.
   1. Right-click on a blank spot on the task bar at the bottom of the Windows screen and select Start Task Manager.
   2. Select the Processes tab.
   3. Click the image name to sort the list alphabetically and see how many java.exe processes are running.

      Do you see any CPU or memory usage changes on any of the java.exe processes?

      If you watch these processes during the installation, you should see java.exe processes start and disappear. During the metadata configuration stage, you might see three java.exe processes running.

   
   
6. Go to the configuration directory to see whether any log files are being created. The default location is C:\SAS\configuration-directory\Lev1\Logs\Configure. If log files are not being created, identify the last two files that were created. If one of those files is person.xml, open the metadatasrv_configureMetadata_date-time.log and look at the last line in the log. Do you see the following:

   [delete] Deleting C:\Docume~1\SAS\Locals~1\Temp\_setup20814\MetadataDeployment\person.xml

   If you do, reference SAS Note 39865 "The SAS 9.2 Metadata Server configuration becomes unresponsive while deleting the person.xml object."
   
   

7. Check the User Account Control (UAC).
   
   
8. Remember to select Log on as a batch job and Access this computer from the network. Also ensure that permissions are not denied:
   1. Click Start ► Settings ► Control Panel ► Administrative Tools ► Local Security Policy.
   2. Click User Rights Assignments under Local Policies and check all of these settings:
      • log on as a batch job
      • access to this computer from the network
      • deny log is on as a batch job (you should not be part of this)
      • deny access to this computer from the network (you should not be part of this)

      For more details see "Windows Privileges" in the SAS 9.2 Intelligence Platform: Security Administration Guide.

      You can also type secpol.msc at the Start ► Run line, to access the User Rights Assignments.

9. You might have an insufficient memory problem and starting the installation with the -Xmx1024M or -Xmx512M command option during configuration could enable the installation to complete. Normally, this approach is used only when you are migrating large EBI configurations. However, with an out-of-the-box installation, you can probably use the -Xmx512M command option.

   When you run the SAS^® Deployment Wizard from the command line, C:\SAS Software Depot\setup.exe -javaoptions "-Xmx512M" , only select Configure Software during the installation; there is no need to install the products again.

   To do this go to a command prompt. Click Start ► Run and type cmd. Type the following at the subsequent prompts:

      cd\
      cd C:\SAS Software Depot   (replace with your depot location)
      setup.exe -javaoptions "-Xmx512M"

   
   
10. Run the SAS Deployment Manager to unconfigure:
    1. Make sure there are no SAS services running. Click Start ► Run and type services.msc.) Look for SAS configuration-directory Lev1 - SAS Meta. If it is running, stop it.
    2. Delete the newly created configuration directory (for example, C:\SAS\EmDesktop).
    3. Delete the service key if it was created. To do this, perform one of the following steps:
       • Go to an MS-DOS command prompt. Click Start ► Run and type cmd). Then type the appropriate start .bat file with -remove at the end. Here is an example for the SAS Metadata Server:
         cd C:\SAS\EMDesktop\Lev1\SASMain\MetadataServer> MetadataServer.bat -remove
         .
       • Go to the services window. Click Start ► Run and type services.msc. Highlight the service, right-click, and select properties. Highlight the service name (for example, SAS [EMDesktop-Lev1] SASMeta - Metadata Server).
       • Go to an MS-DOS command prompt. Click Start ► Run and type cmd. Type sc "service name" -remove. Here is an example:
         sc -remove "SAS [EMDesktop-Lev1] SASMeta - Metadata Server"
       • You can remove the registry entry for the appropriate server service. Remember that changing the registry is the last resort and you should always back up your registry before you make changes to it.
         1. Click Start ► Run and type regedit.
         2. Go to the following location in your registry: HKEY_LOCAL_MACHINE ► System ► CurrentControlSet ► Services
         3. Select the name of SAS service, right-click, and select Delete. For example: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SAS [EMDesktop-Lev1] SASMeta - Metadata Server

            Here is additional documentation about removing services:

            • "Removing a SAS Service" in the SAS 9.2 Companion for Windows, Second Edition
            • SAS Note 12462 "How to remove the old services for SAS Servers" (reference Solution 3)

            NOTE: It is very important to look in the services window after you remove the service, to make sure it is gone. Click Action ► Refresh from the menu and if the service is still listed, reboot the pc. On some operating systems, the service window might not reflect the changes until a reboot occurs. This will affect the SAS installation. So if it is still listed, reboot.

    4. Reboot the PC to make sure everything is all cleaned up.
    5. Log in as an Admin account (the same one that you originally used) and close all non-essential applications, including anti-virus software.
    6. Start the installation again. Select Install SAS Software, when the Deployment Type window appears. Select a planned deployment. Do not check Install Software, ONLY check CONFIGURE. The software should already be installed at this point. It just needs to be configured.
    7. If this is a single machine installation, when prompted for the metadata server information use localhost in both host name fields.

If the problem persists, submit a problem request to Technical Support and send the following information if it is available. If the information is not available, indicate that you were not able to find a particular file. This can help in our diagnosis.

• The SDW.log and the bootstrap.log from C:\Documents and Settings\userID-performing-installation\Local Settings\Application Data\SAS\SASDeploymentWizard\9.2 or C:\Users\userID-performing-installation\AppData\Local\SAS\SASDeploymentWizard\9.2

  Note that you might need to make sure hidden files are showing in order to see these files. For more information about hidden files, search the Windows Help on your machine or search the Microsoft Web site. Here is the link for Windows XP.

• The MIT.log (if it exists) located at C:\Program Files\SAS\InstallMisc\InstallLogs\Maintenance\MIT*.log
• The metadata server log from Configuration-directory\Level-directory\SASMeta\MetadataServer\Log (for example, C:\SAS\EMDesktop\Lev1\SASMeta\MetadataServer\Logs).
• The system.nfo name. To find this information, click Start ► Run and type msinfo32.exe. When the System Information window is displayed, click File ► Save and type system.nfo to identify the name.
• The image from which you are installing. Tell us how that image was created:
  1. Is this copied media? Try the original media.
  2. Is this the original depot that was created from the Electronic Software Download?
  3. Was the depot created by running the "Create a SAS Software Depot" tool?
  4. Did you copy the depot from one machine to another machine? Try creating the depot again by running the "Create a SAS Software Depot" from the original order.
  5. Have you tried installing from a local SAS Software Depot?
  6. Are you pointing to a UNC path or a mapped drive letter? If it is a UNC path, try using a mapped drive to the depot.

     The following SAS Notes discuss some known problems with long pathnames and with UNC paths:

     • SAS Note 36058 "The installation might fail when you install SAS® 9.2 Foundation from a SAS Software Depot if the fully qualified pathname is too long"
     • SAS Note 37370 "An Install Failure dialog box displays "An error has occurred while processing installation package files" when you install SAS® 9.2 Foundation"
     • SAS Note 33606 "Spaces in the SAS Software Depot path might interfere with the installation of SAS® software"
     • SAS Note 34235 "When installing SAS from a UNC path or a mapped drive, the SAS® 9.2 installation might fail immediately when the System Requirements Wizard starts up"

Operating System and Release Information