Troubleshooting AdminSuite 3.0 Client Installations

The following may help resolve the issues you may encounter when running AdminSuite 3.0 on Microsoft Windows platforms.

• Problem: After trying to start the admapp.bat file, a DOS window appears temporarily but disappears without starting anything.

  Solution #1: It is likely that one of thjeenvironment variable in the addmapp.bat file is incorrect. Make sure that the following environment variables are set as indicated here: WS should be set to the directory where AdminSuite is installed. For example: WS=C:\AdminSuite JAVA_HOME should be set to the Java JRE or Java JDK install path. For example: set JAVA_HOME=C:\java CLASSPATH should be set to point to at least the following: .;%WS%\opt\classes;%JAVA_HOME%;<swingpath>\swingall.jar. For example: set CLASSPATH=.;C:\AdminSuite\opt\classes;C:\java;C:\AdminSuite\opt\swingall.jar.

  Solution #2: The correct version of Java must exist. The entire JDK is not needed, just the JRE will suffice but which ever is there must be version 1.1.6 or comptatible. Sometimes using a JFC swingset other than what gets shipped with AdminSuite can cause problems. JFC Swingset version 1.0.3 should be used for now. There appear to be some problems with running version 1.1. If problems are encountered and any error messages with "JFrame" appear, it may be necessary to use the JFC swingset supplied with the AdminSuite installation.

• Problem: After starting the AdminSuite Client for Microsoft Windows, and attempting to log in, an error comes back stating that the RMI registry could not be connected.

  Solution #1: The AdminSuite Server is not running on the machine you specified. Enter the name of a valid AdminSuite server and restart the AdminSuite Client.

  Solution #2: Make sure the user name and password exist within the context of the machine name you specified for your default AdminSuite Server.