none
unexpected error on server associating the workflow

    Question

  • I have created a 2010 template workflow using sharepoint 2013 designer. below is the screenshot of it

    when I published the workflow it shows below error

    Please assist to solve this problem.

    Thursday, February 23, 2017 8:52 AM

All replies

  • Hi Revathy- could be a webconfig issue (see link below). But before you try that, I suggest you log each step of your workflow to see where it breaks down. Or, try simple workflows with each of your steps and see which one doesn't work.

    https://social.msdn.microsoft.com/Forums/sharepoint/en-US/a237e872-db7e-48fc-9d53-b438b55f0717/unexpected-error-on-server-associating-the-workflow?forum=sharepointcustomizationlegacy


    cameron rautmann

    Thursday, February 23, 2017 2:19 PM
  • Hi Revathy Raja,

    This problem is caused by the large number of Types that are created during workflow compilation, for workflows with many local workflow variables. It is more common for workflows with multiple Approval Process actions, as each preconfigured Approval Process Action comes with a large set of local variables, for the different configurable property of the Approval Process.

    For this issue, please do not add so many Start Approval Process actions in the single designer workflow.

    More information about resolutions, you could refer to the following article. It also applies to SharePoint Designer 2013.

    https://support.microsoft.com/en-us/kb/2557533

    Best regards,

    Linda Zhang


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Friday, February 24, 2017 6:52 AM
    Moderator
  • Hello,

    I'm using 2010 workflow template in 2013 environment.

    A simple workflow works fine. After including multiple options it started showing the error.

    Kindly assist.

    Thanks in advance,

    Revathy

    Tuesday, February 28, 2017 8:13 AM
  • Hi Revathy,

    Please do not add so many Start Approval Process actions in the single designer workflow.

    Some ways in which the complexity of larger workflows can be reduced include:

    • Use light weight workflow actions to replace Start Approval Process action, for instance, Start Custom Task Process action or Collect Data from a User.
    • Add new task process variables only as they’re needed.
    • When the task approvers (or task email) need to change based on conditions in the workflow, use a conditional block to save the task approver (or email contents) in a local variable and then use a single Approval Process action, rather than having a separate Approval Process actions with hardcoded approvers/email contents in each branch of the conditional block.
    • When using the small workflows approach, keep the second workflow into a paused state by using an action like Wait for Field Change. In the first workflow, once the Start Approval actions have been completed the workflow can modify a column which the second workflow is monitoring and then it will come out of the paused state and go on.

    For more information, please read this article.

    Best Regards,

    Linda Zhang


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Thursday, March 02, 2017 9:47 AM
    Moderator