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

Bakgrunnur:

Við hafa a viðskipti kröfu þar umhverfis verkfræði framkvæmdastjóri þarf að tryggja að 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 (eða aðstoðarmaður hennar) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Umhverfi:

Moss, 64 hluti, raunverulegur vél umhverfi (þróun kassi), 2 netþjónum (SQL á vefþjóninum #1, allt annað á þjóninum #2).

Vandamál:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. Hins, það virkar ekki vel út af the kassi (fyrir okkur).

1. The workflow starf var ekki áætlað að keyra, ever. I discovered this by reading through Christopher er hvítur (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:\>

   Það var óvart vegna en auðveldlega leyst:

   C:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 mínútur á milli 0 og 59" -url HTTP://localhost

   Aðgerð lokið.

   C:\>

   Þegar aðgerð sem, the first "In Progress" workflow rekinn fljótt upp og gerði það starf.

2. Því miður, the next one didn’t work as expected. Sem betur fer, Christopher refers us hér (http://support.microsoft.com/kb/932816). As of writing of this entry, við erum að bíða eftir að IT deild til að fá að snarhasti, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, svo vonandi mun þetta leysa vandamál.

Lausn:

Re-running the stsadm -o setproperty command seemed to prod the workflow timer awake. It would, u.þ.b. 7 mínútum síðar, actually wake up and continue along with the workflow.

Spurningar / Mála sem:

Hlé þar til dagsetning virkar ekki.

Hlé þar til dagsetning ekki aftur.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"