locked
Does anyone know why immediate alerts timer job might stop mid execution? RRS feed

  • Question

  • Platform: 32 bit MOSS 2007 service pack 3, 1 web front end

    Twice this week I have checked the Central Admin timer job status page and found the Immediate alerts job with this status:

    Initialized 40% date/time

    When I restart the Windows Timer Service, and wait a minute, then I see

    Succeeded 100%

    When I look in the 12 hive and event logs, I see no indication at the date/time of the "halted" timer job of any problem in the system.

    After the first occurance,I recreated the timer job and ran the updatealerttemplates operation.

    The first time it happened, the time stamp was about a week and a half ago. This time, it was about 30 hours ago.

    I would like to find a way to "fix" things so that the timer job just keeps running, or at least I would like to find a log file that documented why it was stopping mid-iniitalization.

    Thursday, January 31, 2013 8:47 PM