Paul Galvin's (old) SharePoint space [SharePoint

Just another WordPress.com site

Problems with “Pause Until Date” activity in SPD-created workflows

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

Background:

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:

MOSS, 64 bit, 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.  However, 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:

    C:\>stsadm -o getproperty -propertyname "job-workflow" -url http://localhost

    <Property Exist="No" />

    C:\>

    That was a surprising result but easily solved:

    C:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 minutes between 0 and 59" -url http://localhost

    Operation completed successfully.

    C:\>

    Upon doing that, the first "In Progress" workflow quickly fired up and did it’s job.

  2. Sadly, the next one didn’t work as expected.  Thankfully, Christopher refers us here (http://support.microsoft.com/kb/932816).  As of writing of this entry, we’re waiting for the IT department to obtain that hotfix, but it does look promising.  Our copies of the affected .dll’s do not share the same byte size, so hopefully this will solve the problem.

Workaround:

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

Questions / Issues Addressed:

Pause Until Date does not work.

Pause Until Date does not resume.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"

Advertisements

2 responses to “Problems with “Pause Until Date” activity in SPD-created workflows

  1. Saurabh October 1, 2008 at 2:38 am

    Hi to all,      I am creating a reminder workflow using SharePoint Designer, and when I  use "Pause Until Date" activity. It doesn\’t resume and Workflow status does not change from "In Progress".(i.e. it displays "Pausing for 0 minutes" only, under Workflow History but it doesn\’t take any specified action).I have done some googling for that in last 4 days, and from there I had got a hot fix – KB 932394 and installed it but still I am in same trouble with “Pause Until Date” Activity.I have also changed “job-workflow” time duration using stsadm command from 5 minutes to 1 minute as below:
    stsadm -o setproperty -propertyname "job-workflow" -propertyvalue "every 1 minutes between 0 and 59" -url http://localhost
    but found same problem.What should I do for this? Please suggest me why "Pause Until Date" doesn\’t resume and Workflow status does not change from "In Progress" in my workflow.
    Thank you,
    Saurabh Kumar Singh

  2. Chris August 21, 2009 at 10:27 pm

    Hey Paul.. Dont know if you are monitoring or not. I am having the pause issue. I also have 3.5 sp1 which also install 3.0 sp2 framework. So when I try to run the hot fix, it is it can not find the product to update. I also have moss sp2 installed. Still getting the delay. I ripped off 3 and 3.5 framework and reinstall. Still getting the dealy…but it takes quite a few loops/waits before it occurs. Any other suggestions?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: