| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
This page should be help you if your JobScheduler installation was succesfull successful installed apperently , but apparently does not work.
...
Check the installation log
- First of all you
...
- should check the installation log. It is located in the folder logs in your data directory of your JobScheduler installation. The name of the log file follows the pattern Install_V<version><timestamp><ident_no>.log.
- Check this file for
...
- error messages, e.g. a Java run-time exception.
- If you are not able to solve an installation problem please contact
...
- us.
Try
...
to start the JobScheduler manually
Go to Start a console session on the machine where you have installed the JobScheduler installed. Change Navigate to the directory to with the bin folder of your installation directory and try to start the JobScheduler, e.g. by
| Code Block | ||||
|---|---|---|---|---|
| ||||
cd /usr/sos-berlin.com/jobscheduler/scheduler-1.3.12.2187/bin
jobscheduler.sh start
|
...
| Code Block | ||||
|---|---|---|---|---|
|
...
cd C:\Program Files\sos-berlin.com\jobscheduler\scheduler-1.3.12.2179\bin
jobscheduler.cmd start
|
...
Check the scheduler log file
Starting the JobScheduler a log file named with the name scheduler.log will be created. You will find this file in the data directory of your JobScheduler installation. If you find one or more lines containing the text [ERROR then you should check the documents below and the other documents in the section Trouble shooting of our Wiki Troubleshooting section.
- If you do not find a solution then please do not hesitate to contact
...
- us
More
...
articles that could help to solve the
...
problem
...
...
- ?
- Z-JAVA-101 Java Virtual Machine is not started
- No license key was found or License key has been expired. <span ih1. "data">find
| Anchor | ||||
|---|---|---|---|---|
|
...
located
If you are not
...
certain where your data directory is
...
located then check the content of the script jobscheduler_environment_variables.cmd (for windows) respectively jobscheduler_environment_variables.sh (for Unix) in the bin folder of your installation path.
You will find a line like this:
| Code Block | ||
|---|---|---|
| ||
set SCHEDULER_DATA=...
|
or
| Code Block | ||
|---|---|---|
| ||
SCHEDULER_DATA=...
|
It This will tell you the location of your data directory.
...
| Anchor | ||||
|---|---|---|---|---|
|
- If you do not find a solution then please contact us via Community Resources.
- In this case please note the instructions in What information will SOS need when you submit a support request?
...