Try our conversational search powered by Generative AI!
AI OnAI Off
EPiServer Scheduler Service does not appear to be active. "DemoXFromsPostsGeneratorJob" should have been executed.
Don't recognize the name of that scheduled job, but DemoXfromsPostGeneratorJob is likely an obsolete job either from pre-CMS 6 version of EPiServer (if your site was upgraded), or from a CMS 6 dashboard gadget (as suggested here: http://world.episerver.com/Forum/Developer-forum/EPiServer-CMS-6-CTP-2/Thread-Container/2011/3/DB-deadlocks-involving-DemoXFromsPostsGeneratorJob-loadbalanced/).
If you are sure you don't need the DemoXfromsPostGeneratorJob job running, disable it via the admin interface.
Occasionally, the database table containing the job queue might get corrupted and prevent other jobs from running. You might need to clear the queue or reset the execution date as described here: http://stackoverflow.com/questions/17651558/episerver-schedule-job-not-running-automatically. You will need database access to do this (remember, backup!)
Sep 04, 2013 23:42
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
Hi,
One of our custom Scheduled Jobs (under CMS -> Admin Mode -> Scheduled Jobs) gives the following message:
"The EPiServer Scheduler Service does not appear to be active, it may have been stopped. Next job "DemoXFromsPostsGeneratorJob" should have been executed".
Does this mean that the Scheduler Service has stopped (for whatever reasons, i.e. not necessarily caused by this particular scheduled job) and hence this custom scheduled job does not run anymore?
And what is DemoXFromsPostsGeneratorJob?
Leonard