| Oracle® Retail Point-of-Service Installation Guide Release 14.1 E54459-01 |
|
 Previous |
 Next |
This appendix describes some common errors encountered during installation of Point-of-Service and Mobile Point-of-Service.
If you see this error message, there could be some settings incorrectly set or problems with the installer itself. For more information, check the
<POS_install_directory>/pos/logs/installer_log.txt file.
Symptom:
The application fails when starting up:
[java] Dispatcher.main, Exception: java.security.AccessControlException: access
denied (java.util.PropertyPermission * read,write)
[java] java.security.AccessControlException: access denied
(java.util.PropertyPermission * read,write)
[java] at java.security.AccessControlContext.checkPermission(Unknown
Source)
[java] at java.security.AccessController.checkPermission(Unknown Source)
[java] at java.lang.SecurityManager.checkPermission(Unknown Source)
[java] at java.lang.SecurityManager.checkPropertiesAccess(Unknown Source)
[java] at java.lang.System.getProperties(Unknown Source)
[java] at
com.extendyourstore.foundation.tour.conduit.Dispatcher.<init>(Dispatcher.java:461)
[java] at
com.extendyourstore.foundation.tour.conduit.Dispatcher.getDispatcher(Dispatcher.java:1301)
[java] at
com.extendyourstore.foundation.tour.conduit.Dispatcher.main(Dispatcher.java:2439)
[java] at
com.extendyourstore.foundation.config.TierLoader.main(TierLoader.java:359)
Solution:
This error usually occurs because the JRE that you are pointing to does not contain the updated java.security file, for example, jre\lib\security\java.security.
Symptom:
The application dies when starting up. Check the
<POS_install_directory>/pos-install-yyyyMMddHHmm.log file, where yyyyMMddHHmm is the timestamp of the install. In the log file, search for Database 'offlinedb' not found.
ERROR 2007-07-29 15:54:49,608 4938 (main:com.extendyourstore.foundation.manager.data.JdbcDataConnection): [com.extendyourstore.foundation.manager.data.JdbcDataConnection.logSQLException (JdbcDataConnection.java:1355)] Get Connection failed :Database 'offlinedb' not found.
Solution:
This error occurs the first time the client is started after it is installed. The server was unable to establish a connection to the database. This prevented the offlinedb database from being created.
This error usually occurs because incorrect information was entered in the Database Configuration window during the install. Reinstall the server with the correct database configuration information. Check that the IDDI folder was created for the server in
<POS_install_directory>/pos/bin.
Symptom:
The application installer quits with the following error message:
BUILD FAILED C:\tmp\j2ee\ormpos\staging\ORMPOS-trunk\build.xml:941: The following error occurred while executing this line: C:\tmp\j2ee\ormpos\staging\ORMPOS-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 Server 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 E), 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 D).
Symptom:
The application installer quits with the following error message:
BUILD FAILED C:\tmp\j2ee\ormpos\staging\ORMPOS-trunk\build.xml:1022: The following error occurred while executing this line: C:\tmp\j2ee\ormpos\staging\ORMPOS-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 E), 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 D).
