C H A P T E R  6

Troubleshooting

This chapter provides some troubleshooting hints to help you during the installation, start up, or configuration of the Mobile Edition IDE.


Using the solaris_patch_installer

TABLE 6-1 describes some errors you might encounter during installation of Solaris patches using the solaris_patch_installer script.

TABLE 6-1 solaris_patch_installer Errors

Problem

Solution

The solaris_patch_installer aborted while attempting to apply one of the required Solaris patches on your system.

  1. Write down the patchID of the last patch that the solaris_patch_installer tried to install.
  2. Obtain a newer revision of that patch from http://sunsolve.sun.com, if one is available.
  3. Install the new revision on your system using the patchadd utility. If you are unfamiliar with installing Solaris packages, contact your system administrator for assistance.
  4. Run the solaris_patch_installer again to ensure you have all the required Solaris 8 patches on your system.

Receipt of an error message similar to the following, after running the solaris_patch_installer on a newly installed Solaris 8 (update 7) environment:

# ./solaris_patch_installer

Solaris Patch Installer for J2SE, v.1.4.0
Installing 109147-14... successfully installed
Installing 108434-06...

...

Installing 108528-13... attempting to patch a package that is not installed
Installing 108652-51... successfully installed
Installing 108921-13... already applied
Installing 108940-40... successfully installed
Installing 108773-12... pkgadd failed
Cannot continue patch installation.
For more details, please look at /var/tmp/solaris_patch_installer.log

Run the solaris_patch_installer script a second time. If you continue to have problems, contact your Solaris system administrator.



Installing the Mobile Edition IDE

TABLE 6-2 describes some errors you might encounter during the Mobile Edition IDE installation.

TABLE 6-2 Mobile Edition IDE Installation Errors

Problem

Solution

Receipt of the following error message while installing the Mobile Edition IDE:
Error writing file = There may not be enough temporary disk space. Try using -is:tempdir to use a temporary directory on a partition with more disk space

Start the installer with the -is:tempdir command-line option, in order to specify a directory on a disk with more free space.

For example, in a Solaris operating environment, you might type the following at the command prompt:

$ ffj_me_solsparc_en.bin -is:tempdir temporary-directory

The Sun ONE Studio 4 update 1 installer fails and displays a message that there is not enough available disk space to use for installation. But, the filesystem you specified to use for installing the IDE has plenty of available disk space.

The filesystem you have specified is symbolically linked to another filesystem whose large amount of disk space is not recognized. For example, in a Solaris environment, /export/home has 2 GB of space and / has 100 MB. The /opt directory is symbolically linked to /export/home. If you specified /opt/s1studio as the IDE installation directory, the Sun ONE Studio 4 update 1 installer does not recognize the symbolic link to /export/home, which has 2 GB of available disk space. The installer only recognizes the / directory, which is the target directory for /opt and only has 100 MB.

To correct the problem, directly specify the filesystem with the larger available disk space. For the preceding example, specify /export/home as the installation directory.

Receipt of the following error message while installing the Mobile Edition IDE:
Error: Could not find JVM

Start the installer with the -is:javahome command-line option, in order to specify a directory on a disk with more free space.

For example, in a Solaris operating environment, type the following at the command prompt:

$ ffj_me_solsparc_en.bin -is:javahome javahome

(Solaris or Linux environments only) The Sun ONE Studio 4 update 1 installer looks like it is hung, after it was started. No messages are displayed.

You may not have set the DISPLAY environment variable correctly. If you are installing on your local system, the DISPLAY environment variable should be set to :0.0. If you are using a superuser (root) account or doing a remote installation, set your DISPLAY environment variable to your local system.

For example, to set the DISPLAY variable from a root account that is using a C-shell, type the following in the command window you used to log into the root account:

setenv DISPLAY your-local-host:0.0.

Run the installer again from the same command window.

The Sun ONE Studio 4 update 1 IDE installer exits without installing the product. No messages are displayed.

These are the possible causes and solutions:

  • The file you have downloaded from the Sun ONE Studio 4 update 1 product download page is not complete. Download the file again and check that the size of the downloaded file is the same as the file size specified on the product download page. Run the IDE installer again.
  • You have specified an invalid command-line parameter in the installer.sp file. Check the file and correct any incorrect command-line parameter setting. Run the IDE installer again.
  • Run the installer launcher (<installer>.exe file or <installer>.bin file) with the option <installer>.exe/bin -is:log log.txt. Check log.txt for possible errors

The -is:tempdir commandline parameter is not working.

Make sure that you are using the correct syntax for the command-line parameter for the installer. For example, on a Solaris environment, the syntax is as follows:

ffj_me_solsparc_en.bin -is:tempdir temporary-directory

(Solaris environment only) Not able to eject the product CD when running the installer manually. (This problem occurs when you are installing the IDE from the merged product CD. Hence, two CD-ROMs are involved in the installation.)

When running the installer manually, do not run it from within its own directory.



