In some instances, the Deployment Registry tool might not function correctly, and execution of the sas.tools.viewregistry.jar file might fail to generate files that identify SAS software products that are installed on your system.

To troubleshoot this problem, perform one or more of the following procedures.

Run the .jar File from a Temporary Directory

Perform the following steps:

1. Go to the SASHOME/deploymntreg directory.
2. Copy the original sas.tools.viewregistry.jar file to a temporary directory.
3. Run the .jar file from the temporary directory.

Set Either, or Both, of the JAVA_HOME and CLASSPATH Environment Variables

Preliminary steps:

1. Determine the location of SASHOME .
Example: C:\Program Files\SAS\
2. Determine the location of the Java home directory.
Examples:
For a Windows 32-bit system: C:\Program Files\Java\jre1.5.0_12
For a Windows x64 system: C:\Program Files (x86)\Java\jre6

Commands:

1. Click Start ► Run to display the command prompt and run the following commands at the prompt.
2. cmd
3. cd\
4. C:
5. cd Program Files\SAS\deploymntreg
6. Enter one of the following, depending on your environment:
• For all Windows environments except for Windows 7 and Windows 2008 R2:

set JAVA_HOME=C:\Program Files\Java\jre1.5.0_12

• For Windows 7 and Windows 2008 R2:

set JAVA_HOME=C:\Program Files (x86)\Java\jre6
7. Verify that the correct version of JAVA appears: java -version
8. Enter one of the following, depending on your environment:
• For all Windows environments except for Windows 7 and Windows 2008 R2:
  set classpath=.;C:\;C:\Program Files\Java\jre1.5.0_12\bin;

Note: ".;C:\" is correct.
• For Windows 7 and Windows 2008 R2, use the following command:

set classpath=.;C:\;C:\Program Files\Java\jre6\bin;
9. sas.tools.viewregistry.jar

Note: The filename ViewRegistry.jar might appear in the directory instead.
10. Verify that the report that is created identifies which SAS software products are loaded on your system.
    Typically, this report is saved to C:\Program Files\SAS\deploymntreg.

Note: The report is saved to the directory from which the viewregistry.jar file is run.

Run the .jar File from the Java Directory

Preliminary steps:

1. Determine the location of SASHOME
.
Example: C:\Program Files\SAS\
2. Determine the location of the Java home directory.
Examples:
For a Windows 32-bit system: C:\Program Files\Java\jre1.5.0_12
for a Windows x64 system: C:\Program Files (x86)\Java\jre6

Commands:

1. Click Start ► Run to display the command prompt and run the following commands at the prompt.
2. cmd
3. cd\
4. C:
5. Enter one of the following commands, depending on your environment:
• For all Windows environments except for Windows 7 and Windows 2008 R2: cd Program Files\Java\jre1.5.0_12 \bin
• For Windows 7 and Windows 2008 R2, use the following command: cd Program Files (x86)\Java\jre6\bin
6. Verify that Java is running correctly: java -version
7. java –jar “C:\Program Files\SAS\deploymntreg\sas.tools.viewregistry.jar”

Download a New Copy of the .jar File

Download the file from either of the sources below. Save the .jar file to the SASHOME/deploymntreg directory.

• http://ftp.sas.com/techsup/download/hotfix/HF2/util01/regreport/sas.tools.viewregistry.jar
• ftp://ftp.sas.com/techsup/download/blind/sas.tools.viewregistry.jar

If None of the Suggestions Above Resolves the Problem, Open a Track with SAS Technical Support

Be prepared to provide the following to the Technical Support consultant:

• The sdw.log and the bootstrap.log files.
• For Windows XP and Windows 2003: The default location is C:\Documents and Settings\userid that installed sas\Local Settings\Application Data\SAS\SASDeploymentWizard\9.2
• For Windows Vista, Windows 7, and Windows 2008 Server: The default location is C:\Users\userid that installed sas\AppData\Local\SAS\SASDeploymentWizard\9.2
• The directories in which the SAS software resides, if there are multiple versions of SAS software installed on your system.
• The output and results from performing the following steps:
  • Click Start ► Run and submit the following commands at the prompt.
  • cmd
  • java -version
  • set path
• The system.nfo file. Perform the following steps:
  • Click Start ► Run.
  • Type msinfo32.exe and press ENTER. The System Information appears.
  • Click File ► Save.
  • Type system for the filename.
  • Save the file in any directory.

For more details, see SAS Note 35968: "Using the ViewRegistry Report and other methods to determine the SAS^® 9.2 and SAS^® 9.3 software releases and hot fixes that are installed."

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	Base SAS	Windows 7 Enterprise 32 bit	9.21_M2		9.2 TS2M2
		Windows 7 Enterprise x64	9.21_M2		9.2 TS2M2
		Windows 7 Home Premium 32 bit	9.21_M2		9.2 TS2M2
		Windows 7 Home Premium x64	9.21_M2		9.2 TS2M2
		Windows 7 Professional 32 bit	9.21_M2		9.2 TS2M2
		Windows 7 Professional x64	9.21_M2		9.2 TS2M2
		Windows 7 Ultimate x64	9.21_M2		9.2 TS2M2
		Windows 7 Ultimate 32 bit	9.21_M2		9.2 TS2M2
		Microsoft® Windows® for 64-Bit Itanium-based Systems	9.21		9.2 TS2M0
		Microsoft Windows Server 2003 Datacenter 64-bit Edition	9.21		9.2 TS2M0
		Microsoft Windows Server 2003 Enterprise 64-bit Edition	9.21		9.2 TS2M0
		Microsoft Windows XP 64-bit Edition	9.21		9.2 TS2M0
		Microsoft® Windows® for x64	9.21		9.2 TS2M0
		Microsoft Windows Server 2003 Datacenter Edition	9.21		9.2 TS2M0
		Microsoft Windows Server 2003 Enterprise Edition	9.21		9.2 TS2M0
		Microsoft Windows Server 2003 Standard Edition	9.21		9.2 TS2M0
		Microsoft Windows XP Professional	9.21		9.2 TS2M0
		Windows Vista	9.21		9.2 TS2M0

* 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.

---

This note addresses what to do when you cannot create a report of the deployment registry to see which SAS software is installed on your system.

Type:	Problem Note
Priority:	high

Date Modified:	2011-03-31 09:13:55
Date Created:	2010-02-01 08:34:53