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

Sfond:

Għandna rekwiżit tan-negozju fejn manager inġinerija ambjent jeħtieġ li tiżgura li 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 (jew assistent tagħha) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Ambjent:

MOSS, 64 bit, ambjent magna virtwali (kaxxa iżvilupp), 2 servers (SQL fuq server #1, kull ħaġa oħra fuq server #2).

Problemi:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. Madankollu, ma jaħdimx sew barra mill-kaxxa (għalina).

1. Ix-xogħol workflow kienx skedat jiddekorri, ever. I discovered this by reading through Christopher White Paper (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:\>

   Dan kien riżultat sorprendenti imma jissolvew faċilment:

   C:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 minuta bejn 0 u 59" -url http://localhost

   Operazzjoni kompluta b'suċċess.

   C:\>

   Malli tagħmel dan, the first "In Progress" workflow malajr fired up u ma impjieg huwa.

2. Sfortunatament, the next one didn’t work as expected. Thankfully, Christopher refers us hawn (http://support.microsoft.com/kb/932816). As of writing of this entry, aħna qed jistennew għall-dipartiment IT sabiex tikseb dan hotfix, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, hekk nisperaw li dan se ssolvi l-problema.

Workaround:

Re-running the stsadm -o setproperty command seemed to prod the workflow timer awake. It would, bejn wieħed u ieħor 7 minuti wara, actually wake up and continue along with the workflow.

Mistoqsijiet / Kwistjonijiet indirizzati:

Pause Sa Data ma taħdimx.

Pause Sa Data ma jerġa 'jibda.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"