Running a report with Run Now hangs the Plant Explorer. Test Action works okay
Running a job by using the Run Now feature of the Scheduling Definition Asepct will hang the Plant Explorer and the report will not run. The report will not run either if the scheduler is allow to dispatch the job per the enabled Scheduling Definition Aspect. However, the report does work if the Test Action method of the Action Aspect is used.
In the c:\temp\Scheduler.log file is a line similar to:
Job "erpTest" will never be scheduled. It must be a descendant of the "Job Descriptions Job Folder"Symptoms:
New Job Folder objects created at same level as the default "Job Description" Job Folder is not supported by scheduler. All new scheduler objects created by the customer for running new jobs must be under the Job Descriptions folder.
create new Job Folder under existing Job Description object in Scheduling Structure.
Note: copying a working Job Folder object with children scheduling objects/aspects to the same level as the default "Job Descriptions" folder may work, but it should not be used as a workaround to this limitation in the Schduler application as copy/paste of scheduler objects/aspects has known bad side effects.