E Appendix: Common Installation Errors

This appendix describes some common errors encountered during installation of Central Office.

JMS Queues Do Not Work

If there is no infrastructure for IPv6 protocol, you must disable IPv6. To disable IPv6 on Linux, Solaris, or AIX, consult with your System Administrator on the specific steps needed.

Unreadable Buttons in the Installer

If you are unable to read the text within the installer buttons, it probably means that your JAVA_HOME needs to be set to a version 7 JDK. Set JAVA_HOME to a Java development kit of version 7 or later and run the installer again.

WebLogic Domain Does Not Exist

Symptom:

The application installer quits with the following error message:

BUILD FAILED
/tmp/j2ee/orco/staging/ORCO-trunk/build.xml:941: The following error occurred
 while executing this line:
/tmp/j2ee/orco/staging/ORCO-trunk/build-common-wl.xml:83: startWebLogic.sh under
 /opt/Oracle/Middleware/user_projects/domains/base_domain is missing.
 Installation cannot continue.

Solution:

This error occurs because the WebLogic domain provided does not exist.

Make sure that the domain exists, and then check the ant.install.properties file for entry mistakes. Pay close attention to the input.deployer.uri (see Appendix D), input.admin.user, and input.admin.password properties. If you need to make a correction, you can run the installer again with this file as input by running silent mode (see Appendix B).

WebLogic Domain Server is Not Started

Symptom:

The application installer quits with the following error message:

BUILD FAILED
/tmp/j2ee/orco/staging/ORCO-trunk/build.xml:1022: The following error occurred 
while executing this line:
/tmp/j2ee/orco/staging/ORCO-trunk/build-common-wl.xml:152: url http://localhost:
7001/console is not available. Installation cannot continue.

Solution:

This error occurs because the WebLogic domain server provided is not running.

Make sure that the WebLogic domain server is running, and then check the ant.install.properties file for entry mistakes. Pay close attention to the input.deployer.uri (see Appendix D), input.wl.domain.path, input.admin.user, and input.admin.password properties. If you need to make a correction, you can run the installer again with this file as input by running silent mode (see Appendix B).

"Could not create system preferences directory" Warning

Symptom:

The following text appears in the installer Errors tab:

[May 22, 2006 11:16:39 AM java.util.prefs.FileSystemPreferences$3 run
WARNING: Could not create system preferences directory. System preferences are unusable.
May 22, 2006 11:17:09 AM java.util.prefs.FileSystemPreferences
 checkLockFile0ErrorCode
WARNING: Could not lock System prefs. Unix error code -264946424

Solution:

This is related to Java bug 4838770. The /etc/.java/.systemPrefs directory may not have been created on your system. See http://bugs.sun.com for details.

This is an issue with your installation of Java and does not affect the Oracle Retail product installation.