This section describes known installation issues and associated solutions.
This problem has been observed on several Linux systems. It is most common on Java Desktop System 2 but has also been observed on Linux Red Hat distributions.
After clicking the "Finish" button on the last installer screen, the installer fails to launch a browser window containing the product About page or product registration page, and hangs indefinitely, not returning the command prompt.
Exit the installer by pressing Ctrl+C in the terminal window in which the installer was started. After doing this, browser window containing product About page or registration page will sometimes be launched, but if it does not show up, start the browser and enter following URL in order to review About page:
If you also selected the installation option to register the product, follow the link to registration page available on product About page.
On OpenSolaris 2008.11, when you attempt to start the domain with the asadmin start-domain command, the following error message is displayed:
Timeout waiting for domain domain1 to go to starting state. CLI156 Could not start the domain domain1.
The domain has started successfully. Correct the time and date after rebooting the machine.
On Windows, immediately after installing Application Server Enterprise Edition, the Message Queue broker fails on startup with a message saying the directory drive:\as\domains\domain1\imq does not exist.
Note that if the broker is started after starting domain1, the directory will be created by the Application Server and the problem will not occur.
Create the var_home_dir_location before creating the broker:
$imqbrokerd -varhome var_home_dir_location
$imqbrokerd -varhome D:\as\domains\domain1\imq
If the Communications Server productregistry file contains shared component configurations, an Communications Server uninstallation procedure does not update the productregistry file correctly, and you will not be able to use silent mode in a subsequent installation unless the productregistry file is renamed or removed. Leaving the shared components entries in the productregistry file intact is by design, but it leads to confusion with subsequent silent installs.
After a successful uninstallation is reported back through uninstall log files, delete the productregistry file prior to running a subsequent installation. To verify that a previous uninstallation has completed successfully, look for a appserv_uninstall.class file in as-install. This file will not be present if the uninstallation was successful.
Do not delete the productregistry if the uninstallation was not successful.
The productregistry file is located in /var/sadm/install on Solaris and /var/tmp on Linux.