Trouble Shooting at Startup

Out of environment space

• Reason: This error message is thrown while starting batch files present in the <Agent Toolkit Home>/bin directory. Problem with the Windows' environment variable settings causes this error.

• Solution: Modify the properties of your DOS prompt (right click on the title bar of the DOS prompt window, select properties,choose memory tab, in that increase the value of the initial environment field (preferably 4096)).

Too many parameters

• Reason: This error arises due to problem with the Windows' PATH variable which doesn't accept paths which include space in their names (e.g., c:\program files)

• Solution: Modify the path variable to a DOS compatible one (ie., c:\program files can be changed to c:\progra~1 ).

MS-Dos window starts and closes immediately

• Reason: While starting a batch file the MS-Dos window appears and is closed immediately. This occurs when JAVA_HOME is not set correctly in the setenv.bat file present in the <Agent Toolkit Home>/bin directory.

• Solution: Please verify if JAVA_HOME is set correctly in the setenv.bat file. The jdk version and the drive in which you have installed jdk should be the same as that specified in the file. If not, modify the JAVA_HOME variable and save the file and restart the tool.

Graphics configuration error

• Reason: This problem occurs if the monitor is configured for 16 colors mode. Swing /awt components of JDK requires at least 256 colors to run.
  Error Message : Exception in thread "main" java.lang.ExceptionInInitializerError: java.lang.RuntimeException:

Unable to create a suitable default GraphicsConfiguration. Try changing your Display Settings.
at sun.awt.Win32GraphicsDevice.getDefaultPix (Native Method)
at sun.awt.Win32GraphicsDevice.getDefaultConfiguration(Win32GraphicsDevice.java:137)
at sun.awt.windows.WToolkit.resetG(WToolkit.java:87)
at sun.awt.windows.WToolkit.<clinit>(WToolkit.java:77)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:120)
at java.awt.Toolkit$2.run(Toolkit.java:512)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:503)

• Solution: Change the monitor configurations to 256 colors or install the Agent Toolkit in a monitor which supports at least 256 colors.

javac not recogonized as an internal or external command

• Reason: The PATH variable is not set properly.

• Soulition: Set the PATH variable if you want to be able to conveniently run the SDK executables (javac.exe, java.exe, javadoc.exe, etc.) from any directory without having to type the full path of the command. If you don't set the PATH variable, you need to specify the full path to the executable every time you run it, such as: C:> \jdk1.2.2\bin\javac MyClass.java
  It's useful to set the PATH permanently so it will persist after rebooting.  To set the PATH permanently, add the full path of the jdk1.2.2\bin directory to the PATH variable. Typically this full path looks something like C:\jdk1.2.2\bin. Set the PATH as follows, according to whether you are on Windows NT or Windows 95/98.

Windows NT - To set the PATH permanently:

1. Start the Control Panel, select System, select Environment, and look for "Path" in the User Variables and System Variables. If you're not sure where to add the path, add it to the right end of the "Path" in the User Variables. A typical value for PATH is:  C:\jdk1.2.2\bin

2. Click "Set", "OK" or "Apply".

3. The new path takes effect in each new Command Prompt window you open after setting the PATH variable.

Windows 98 and Windows 95 - To set the PATH permanently,

1. Open the AUTOEXEC.BAT file and add or change the PATH statement as follows:

2. Start the system editor. Choose "Start", "Run" and enter sysedit, then click OK. The system editor starts up with several windows showing. Go to the window that is displaying AUTOEXEC.BAT.

3. Look for the PATH statement. (If you don't have one, add one.) If you're not sure where to add the path, add it to the right end of the PATH. For example, in the following PATH statement, we have added the bin directory at the right end:

4. PATH C:\WINDOWS; C:\WINDOWS\COMMAND;C:\JDK1.2.2\BIN

5. To make the path take effect in the current Command Prompt window, execute the following: C:> c:\autoexec.bat

To find out the current value of your PATH, to see if it took effect, at the command prompt, type:  C:> path

java.lang.NullPointerException -- com.adventnet.tools.license.LicensingKey.getDays

• Reason: The exception has been noticed with jdk1.4 or j2sdk1.4.0 if Agent Toolkit installation PATH has got space in their directory names. This is caused because of a bug in jdk1.4 where getting a resource (a file here) is not possible under this circumstance. 

• Solution: Please install the Toolkit in a PATH, which does not have space and try running the application.