This page should be help you if your JobScheduler installation was succesfull installed apperently but does not work.

check the installation log

First of all you have to 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 any error message like a java runtime exception.

If you are not able to solve an installation problem please contact us via mail (info@sos-berlin.com).

try to start the JobScheduler manually

Go to a console session on the machine you have the JobScheduler installed. Change the directory to the bin folder of your installation directory and try to start the JobScheduler e.g.

 cd /usr/sos-berlin.com/jobscheduler/scheduler-1.3.12.2187/bin 
 jobscheduler.sh start

respectively for Windows

 cd C:\Program Files\sos-berlin.com\jobscheduler\scheduler-1.3.12.2179\bin
 jobscheduler.cmd start

check the scheduler log

Starting the JobScheduler a log file named 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 you should check the documents below and the other documents in the section Trouble shooting of our Wiki.

If you do not find a solution please do not hesitate to contact us via the help forum or per mail (info@sos-berlin.com). In this case please note the document What infos the support need in case of a support-request?.

<span id"articles">more articles that could help to solve the problem</span>h1. * How will JobScheduler determine the location of the JVM (MS Windows only)?

• Z-JAVA-101 Java Virtual Machine is not started
• No license key was found or License key has been expired. <span ih1. "data">find out where the data directory is located</span>
  If you not sure where your data directory is, 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:

 set SCHEDULER_DATA=...

or

 SCHEDULER_DATA=...

It will tell you the location of your data directory.

 [back to Trouble Shooting|JobScheduler_FAQ#Trouble_Shooting]