Dec 20, 2010
  9399
(2 votes)

Troubleshooting the Scheduler

 We have seen a influx of cases regarding the Scheduler service, so I thought it would be a good time to write about how to troubleshoot it yourself!

The deal

The scheduling service run jobs you define for it and also EPiServer's own shipped jobs, such as archiving pages, subscription and delete wastebasket pages.

But sometimes it goes wrong and the scheduler doesn't automatically run the jobs anymore. It's stuck.

The tactics

We have a few tactics we use. First one is to delete the, possibly corrupted,  config file and there's a FAQ item describing how to do that. If that doesn't work we usually suggest to the client to delete all the rows in the two tables the scheduler uses, tblScheduledItem and tblScheduledItemLog. To be able to do that you must first deactivate the foreign key defined on tblScheduledItemLog to tblScheduledItem. This can be achieved using the first line below.

ALTER TABLE tblScheduledItemLog NOCHECK CONSTRAINT ALL
ALTER TABLE tblScheduledItemLog CHECK CONSTRAINT ALL

Don't worry about truncating these two tables as they are recreated by the Scheduler service. But as always when making changes directly in the database you should take a backup. Safety first, don't forget that!

The third way is to figure it out yourself by logging the Scheduler service. The scheduler service can use the log4net logging framework (as all of our services), so you only need to drop a log4net.dll and a log4net.config (see the fileAppender section) in its folder for it to start logging. This way you can see what's causing the scheduler to fail and hopefully you can fix it yourself.

Example of a log4net.config file 

<?xml version="1.0" encoding="utf-8" ?>
<log4net>
<appender name="ErrorAppender" type="log4net.Appender.FileAppender" >
<file value="C:\temp\LogServerError.log" />
<appendToFile value="true" />
<layout type="log4net.Layout.PatternLayout">
<conversionPattern value="%d [%t] %l - %m%n" />
</layout>
</appender>

<root>
<level value="ALL" />
<appender-ref ref="ErrorAppender" />
</root>
</log4net>

Dec 20, 2010

Comments

Please login to comment.
Latest blogs
CMS 13: The New Core Element of Your AI-First Optimizely Platform

CMS 13 is out and already brings solid AI-first foundations. With impressive features already shipped and an exciting roadmap ahead, this is the...

Michał Mitas | Apr 11, 2026 |

Deploying to Linux in SaaS (Configured) Commerce

With Optimizely SaaS (Configured) Commere now suporting net8.0 extensions dll, you will need to make a small tweak to how you distribute you...

Mark Hall | Apr 10, 2026 |

Optimizely CMS 13 and the Alloy demo site

The Alloy demo site now runs on Optimizely CMS 13. Here’s a quick guide to getting it up and running locally.

Tomas Hensrud Gulla | Apr 10, 2026 |

A day in the life of an Optimizely OMVP: Getting Up to Speed with Optimizely CMS 13 — A Free Learning Path

If you're working with Optimizely and haven't started exploring CMS 13 yet, now's the time. I've put together a dedicated CMS 13 course within the...

Graham Carr | Apr 10, 2026