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. Toe, sharepoint configuration utility on each server. Here is the MS Support link for that KB: http://support.microsoft.com/kb/932816.

Agtergrond:

Ons het 'n besigheid vereiste waar 'n omgewing ingenieurswese bestuurder nodig het om te verseker dat 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 (of haar assistent.) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Omgewing:

MOSS, 64 bietjie, virtuele masjien omgewing (ontwikkeling boks), 2 servers (SQL op bediener #1, alles op bediener #2).

Probleme:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. Egter, dit werk nie goed uit die boks (vir ons).

1. Die workflow taak is nie om te hardloop, ever. I discovered this by reading through Christopher White se (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:\>

   Dit was 'n verrassende uitslag, maar maklik opgelos:

   C:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 minute tussen 0 en 59" -url http://localhost

   Operasie suksesvol voltooi.

   C:\>

   By dit te doen, the first "In Progress" workflow vinnig afgedank word en het dit se werk.

2. Ongelukkig, the next one didn’t work as expected. Gelukkig, Christopher refers us hier (http://support.microsoft.com/kb/932816). As of writing of this entry, ons wag vir die IT-afdeling te verkry dat die hotfix, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, so hopelik sal dit die probleem op te los.

Work Around:

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

Vrae / Kwessies:

Stop Tot Datum werk nie.

Stop Tot Datum hervat nie.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"