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

Aurrekariak:

Enpresa-baldintza, non ingurumen ingeniaritza kudeatzailea behar ziurtatu dugu 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 (edo bere laguntzaile) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Ingurumena:

Moss, 64 bit, Makina birtual ingurumena (garapen kutxa), 2 zerbitzariak (SQL zerbitzari batean #1, beste guztia zerbitzari batean #2).

Arazoak:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. Hala eta guztiz ere, ez da ongi atera kutxa (Gurekin).

1. Workflow lana ez zen programatuta exekutatu, ever. I discovered this by reading through Christopher White en (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:\>

   Duten emaitza harrigarria izan zen, baina erraz konpondu:

   C:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 minutu artean 0 eta 59" -url http://localhost

   Eragiketa burutu.

   C:\>

   Gainean egiten duten, the first "In Progress" workflow azkar tiro sortu eta bere lana egin.

2. Tamalez, the next one didn’t work as expected. Zorionez, Christopher refers us hemen (http://support.microsoft.com/kb/932816). As of writing of this entry, IT departamentuko ari gara Hotfix zuzenketa hori lortzeko zain, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, beraz, espero honek arazoa konponduko.

Sahiesteko:

Re-running the stsadm -o setproperty command seemed to prod the workflow timer awake. It would, gutxi gorabehera 7 minutu geroago, actually wake up and continue along with the workflow.

Galderak / Aleak Norentzat:

Data pausatu arte ez du funtzionatzen.

Data pausatu arte ez da hasi berriro.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"