locked
Deregister and register workflow management in SharePoint 2013 RRS feed

  • Question

  • I just installed workflow management.

    All my sites are located under http://spse/sites

    I tried to configure it using this command: Register-SPWorkflowService -SPSite "http://spse/sites" -WorkflowHostUri "http://spse:12291" –AllowOAuthHttp

    This failed. Why?

    So I use the same command pointing to one of the site: Register-SPWorkflowService -SPSite "http://spse/sites/demo" -WorkflowHostUri "http://spse:12291" –AllowOAuthHttp

    This succeeded.

    I tried to register another site: Register-SPWorkflowService -SPSite "http://spse/sites/demo2" -WorkflowHostUri "http://spse:12291" –AllowOAuthHttp

    That failed. I am getting the following error: Register-SPWorkflowService : Failed to register because the farm or partition is already registered with a workflow service

    So I have two issues to resolve:

    How to unregister http://spse/sites/demo

    How to register all the sites I have under http://spse/sites

    Tuesday, January 14, 2014 1:06 AM

Answers

  • Given both Demo and Demo2 site collections are in the same web applications you do not need to register your workflow service again. 

    Basically the idea is you register the workflow service once by providing one site collection as an argument and that service will be available for all site collections in that particular web application.

    If you have other web applications and they are using default service application association group then you will have your workflow service available for those web application as well.

    So to answer you question.

    1) You do not need to unregister your workflow service.

    2) As mentioned above you do no need to register workflow service again

    a) They are under the same web application

    b) Using the default service application association even on the different web application.


    Amit

    • Marked as answer by MAS Services Tuesday, January 14, 2014 4:58 PM
    Tuesday, January 14, 2014 10:47 AM

All replies

  • Given both Demo and Demo2 site collections are in the same web applications you do not need to register your workflow service again. 

    Basically the idea is you register the workflow service once by providing one site collection as an argument and that service will be available for all site collections in that particular web application.

    If you have other web applications and they are using default service application association group then you will have your workflow service available for those web application as well.

    So to answer you question.

    1) You do not need to unregister your workflow service.

    2) As mentioned above you do no need to register workflow service again

    a) They are under the same web application

    b) Using the default service application association even on the different web application.


    Amit

    • Marked as answer by MAS Services Tuesday, January 14, 2014 4:58 PM
    Tuesday, January 14, 2014 10:47 AM
  • Thanks Amit
    Tuesday, January 14, 2014 4:59 PM
  • I have found that this is not the case for me, I registered the workflow service against my root site collection. //servername however my live site collections reside here //servername/sites

    I have a separate site collection per department so for instance //servername/sites/IT //servername/sites/HR etc

    If I open the site //servername/ in SP designer I can see that 2013 workflow is available if I open //servername/sites/IT in SP designer I get the error that the workflow service is not configured.  All Site collections are under the same Web Application.

    Please help its driving me crazy! I would be happy to go back a register //servername/sites but as it is already registered once I cant do this hence me looking to "de-register"

    Tuesday, April 8, 2014 4:38 PM
  • Ditto here.  I have multiple web applications and they are all using the default service application group with the workflow proxy checked. I registered the workflow service with the main web application. Designer always sees 2013 workflows for that web application, and sometimes it shows up and sometimes not with the other web applications.
    • Proposed as answer by Louis7711 Tuesday, September 29, 2015 1:52 PM
    • Unproposed as answer by Louis7711 Tuesday, September 29, 2015 1:52 PM
    Thursday, June 5, 2014 6:30 PM
  • Good day all

    I ran into the same problem, where my Workflow Server crashed and could not be recovered.

    This is what i did to resolve the issue.

    I reinstalled the workflow server with a new name.

    Reinstalled workflow manager on the new server

    When i wanted to join the SharePoint server to the new Workflow server i got the error that stated that the SharePoint farm is already registred with a Workflow service.

    What i did then was i deleted the Workflow Service Application using Central Administration

    Ran Iisreset

    Then i tried to run the Register-SPWorkflowservice command again, this time i received another error that stated that there is already a scope called SharePoint.

    I reran the command but this time i added - force at the end.

    See example below.

    After that everything worked like a charm.

    Register-SPWorkflowService -SPSite "https://myserver/mysitecollection" -WorkflowHostUri "https://workflow.example.com:12290" -force

    Regards

    Louis

    Tuesday, September 29, 2015 2:00 PM