Troubleshooting JAMS Services

Each JAMS Service generates a ServiceName.log, such as JAMSScheduler.log, in the installation directory. These logs are reset every Sunday with the previous weeks log files renamed to ServiceNameArchive.log, such as JAMSSchedulerArchive.log. The default location is C:\Program Files\MVPSI\JAMS\Scheduler.

NOTE: JAMS Services writes any serious errors to the Windows Event log. When troubleshooting JAMS, always check the event log and the .log files.

If you suspect there are problems with JAMS, shutting down one of the three services may resolve your issues. The list below provides some guidelines from the least to most disruptive option.

Restart the JAMS Scheduler

While the JAMS Scheduler Service does the most work, restarting it is the least disruptive. Restarting the JAMS Scheduler Service does not cause any Jobs failures and all job completion information remains intact. While the JAMS Scheduler service is stopped, no new Jobs can enter into the Schedule.

Stop the JAMS Server Service

The JAMS Server service may be stopped without losing any job execution information. The JAMS Client will not function while the JAMS Server service is shut down.

Shut down the JAMS Executor Service

Stopping the JAMS Executor service should be a last resort, as it will not typically resolve JAMS issues. This service executes and monitors Jobs. When this service is halted, completion information for any executing Jobs will be lost and some executing Jobs may fail. The JAMS Executor service does not access the JAMS database, so stopping this service won’t be necessary during SQL service maintenance.