UPDATE 12/10/07: Hotfix as described in MSDN KB929816 solved the problem for us mentioned below. Obtain the hotfix and then install on each server on the farm. Igitur, sharepoint configuration utility on each server. Here is the MS Support link for that KB: http://support.microsoft.com/kb/932816.

Background:

An environmental engineering amet habemus negotium ubi necessitas requirit ut 30 some-odd manufacturing locations located throughout the United States needs to ensure that those plants file for their various state-mandated permits in a timely fashion. One approach we’ve investigated leverages the "Pause Until Date" activity available to us via SharePoint Designer worfklow. The engineering manager (vel eius vicarii) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Environment:

MUSCUS, 64 frenum, Rectum Apparatus environment (progressionem buxum), 2 servientibus (In SQL servo #1, omnia alia server #2).

Problemata:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. Autem, Quisque a quam non faciat (pro nobis).

1. Job non workflow est scheduled ad currere, ever. I discovered this by reading through CHRISTOPHORVS Albus scriptor (http://chrissyblanco.blogspot.com/2007/06/issues-with-delay-activity-in-moss.html) excellent write-up by using stsadm thusly:
   

   C:\>stsadm -o getproperty -propertyname "job-workflow" -url http://localhost

   <Property Exist="No" />

   C:\>

   Quod mirum erat, sed facile solvitur per:

   C:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 inter minutes 0 et LIX" -url http://localhost

   Operatio feliciter expletum.

   C:\>

   Quod faciendum, the first "In Progress" workflow celeriter officium fecit et concitus.

2. Miserabile, the next one didn’t work as expected. Gratanter, Christopher refers us hic (http://support.microsoft.com/kb/932816). As of writing of this entry, IT department sumus expectantes obtinere hotfix, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, ita spero satisfaciet proposito.

Workaround:

Re-running the stsadm -o setproperty command seemed to prod the workflow timer awake. It would, Violatis 7 minutes laxus, actually wake up and continue along with the workflow.

Quæstiones / Alloquitur exitibus:

Donec mora Date non operatur.

Date mora Donec non recuperabit.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"