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

Pozadina:

Imamo poslovne zahtjev u kojem inženjerstva okoliša manager treba osigurati da 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 (ili njezin pomoćnik) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Okolina:

MOSS, 64 bit, virtualni stroj okoliš (Razvoj box), 2 poslužitelji (SQL na poslužitelju #1, sve ostalo na poslužitelju #2).

Problemi:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. Međutim, to ne radi i iz kutije (za nas).

1. Tijek posao nije na rasporedu, ever. I discovered this by reading through Christopher Whitea (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:\>

   To je čudno, ali rezultat se lako riješiti:

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

   Operacija je uspješno završena.

   C:\>

   Na taj događaj, the first "In Progress" tijek brzo vatru i učinio da je posao.

2. Nažalost, the next one didn’t work as expected. Srećom, Christopher refers us ovdje (http://support.microsoft.com/kb/932816). As of writing of this entry, čekamo IT odjela dobiti taj hitni popravak, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, pa se nadam da će to riješiti problem.

Rješenje:

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

Pitanja / Razmatrana pitanja:

Pauza Do danas ne rade.

Pauza do datuma se ne vraća.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"