London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!

Nicklas Israelsson
Jan 22, 2009
  5767
(0 votes)

Scheduler not active when using Extension (X3)

When using X3 on your CMS 5 sites (mainly SP2) you might find out that your scheduled jobs doesn't run. When looking at the jobs in admin mode you get this message: "The EPiServer Scheduler Service does not appear to be active, it may have been stopped."

On a regular site you follow this FAQ and the scheduler starts to work for your site. But when using X3 this might not work.

We've found out that the problem is caused by the installation package. It adds the extension httpmodule on the same row as the scheduler initialization module and thus removing it. Your httpmodules section in web config might look something like this:

<httpModules>
  <!--<add name="BasicAuthentication" type="EPiServer.Security.BasicAuthentication, EPiServer" />-->
  <add name="Dropit.Extension" type="Dropit.Extension.Handlers.HttpModule, Dropit.Extension" />
  <add name="WorkflowRuntime" type="EPiServer.WorkflowFoundation.WorkflowSystem, EPiServer.WorkflowFoundation" />
  <add name="UrlRewriteModule" type="EPiServer.Web.UrlRewriteModule, EPiServer" />
  ...
</httpModules>

To fix this you'll need to manually re-add the scheduler initialization module. After adding it your httpmodules it might look something like this:

<httpModules>
  <!--<add name="BasicAuthentication" type="EPiServer.Security.BasicAuthentication, EPiServer" />-->
  <add name="Initializer" type="EPiServer.Scheduler.Initializer, EPiServer.Scheduler" />
  <add name="Dropit.Extension" type="Dropit.Extension.Handlers.HttpModule, Dropit.Extension" />
  <add name="WorkflowRuntime" type="EPiServer.WorkflowFoundation.WorkflowSystem, EPiServer.WorkflowFoundation" />
  <add name="UrlRewriteModule" type="EPiServer.Web.UrlRewriteModule, EPiServer" />
  ...
</httpModules>

After adding this you can follow the above mentioned FAQ and your scheduler should now once again be active.

Jan 22, 2009

Comments

Please login to comment.
Latest blogs
Creating a Dropdownlist in Optimizely CMS: Populate ISelectionFactory with values from another block's properties

Create a Block to hold selection options using EPiServer.Cms.Shell.UI.ObjectEditing.EditorDescriptors; using EPiServer.PlugIn; using EPiServer.Shel...

sunylcumar | May 12, 2025

Opal AI available in Optimizely CMS (SaaS)

Use Opal AI to translate your content!

Tomas Hensrud Gulla | May 12, 2025 |

Get Up to Speed with Optimizely Opal: Quick Start Resources

Exciting New Feature Updates to Optimizely Opal: Elevating Your Product Experience We're thrilled to announce the launch of massive feature updates...

Patrick Lam | May 9, 2025

Scan file uploads for Malware in EPiServer/Optimizely CMS 11 - EPiServer Forms

Do you have forms on your website where visitors can upload files? Perhaps CV's for job applications or documentation for claims, or other kind of...

Allan Thraen | May 9, 2025 |

Exposing Color Picker to Content Graph

A guide on how to consume custom CMS property backing types in a headless architecture, using a color picker as an example.

Damian Smutek | May 9, 2025 |

Exam Prep Sessions are now live: Here's what you need to know!

So you've decided to level with an Optimizely certification. Congratulations! That's a smart move for your career in digital experince, but anyone...

Satata Satez | May 8, 2025