Starting Up the Mobile Edition IDE

TABLE 6-3 describes some errors you might receive during startup and configuration of the newly installed Mobile Edition IDE software.

TABLE 6-3 Mobile Edition IDE Startup and Configuration Errors

Problem

Solution

Receipt of an error message similar to the following during the IDE startup in a supported Solaris environment:
Error: Java 2 SDK search failed to find a suitable J2SDK!

Reinstall the SDK while logged in as superuser and ensure that the installation directory is on the root level.

Receipt of an error message similar to the following during the IDE startup in asupported Solaris environment:
Error: No J2SE was found at /usr/j2se/bin/java
ERROR: The following required 5.8 patches have not been installed on system "myserver": 106950-16 106327-11 106541-17

NOTE: You can download and install the J2SE[tm] and related Solaris[tm] patches from http://access1.sun.com/forte/.

Warning:Current runtime environment does not satisfy minimum requirements.

Install the J2SE, v. 1.4.0_02 platform on your system. For a Solaris 8 operating environment, include any necessary patches. Refer to for more information on installing this software on your system.

Receipt of the following error message after starting the IDE:
Error: Unable to load java.dll

Make sure there is no space in the name of the directory in which you have installed the J2SE, v. 1.3.1 or J2SE, v. 1.4.0_02 platform.

Mobile Edition IDE is not pointing to the J2SE, v. 1.4.0 platform you had specified during the IDE installation and you receive an error message similar to the following:

ERROR: The J2SE[tm] 1.2.1 found at /usr/java1.2/bin/java cannot be used by the IDE. J2SE[tm] 1.4 is recommended.
NOTE: You can download and install the J2SE[tm] and related Solaris[tm] patches from http://access1.sun.com/forte/.

Warning:Current runtime environment does not satisfy minimum requirements.

Check the Java environment variables already set prior to starting the IDE and unset them.

The values of the $JAVA_PATH and $JDK_HOME environment variables override the value of the J2SE SDK path you specified during the IDE installation. You need to unset these environment variables or use the -jdkhome command-line option when starting the IDE.

The user directory is created in the wrong location in a Microsoft Windows system.

If you have previously installed any edition of the Sun ONE Studio 4 IDE in a Windows environment, the location of the user directory is recorded in the Microsoft Windows Registry under HKEY_CURRENT_USER/Software/Sun Microsystems, Inc./Forte for Java/ME/4.0. This value is not deleted when you uninstall the IDE. Therefore, when you install another version of the Sun ONE Studio 4 IDE, the user directory specified in a previous installation is reused.

If you want to use a different location for the user directory, do the following:

  1. Uninstall the Mobile Edition IDE.
  2. In a command window, type regedit to start the Microsoft Windows Registry editor.
  3. From the Registry editor, expand the HKEY_CURRENT_USER registry and the keys for Software/Sun Microsystems, Inc./Forte for Java/ME/4.0
  4. Right-click the UserDir value and choose Delete from the contextual menu.
  5. Install the Mobile Edition IDE again.
  6. After installation, start the Mobile Edition IDE and when you are prompted, specify a new location for the user directory.

(Solaris environment only) Receipt of the following error message: Cannot find product /product.xml on your computer.

Stop and start volume management (vold) on the system, and run the installer again.

To stop volume management:

1. Ensure that media are not being used.

If you are not sure whether you have found all users of the media, use the fuser command.

2. Become superuser.

3. Type the volmgt stop command:

# /etc/init.d/volmgt stop

#

To restart volume management:

1. Become superuser.

2. Type the volmgt start command:

# /etc/init.d/volmgt start

volume management starting



Configuring an External Compiler

TABLE 6-4 describes a problem you might encounter when compiling MIDlets or MIDlet suites.

TABLE 6-4 Mobile Edition IDE Compilation Errors

Problem

Solution

Receipt of compilation errors after switching to an external compiler or updating the internal compiler.

The Java Wireless Toolkit v.1.0.3 preverifier does not support JDK 1.4.0 classes. If you are using theJ2SE, v. 1.4.0_02 platform, the default for the Preverify compiler is an internal compiler. If you want to use an external compiler or download an updated internal compiler, you need to configure the Preverify Compiler properties within the Mobile Edition to use the external compiler.

To configure the Preverify compiler:

  1. Choose Tools right arrow Options right arrow Building right arrow Compiler Types right arrow Preverify Compiler. The properties for the Preverify Compiler are listed on the right.
  2. Click in the Java Compiler property field and select External Compilation from the menu.
  3. Click on the ellipsis(...) button in the External Compiler property field and add the switch -target 1.1 to the Process field.
    The syntax for the External Compiler property is: {jdk.home}{/}bin{/}javac -target 1.1 {debug info} {deprecation} {optimize} {outputdir} {encoding} {source opt} {bootclasspath.opt} {bootclasspath} -classpath {filesystems}{:} {classpath} {files}.
  4. Click OK to finish.