Possible causes are:
Java not found
To check if Java is installed and configured, first try to start the server.
If Java cannot be found, the file wrapper.log contains a message similar to the following:
ERROR | wrapper | 2019/01/25 14:30:35 | Unable to execute Java command. The system cannot find the file specified. (0x2)
Please check that you have Java 8 installed. Furthermore the environment variable JAVA_HOME has to point to the location of the Java installation (the directory containing the bin directory). If you do not want to change the value of the JAVA_HOME variable, you can use the environment variable XSERVER1_JAVA_HOME.
You should note that if neither the environment variable JAVA_HOME nor the environment variable XSERVER1_JAVA_HOME is defined, the wrapper.log contains an additional warning similar to the following:
WARN | wrapper | 2019/01/25 14:30:35 | The 'JAVA_HOME' environment variable was referenced but has not been defined.
Unsupported Java version
To check if the version of the configured Java installation is supported, first try to start the server.
If the Java version is unsupported, the file wrapper.log contains a message similar to the following:
FATAL | wrapper | 2019/01/25 15:37:36 | The version of Java specified by wrapper.java.command (9)
FATAL | wrapper | 2019/01/25 15:37:36 | is greater than the maximum allowed (1.8).
Please check that you have Java 8 installed. Furthermore the environment variable JAVA_HOME has to point to the location of the Java installation. If you do not want to change the value of the JAVA_HOME variable, you can use the environment variable XSERVER1_JAVA_HOME.
Missing or insufficient license
To check whether the license is valid or not, start the server in console mode (using <xserver>.bat under windows or <xserver>.sh console under Linux). An adequate message should occur if there is no valid license file.
If your license file has expired, the file wrapper.log contains a message similar to the following, so you can check immediately whether your problem is caused by an invalid license.
INFO | jvm 2 | 2010/11/29 09:59:08 | licensing error -6 / file error
If your license expires while the PTV xServer is running, it is shutting down. When it restarts, the error message from above is shown in your log file. Furthermore there is an entry in your log file some time before the license expires.
Illegal installation directory
Following the same procedure as above, you will get an adequate error message if this is the case. To correct that, check whether your installation path contains whitespaces - these are not allowed!
Possible causes are:
Corrupted Configuration
See the configuration section for details on legal values.
Missing data
Are the configured data paths correct? Note that paths must use posix-separators (forward-slashes '/') to separate directories. Some module might want trailing '/' characters at the end of the path.
Possible causes are:
Startup time exceeds default timeout setting of 30sec
Add or change the registry entry ServicePipeTimeout to a higher value such as 180000 to allow all processes to initialise. See also Microsoft Support Page.
/tmp/boost_interprocessPossible causes are:
This folder lacks the sticky bit
Add the sticky bit to that folder by executing chmod +t /tmp/boost_interprocess. Note that this is a folder which may also be used by other application, side-effects might be possible.
These error codes indicate a general exception during server startup and may be symptom of an installation problem.
| 0 |
OK - no error occurred Illegal installation / root path - the path must not contain whitespaces. |
| 99 | Licensing exception |
| 50 | Module was not able to start - please check the module configuration file for invalid data configuration. |
| 52 | Module Timeout - the module did not receive a ping from the server for a certain time and hence will go down. |
| 54 | Module could not be initialised, the PTV xServer will be shut down. This is typically the case if there is a problem in the module specific configuration such as a typing error in the data path. |
| 102 | Unable to open the alive port. Either there is a port misconfiguration or the port is already in use on your system. |
| 103 | Illegal/invalid server config. The configuration file xserver.properties does contain invalid settings or is not accessible. |
Copyright © 2024 PTV Logistics GmbH All rights reserved. | Imprint