Jobs may not run properly on the Job Server


If a problem occurs in the TAC database, it is possible that Jobs will not run properly. This generally happens when there is a duplicate entry in the database that prevents normal operation. This could occur with manual execution or a scheduled job.



Windows or Linux



Jobs from Job Conductor will not run either manually or on schedule.

The following error is located in the logs:

ERROR ExecutionTriggerableHelper  - org.talend.administrator.common.exception.UnicityExceptionorg.talend.administrator.common.exception.SystemException: org.talend.administrator.common.exception.UnicityException
        at org.talend.administrator.scheduler.persistence.helper.ExecutionTaskHelper.findByIdQuartzJob(
        at org.talend.administrator.scheduler.persistence.helper.ExecutionTaskHelper.findByIdQuartzJob(
        at org.talend.administrator.executionplan.persistence.helper.ExecutionTriggerableHelper.getByIdQuartzJob(
        at org.quartz.simpl.SimpleThreadPool$
Caused by: org.talend.administrator.common.exception.UnicityException
        at org.talend.administrator.scheduler.persistence.helper.ExecutionTaskHelper.findByIdQuartzJob(
        ... 5 more



To fix this issue, look at the ExecutionTask table in the TAC database.

Look for the same idQuartzJob duplicated in this table and remove the conflicting entry.

Note: Be sure you have a complete backup of the database before making any modifications to it.

Version history
Revision #:
8 of 8
Last update:
‎05-05-2017 06:25 PM
Updated by:
Tags (1)