E Appendix: Common Installation Errors

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

JMS Queues Do Not Work

If there is no infrastructure for IPv6 protocol, you must disable IPv6:

To disable IPv6 on Microsoft Windows, see the following web site:
```
http://support.microsoft.com/kb/929852
```
To disable IPv6 on Novell SLEPOS, 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
C:\tmp\j2ee\orbo\staging\ORBO-trunk\build.xml:941: The following error occurred
 while executing this line:
C:\tmp\j2ee\orbo\staging\ORBO-trunk\build-common-wl.xml:83: startWebLogic.sh
 under C:/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
C:\tmp\j2ee\orbo\staging\ORBO-trunk\build.xml:1022: The following error occurred while executing this line:
C:\tmp\j2ee\orbo\staging\ORBO-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).

Loading Parameters Fails

Symptom:

The Back Office load parameters script fails at installation time.

Solution:

This error occurs if the listen address from the Back Office domain does not match the address used in the build.xml file for the installation.

Modify localhost in the build.xml file in the Back Office installation directory to match the Back Office domain listen address. For information on setting up the listen address, see the Oracle WebLogic documentation.