Views: 4665
Number of votes: 0
Average rating:

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

Please login to comment.