java.lang.RuntimeException: org.pentaho.platform.api.scheduler2.SchedulerException: QuartzJobKey.ERROR_0002 - Missing data in jobId "Admin:!@#$%^&*()_+{}|":P?>< testing <>?:"{}|\][';/.,:1365445528198".

Pentaho BI Platform Tracking | Sarah Moursalien | 4 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    Steps: 1. Right-click on any report and select Schedule 2. Select Recurrence type of seconds, minutes, hours, daily, monthly or yearly 3. Type into the pattern textbox an alpha character 4. Click Next and OK to create the Schedule BUG 1: Get Server Error 500 1. Right-click on any report and select Schedule 2. Select Recurrence type of Cron 3. Type into the Cron String: 0 15 10 * * ? 2005 (Notice the invalid year) 4. Click Next and OK to create the Schedule BUG 2: Get Server Error 500 1. Right-click on any report and select Schedule 2. Type Special Characters into the Schedule Name 3. Click Next and Ok to create the Schedule BUG 3: the schedule does not get added to the workspace. Error in log: ERROR [org.quartz.core.JobRunShell] Job Admin.Admin:!@#$%^&*()_+{}|":P?>< testing <>?:"{}|\][';/.,:1365445528198 threw an unhandled Exception: java.lang.RuntimeException: org.pentaho.platform.api.scheduler2.SchedulerException: QuartzJobKey.ERROR_0002 - Missing data in jobId "Admin:!@#$%^&*()_+{}|":P?>< testing <>?:"{}|\][';/.,:1365445528198". at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.getBlockOutJobs(PentahoBlockoutManager.java:49) at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.getBlockOutJobTriggers(PentahoBlockoutManager.java:102) at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.shouldFireNow(PentahoBlockoutManager.java:62) at org.pentaho.platform.scheduler2.quartz.BlockingQuartzJob.execute(BlockingQuartzJob.java:36) at org.quartz.core.JobRunShell.run(JobRunShell.java:199) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:546) Caused by: org.pentaho.platform.api.scheduler2.SchedulerException: QuartzJobKey.ERROR_0002 - Missing data in jobId "Admin:!@#$%^&*()_+{}|":P?>< testing <>?:"{}|\][';/.,:1365445528198". at org.pentaho.platform.scheduler2.quartz.QuartzJobKey.parse(QuartzJobKey.java:75) at org.pentaho.platform.scheduler2.quartz.QuartzScheduler.setJobTrigger(QuartzScheduler.java:455) at org.pentaho.platform.scheduler2.quartz.QuartzScheduler.getJobs(QuartzScheduler.java:436) at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.getBlockOutJobs(PentahoBlockoutManager.java:37) ... 5 more

    Pentaho BI Platform Tracking | 4 years ago | Sarah Moursalien
    java.lang.RuntimeException: org.pentaho.platform.api.scheduler2.SchedulerException: QuartzJobKey.ERROR_0002 - Missing data in jobId "Admin:!@#$%^&*()_+{}|":P?>< testing <>?:"{}|\][';/.,:1365445528198".
  2. 0

    Steps: 1. Right-click on any report and select Schedule 2. Select Recurrence type of seconds, minutes, hours, daily, monthly or yearly 3. Type into the pattern textbox an alpha character 4. Click Next and OK to create the Schedule BUG 1: Get Server Error 500 1. Right-click on any report and select Schedule 2. Select Recurrence type of Cron 3. Type into the Cron String: 0 15 10 * * ? 2005 (Notice the invalid year) 4. Click Next and OK to create the Schedule BUG 2: Get Server Error 500 1. Right-click on any report and select Schedule 2. Type Special Characters into the Schedule Name 3. Click Next and Ok to create the Schedule BUG 3: the schedule does not get added to the workspace. Error in log: ERROR [org.quartz.core.JobRunShell] Job Admin.Admin:!@#$%^&*()_+{}|":P?>< testing <>?:"{}|\][';/.,:1365445528198 threw an unhandled Exception: java.lang.RuntimeException: org.pentaho.platform.api.scheduler2.SchedulerException: QuartzJobKey.ERROR_0002 - Missing data in jobId "Admin:!@#$%^&*()_+{}|":P?>< testing <>?:"{}|\][';/.,:1365445528198". at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.getBlockOutJobs(PentahoBlockoutManager.java:49) at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.getBlockOutJobTriggers(PentahoBlockoutManager.java:102) at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.shouldFireNow(PentahoBlockoutManager.java:62) at org.pentaho.platform.scheduler2.quartz.BlockingQuartzJob.execute(BlockingQuartzJob.java:36) at org.quartz.core.JobRunShell.run(JobRunShell.java:199) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:546) Caused by: org.pentaho.platform.api.scheduler2.SchedulerException: QuartzJobKey.ERROR_0002 - Missing data in jobId "Admin:!@#$%^&*()_+{}|":P?>< testing <>?:"{}|\][';/.,:1365445528198". at org.pentaho.platform.scheduler2.quartz.QuartzJobKey.parse(QuartzJobKey.java:75) at org.pentaho.platform.scheduler2.quartz.QuartzScheduler.setJobTrigger(QuartzScheduler.java:455) at org.pentaho.platform.scheduler2.quartz.QuartzScheduler.getJobs(QuartzScheduler.java:436) at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.getBlockOutJobs(PentahoBlockoutManager.java:37) ... 5 more

    Pentaho BI Platform Tracking | 4 years ago | Sarah Moursalien
    java.lang.RuntimeException: org.pentaho.platform.api.scheduler2.SchedulerException: QuartzJobKey.ERROR_0002 - Missing data in jobId "Admin:!@#$%^&*()_+{}|":P?>< testing <>?:"{}|\][';/.,:1365445528198".
  3. 0

    If in Pentaho 4.8 you have a schedule with a colon (:) in the name, and run the Pentaho 4.8 to 5.0 migration utility the scheduler in 5.0 does not work. Scheduled jobs fail, and the scheduler perspective reports that there are no scheduled jobs. The only way to fix this is to re-initialize your 5.0 Quartz database, edit the schedules in 4.8 to remove the colon, and re-run the migration utility. I personally do not care whether the fix is to change the migration utility to remove colons from the schedule name or a fix to the scheduler so it can handle colons in the schedule name. The error is: 11:40:42,670 ERROR [JobRunShell] Job joe.joe:Purge Mondrian Schema Cache:1387305441511 threw an unhandled Exception: java.lang.RuntimeException: org.pentaho.platform.api.scheduler2.SchedulerException: QuartzJobKey.ERROR_0002 - Missing data in jobId "jodea:Daily at 6:00 - Email-Daily-Channel-AllStore-0521:1387305441901". at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.getBlockOutJobs(PentahoBlockoutManager.java:49) at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.getBlockOutJobTriggers(PentahoBlockoutManager.java:102) at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.shouldFireNow(PentahoBlockoutManager.java:62) at org.pentaho.platform.scheduler2.quartz.BlockingQuartzJob.execute(BlockingQuartzJob.java:37) at org.quartz.core.JobRunShell.run(JobRunShell.java:199) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:546) Caused by: org.pentaho.platform.api.scheduler2.SchedulerException: QuartzJobKey.ERROR_0002 - Missing data in jobId "jodea:Daily at 6:00 - Email-Daily-Channel-AllStore-0521:1387305441901". at org.pentaho.platform.scheduler2.quartz.QuartzJobKey.parse(QuartzJobKey.java:75) at org.pentaho.platform.scheduler2.quartz.QuartzScheduler.setJobTrigger(QuartzScheduler.java:462) at org.pentaho.platform.scheduler2.quartz.QuartzScheduler.getJobs(QuartzScheduler.java:443) at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.getBlockOutJobs(PentahoBlockoutManager.java:37) ... 5 more 11:40:42,673 ERROR [ErrorLogger] Job (joe.joe:Purge Mondrian Schema Cache:1387305441511 threw an exception. org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: java.lang.RuntimeException: org.pentaho.platform.api.scheduler2.SchedulerException: QuartzJobKey.ERROR_0002 - Missing data in jobId "jodea:Daily at 6:00 - Email-Daily-Channel-AllStore-0521:1387305441901".] at org.quartz.core.JobRunShell.run(JobRunShell.java:210) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:546) Caused by: java.lang.RuntimeException: org.pentaho.platform.api.scheduler2.SchedulerException: QuartzJobKey.ERROR_0002 - Missing data in jobId "jodea:Daily at 6:00 - Email-Daily-Channel-AllStore-0521:1387305441901". at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.getBlockOutJobs(PentahoBlockoutManager.java:49) at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.getBlockOutJobTriggers(PentahoBlockoutManager.java:102) at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.shouldFireNow(PentahoBlockoutManager.java:62) at org.pentaho.platform.scheduler2.quartz.BlockingQuartzJob.execute(BlockingQuartzJob.java:37) at org.quartz.core.JobRunShell.run(JobRunShell.java:199) ... 1 more Caused by: org.pentaho.platform.api.scheduler2.SchedulerException: QuartzJobKey.ERROR_0002 - Missing data in jobId "jodea:Daily at 6:00 - Email-Daily-Channel-AllStore-0521:1387305441901". at org.pentaho.platform.scheduler2.quartz.QuartzJobKey.parse(QuartzJobKey.java:75) at org.pentaho.platform.scheduler2.quartz.QuartzScheduler.setJobTrigger(QuartzScheduler.java:462) at org.pentaho.platform.scheduler2.quartz.QuartzScheduler.getJobs(QuartzScheduler.java:443) at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.getBlockOutJobs(PentahoBlockoutManager.java:37) ... 5 more

    Pentaho BI Platform Tracking | 3 years ago | Chris Deptula
    java.lang.RuntimeException: org.pentaho.platform.api.scheduler2.SchedulerException: QuartzJobKey.ERROR_0002 - Missing data in jobId "jodea:Daily at 6:00 - Email-Daily-Channel-AllStore-0521:1387305441901".
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    If in Pentaho 4.8 you have a schedule with a colon (:) in the name, and run the Pentaho 4.8 to 5.0 migration utility the scheduler in 5.0 does not work. Scheduled jobs fail, and the scheduler perspective reports that there are no scheduled jobs. The only way to fix this is to re-initialize your 5.0 Quartz database, edit the schedules in 4.8 to remove the colon, and re-run the migration utility. I personally do not care whether the fix is to change the migration utility to remove colons from the schedule name or a fix to the scheduler so it can handle colons in the schedule name. The error is: 11:40:42,670 ERROR [JobRunShell] Job joe.joe:Purge Mondrian Schema Cache:1387305441511 threw an unhandled Exception: java.lang.RuntimeException: org.pentaho.platform.api.scheduler2.SchedulerException: QuartzJobKey.ERROR_0002 - Missing data in jobId "jodea:Daily at 6:00 - Email-Daily-Channel-AllStore-0521:1387305441901". at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.getBlockOutJobs(PentahoBlockoutManager.java:49) at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.getBlockOutJobTriggers(PentahoBlockoutManager.java:102) at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.shouldFireNow(PentahoBlockoutManager.java:62) at org.pentaho.platform.scheduler2.quartz.BlockingQuartzJob.execute(BlockingQuartzJob.java:37) at org.quartz.core.JobRunShell.run(JobRunShell.java:199) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:546) Caused by: org.pentaho.platform.api.scheduler2.SchedulerException: QuartzJobKey.ERROR_0002 - Missing data in jobId "jodea:Daily at 6:00 - Email-Daily-Channel-AllStore-0521:1387305441901". at org.pentaho.platform.scheduler2.quartz.QuartzJobKey.parse(QuartzJobKey.java:75) at org.pentaho.platform.scheduler2.quartz.QuartzScheduler.setJobTrigger(QuartzScheduler.java:462) at org.pentaho.platform.scheduler2.quartz.QuartzScheduler.getJobs(QuartzScheduler.java:443) at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.getBlockOutJobs(PentahoBlockoutManager.java:37) ... 5 more 11:40:42,673 ERROR [ErrorLogger] Job (joe.joe:Purge Mondrian Schema Cache:1387305441511 threw an exception. org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: java.lang.RuntimeException: org.pentaho.platform.api.scheduler2.SchedulerException: QuartzJobKey.ERROR_0002 - Missing data in jobId "jodea:Daily at 6:00 - Email-Daily-Channel-AllStore-0521:1387305441901".] at org.quartz.core.JobRunShell.run(JobRunShell.java:210) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:546) Caused by: java.lang.RuntimeException: org.pentaho.platform.api.scheduler2.SchedulerException: QuartzJobKey.ERROR_0002 - Missing data in jobId "jodea:Daily at 6:00 - Email-Daily-Channel-AllStore-0521:1387305441901". at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.getBlockOutJobs(PentahoBlockoutManager.java:49) at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.getBlockOutJobTriggers(PentahoBlockoutManager.java:102) at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.shouldFireNow(PentahoBlockoutManager.java:62) at org.pentaho.platform.scheduler2.quartz.BlockingQuartzJob.execute(BlockingQuartzJob.java:37) at org.quartz.core.JobRunShell.run(JobRunShell.java:199) ... 1 more Caused by: org.pentaho.platform.api.scheduler2.SchedulerException: QuartzJobKey.ERROR_0002 - Missing data in jobId "jodea:Daily at 6:00 - Email-Daily-Channel-AllStore-0521:1387305441901". at org.pentaho.platform.scheduler2.quartz.QuartzJobKey.parse(QuartzJobKey.java:75) at org.pentaho.platform.scheduler2.quartz.QuartzScheduler.setJobTrigger(QuartzScheduler.java:462) at org.pentaho.platform.scheduler2.quartz.QuartzScheduler.getJobs(QuartzScheduler.java:443) at org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.getBlockOutJobs(PentahoBlockoutManager.java:37) ... 5 more

    Pentaho BI Platform Tracking | 3 years ago | Chris Deptula
    java.lang.RuntimeException: org.pentaho.platform.api.scheduler2.SchedulerException: QuartzJobKey.ERROR_0002 - Missing data in jobId "jodea:Daily at 6:00 - Email-Daily-Channel-AllStore-0521:1387305441901".

    Root Cause Analysis

    1. org.pentaho.platform.api.scheduler2.SchedulerException

      QuartzJobKey.ERROR_0002 - Missing data in jobId "Admin:!@#$%^&*()_+{}|":P?>< testing <>?:"{}|\][';/.,:1365445528198".

      at org.pentaho.platform.scheduler2.quartz.QuartzJobKey.parse()
    2. org.pentaho.platform
      BlockingQuartzJob.execute
      1. org.pentaho.platform.scheduler2.quartz.QuartzJobKey.parse(QuartzJobKey.java:75)
      2. org.pentaho.platform.scheduler2.quartz.QuartzScheduler.setJobTrigger(QuartzScheduler.java:455)
      3. org.pentaho.platform.scheduler2.quartz.QuartzScheduler.getJobs(QuartzScheduler.java:436)
      4. org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.getBlockOutJobs(PentahoBlockoutManager.java:37)
      5. org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.getBlockOutJobTriggers(PentahoBlockoutManager.java:102)
      6. org.pentaho.platform.scheduler2.blockout.PentahoBlockoutManager.shouldFireNow(PentahoBlockoutManager.java:62)
      7. org.pentaho.platform.scheduler2.quartz.BlockingQuartzJob.execute(BlockingQuartzJob.java:36)
      7 frames
    3. quartz
      SimpleThreadPool$WorkerThread.run
      1. org.quartz.core.JobRunShell.run(JobRunShell.java:199)
      2. org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:546)
      2 frames