What is the purpose of the "Trigger" button?
My understanding is that it will trigger the job immediately.
However it's throwing:
Quartz.SchedulerException: Job threw an unhandled exception. ---> Quartz.JobPersistenceException: Couldn't store job: Unable to store Job: 'epg.epg-export', because one already exists with this identification. ---> Quartz.ObjectAlreadyExistsException: Unable to store Job: 'epg.epg-export', because one already exists with this identification. at Quartz.Impl.AdoJobStore.JobStoreSupport.StoreJob(ConnectionAndTransactionHolder conn, IJobDetail newJob, Boolean replaceExisting) in c:\Program Files (x86)\Jenkins\workspace\Quartz.NET\src\Quartz\Impl\AdoJobStore\JobStoreSupport.cs:line 913
I think when you call StdScheduler.ScheduleJob(), it will actually try store the JobDetail AGAIN. This is causing issue because it conflicts with existing DB primary key.
What is the purpose of the "Trigger" button? My understanding is that it will trigger the job immediately. However it's throwing:
Quartz.SchedulerException: Job threw an unhandled exception. ---> Quartz.JobPersistenceException: Couldn't store job: Unable to store Job: 'epg.epg-export', because one already exists with this identification. ---> Quartz.ObjectAlreadyExistsException: Unable to store Job: 'epg.epg-export', because one already exists with this identification. at Quartz.Impl.AdoJobStore.JobStoreSupport.StoreJob(ConnectionAndTransactionHolder conn, IJobDetail newJob, Boolean replaceExisting) in c:\Program Files (x86)\Jenkins\workspace\Quartz.NET\src\Quartz\Impl\AdoJobStore\JobStoreSupport.cs:line 913
I think when you call
StdScheduler.ScheduleJob()
, it will actually try store the JobDetail AGAIN. This is causing issue because it conflicts with existing DB primary key.