અપડેટ 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.

પૃષ્ઠભૂમિ:

We have a business requirement where an environmental engineering manager needs to ensure that 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 (or her assistant) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Environment:

શેવાળ, 64 જરાક, virtual machine environment (development box), 2 servers (SQL on server #1, everything else on server #2).

Problems:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. તેમ છતાં, it does not work well out of the box (for us).

1. The workflow job was not scheduled to run, ever. I discovered this by reading through Christopher White’s (http://chrissyblanco.blogspot.com/2007/06/issues-with-delay-activity-in-moss.html) excellent write-up by using stsadm thusly:
   

   સી:\>stsadm -o getproperty -propertyname "job-workflow" -URL HTTP://localhost

   <Property Exist="No" />

   સી:\>

   That was a surprising result but easily solved:

   સી:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 વચ્ચે મિનિટ 0 અને 59" -URL HTTP://localhost

   ઓપરેશન સફળતાપૂર્વક સમાપ્ત.

   સી:\>

   કે કરી અપોન, the first "In Progress" વર્કફ્લો ઝડપથી ગોળીબાર કર્યો હતો અને તે કામ કર્યું.

2. દુર્ભાગ્યે, the next one didn’t work as expected. Thankfully, Christopher refers us અહીં (http://support.microsoft.com/kb/932816). As of writing of this entry, અમે તે હોટફિક્સ મેળવવા માટે આઇટી વિભાગ માટે રાહ જોઈ રહ્યા છો, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, તેથી આશા છે કે આ સમસ્યા હલ થશે.

ઉકેલ:

Re-running the stsadm -o setproperty command seemed to prod the workflow timer awake. It would, લગભગ 7 મિનિટ પછી, actually wake up and continue along with the workflow.

પ્રશ્નો / મુદ્દાઓ સંબોધવામાં:

તારીખ સુધી થોભો કામ કરતું નથી.

તારીખ સુધી થોભો ફરી શરૂ નથી.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"