Publish Delayed Page Versions

You are currently browsing articles tagged Publish Delayed Page Versions.

Enable debug logging for EPiServer Scheduler

April 3, 2008 | 3 comments

If you have problems with the EPiServer Scheduler Service unexcitingly stopping you can also turn on debug logging to get more clues.

Change EPiServer.SchedulerSvc.exe.config FILE

You need to add the following to the service’s config-file to get detailed call stacks for exceptions that occur in you web application:

<system.runtime.remoting>
  <customErrors mode="Off"/>
</system.runtime.remoting>

Update EPiServer.SchedulerSvc Registry

image Prepare a folder for the log file and make sure the account running the service has write access. I’m usually lazy and give everyone full access since this logging usually is not left on forever.

User RegEdit and change the ImagePath value for the EPiServer Scheduler Service to include a parameter with the log-filename.

HKLM\SYSTEM\CurrentControlSet\Services\EPiServer.SchedulerSvc
ImagePath = C:\Program Files\EPiServer.Scheduler\EPiServer.SchedulerSvc.exe D:\Log\EPiServer.SchedulerSvc.log

Be careful when you edit the Registry! I use to export the key to a file before I change anything so I can look at the original configuration.

See also: Auto Restart of EPiServer Scheduler Service

Tags: , , , , , , ,

Auto Restart of EPiServer Scheduler Service

April 3, 2008 | 5 comments

imageThere are several functions in a EPiServer Web Application that rely on the Services installed by EPiServer Manager. For example delayed publish of a new version of a page at a specific time, mirroring of pages between servers, archiving pages that has past the stopped publish date and removing old pages from the waste basket.

Requirements for Scheduled Jobs in EPiServer

Several things must be true for tasks to be executed:

  • The Service must be running
    The service is installed and updated by EPiServer manager but you may have to configure it and setup the in the computers Administrative Tool for Services.
  • Each EPiServer Web must be allowed to use the Service
    There is only one instance of the Service but there might be several Web Applications. Each has a setting that controls if they are allowed imageto connect to the service or not. This often misunderstood setting is displayed on the Capability page in EPiServer Manager.
  • Each Job must be active and have a schedule
    You must also for each Web Application go to admin mode and enable each Scheduled Job by checking Active and give it a schedule.

The EPiServer Scheduler Service does not appear to be active

imageIf you have satisfied all requirements above and it suddenly stops working it can be an uncaught exception that halts your service.

My recommendation is always to configure the EPiServer Services to automatically restart if it should stop unexpectedly. This can be done from the Recovery Tab in the Properties for each Service.

Update

See also: Enable debug logging for EPiServer Scheduler

Tags: , , , , , ,