none
SharePoint 2010 OOB "Page Approval" Workflow Issue

    Question

  • Hi All,

    I've created some powershell scripts to deploy a large amount of SharePoint publishing sites with some base content. The scripts go through and edit web parts and configuration files to make sure every site is unique and working ok.

    The OOB Page Approval workflow was initially fine, content was being added to each of the sites and the approval process was working fine. All of a sudden we had a Managed Service Account get locked out for the database on that site collection. We resolved that issue (relevent or not) and have seen that since then none of the "page approval" workflows work on that site collection. (edit to add: all of the sites before this happened display the error - any new sites deployed work fine...)

    The error I get is:

    An error has occurred in Page Approval.
    The workflow operation failed because the workflow lookup found no matching item.

    Interestingly enough, any sites I have deployed since using the same scripts and so forth (even subsites of the error ridden sites) work fine and the publishing workflow operates normally.


    So far i've tried:

    Disabling & Re-enabling the OOB Page Approval workflow feature
    Disabling & Re-enabling the Publishing Features (both at site and site collection level)

    I tried copying and modifying the Page Approval workflow and hit an issue where the "workflow list did not exist" -
    After editing the lookups in my xoml file and pointing them specifically to the list in question I resolved this but encountered the same issue on that workflow.

     

    Any Ideas I may have missed would be very usefull - scratching my head now..

     

    Thanks,
    Ryan

     

     


    Drummer.. Oh and SharePoint Developer & Consultant http://spdrummerboy.blogspot.com
    Monday, February 06, 2012 3:07 PM

Answers

  • Managed to resolve this issue by deleting all of the Timer Job job-workflow tasks for those sites and resetting the timerjob.
    All of the workflows are now processing as normal.

    R


    Drummer.. Oh and SharePoint Developer & Consultant http://spdrummerboy.blogspot.com

    • Marked as answer by Ryan Mathieson Tuesday, February 07, 2012 1:42 PM
    Tuesday, February 07, 2012 1:41 PM

All replies

  • Must say it is a curious issue.

    I remember one of my customer had a similar problem but with a custom workflow. And we had to remove the WF and readd it. The learning we got was that Workflow upgrade isnt that clean and needs all instances to be completed (Status Field) before you upgrade to new version of Workflow.

    Hpe this helps you.


    Varun Malhotra

    • Marked as answer by Ryan Mathieson Tuesday, February 07, 2012 1:41 PM
    • Unmarked as answer by Ryan Mathieson Tuesday, February 07, 2012 1:41 PM
    Tuesday, February 07, 2012 1:30 AM
  • Managed to resolve this issue by deleting all of the Timer Job job-workflow tasks for those sites and resetting the timerjob.
    All of the workflows are now processing as normal.

    R


    Drummer.. Oh and SharePoint Developer & Consultant http://spdrummerboy.blogspot.com

    • Marked as answer by Ryan Mathieson Tuesday, February 07, 2012 1:42 PM
    Tuesday, February 07, 2012 1:41 PM
  • Managed to resolve this issue by deleting all of the Timer Job job-workflow tasks for those sites and resetting the timerjob.
    All of the workflows are now processing as normal.

    R


    Drummer.. Oh and SharePoint Developer & Consultant http://spdrummerboy.blogspot.com


    Ryan, sorry to bring up old issue. I am encountering the exact same problem. Could you please explain the step to delete timer job and reset timer job?
    Wednesday, May 06, 2015 2:00 AM