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:
- Go to the SASHOME/deploymntreg directory.
- Copy the original sas.tools.viewregistry.jar file to a temporary directory.
- Run the sas.tools.viewregistry.jar file from the temporary directory.
Set Either, or Both, of the JAVA_HOME and CLASSPATH Environment Variables
Preliminary steps:
Example: C:\Program Files\SAS\
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
- Determine the location of SASHOME.
- Determine the location of the Java home directory.
Commands:
Note: The report is saved to the directory from which the viewregistry.jar file is run.
- Click Start ► Run to display the command prompt and run the following commands at the prompt.
- cmd
- cd\
- C:
- cd Program Files\SAS\deploymntreg
- 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
- Verify that the correct version of JAVA appears: java -version
- 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;
- sas.tools.viewregistry.jar
- Note: The filename ViewRegistry.jar might appear in the directory instead.
- 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.
***Please note that the JAVA_HOME and the CLASSPATH environment variables are only good for the Command Prompt session you are in. Once you close the Command Prompt window, those settings are not retained. You can set them up permanently thru the Environment Variables setup for your operating system. Use the following steps to open the Environment Variables:
a. Click New to add a new variable name and value.
For example:
Variable Name JAVA_HOME
Variable Value C:\Program Files (x86)\Java\jre6
Click OK
b. Click New to add another new variable name and value.
For example:
Variable Name CLASSPATH
Variable Value .;C:\;C:\Program Files\Java\jre6\bin;
Click OK, OK and OK.
Run the .jar File from the Java Directory
Preliminary steps:
- Right-click My Computer from your desktop or in Windows Explorer, and then click Properties.
- Click the Advanced tab or Advanced System Settings.
- Click Environment variables.
- In the System Variables section, perform the following steps:
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
- Determine the location of SASHOME
- .
Example: C:\Program Files\SAS\
- Determine the location of the Java home directory.
- Note: In SAS 9.4, you may use the Private JRE located here: C:\Program Files\SASHome\SASPrivateJavaRuntimeEnvironment\9.4\jre\bin\
Commands:
- Click Start ► Run to display the command prompt and run the following commands at the prompt.
- cmd
- cd\
- C:
- 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
- Verify that Java is running correctly: java -version
- java -jar "C:\Program Files\SAS\deploymntreg\sas.tools.viewregistry.jar"
- Note the report will be created in the directory that you are sitting at when you run the sas.tools.viewregistry.jar. From the above example the DeploymentRegistry.html and the DeploymentRegistry.txt files would be created in the C:\Program Files (x86)\Java\jre6\bin directory.
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.
Manually type in the commands, instead of using cut and paste
In some cases you might see garbage characters in the command prompt window after you run the command. If you then manually type the command, you will see the expected results. Another option is to copy the content into Notepad, then highlight the text in Notepad and select Edit>Copy, then paste the text into the Command window.
For example:
Exception in thread "main" java.lang.NoClassDefFoundError: ûjar
Caused by: java.lang.ClassNotFoundException: ûjar
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
Could not find the main class: ΓÇôjar. Program will exit.
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 KB0036131: "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
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.