"The option for the SharePoint 2013 workflow platform is not available because the workflow service is not configured on the server."

You have configured SharePoint 2013 and Workflow Manager. You have created a new Site Collection. You’re unable to create SharePoint 2013 workflows (but SharePoint 2010 workflows works).

Problem: The site collection was created using the blank template, which doesn’t include all necessary dependency features for creating workflows.

Fix: You need to enable the hidden feature WorkflowServiceStore using PowerShell.

Enable-SPFeature -Identity WorkflowServiceStore –Url $yourUrl

 

Credit goes to Anuja Bhojani (blog) for finding this nugget.

8 thoughts on “"The option for the SharePoint 2013 workflow platform is not available because the workflow service is not configured on the server."”

  1. I found the solution
    Run registration command
    Register-SPWorkflowService -SPSite “http://servername/” -WorkflowHostUri “http://servername:12291/” -AllowOAuthHttp

  2. Had same issue, and ran the command you gave above, and power shell responded that the feature was already activated at that site.

    I would appreciate any other suggestions for a fix that someone may have.

  3. Hi,

    we have two servers one is application and front end server.i installed the workflow manager in app server,i checked the workflow service application proxy in services it is showing Workflow connected.
    when i tried to create the 2013 workflow i am not getting the option to select the 2013 workflow and it is showing following message.

    The option for the SharePoint 2013 workflow platform is not available because the workflow service is not configured on the server.

    Any one find the solution.

  4. In my case, I had used a BLANK site template to create my site. Took a long time to figure out that 2013 workflow was available on every other site in the collection, just not on my SPWeb that I provisioned with the BLANK site template. My guess is some hidden features are stapled to other templates, but not the blank template. I fixed my problem by deleting the SPWeb, creating a team site, deleting all the junk that comes with a team site. 2013 workflow in SPDesigner worked just fine after that.

    1. Ben, yeah you’re right. It’s the TaxonomyFieldAdded (ID 73ef14b1-13a9-416b-a9b5-ececa2b0604c) feature that needs to be activated, which is not stapled to the blank site definition.

  5. I encountered this same issue with sites created from the blank site template, and after running:

    Enable-SPFeature -Identity WorkflowServiceStore -Url “URLtoTheSiteThatDoesNotShowThe2013WorkFlowVIA_SharePointDesigner” -force

    the sites showed the 2013 workflow features via SP designer.

Leave a Reply

Your email address will not be published. Required fields are marked *