none
Cannot register SP2013 to a Workflow manager 1.0 server RRS feed

  • Question

  • I am trying to register workflow manager on my SP 2013 server.

    situation:

    we had workflow manager 1.0 installed on a server.  This server died and we don't have a backup of it (on purpose, it was not an important server).

    Also if I do a get-spsite I can see https://sp.domain.com/

    so I am not certain exactly what this error is referring too.

    Now I installed workflow manager 1.0 on a new server and setup a workflow farm.  I can access the workflow website on the http port from the sharepoint server just fine.  Also if I do a get-spsite

    PS C:\> Register-SPWorkflowService -SPSite "https://sp.domain.com/" -WorkflowHostUri "http://server-webapps:12291" -AllowOAuthHttp -Force
    Register-SPWorkflowService : The remote server returned an error: (404) Not
    Found.
    At line:1 char:1
    + Register-SPWorkflowService -SPSite "https://sp.domain.com/"
    -WorkflowHostUri "h ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ~~~
        + CategoryInfo          : InvalidData: (Microsoft.Share...WorkflowService:
       RegisterSPWorkflowService) [Register-SPWorkflowService], WebException
        + FullyQualifiedErrorId : Microsoft.SharePoint.WorkflowServices.PowerShell
       .RegisterSPWorkflowService

    Sunday, November 3, 2013 11:28 AM

Answers

  • We ended up installing it on another server and it worked out fine.

    We tried to upgrade to CU1 bur workflow manager wouldn't let me update../  All in all I spent a lot of time on nothing since

    Monday, November 4, 2013 5:45 PM

All replies

  • Hi,

    Use Web PI to install individually the following from Workflow Manager Server:

    • Service Bus 1.0 Cumulative Update 1 (This will require a reboot)

    • Workflow Manager 1.0 Cumulative Update 1

    Visit the below link for more information:

    http://blogs.msdn.com/b/workflowteam/archive/2013/03/03/cumulative-update-1-released-for-workflow-manager-1-0.aspx

    If the above cannot help, register the workflow using Register-SPWorkflowService with new scope by using the switch -scopename with force. Also, check the errors in the ULS logs.

    See the thread:

    http://social.msdn.microsoft.com/Forums/sharepoint/ro-RO/8fb130f1-94bf-442a-be50-9af2608c305c/sharepoint-2013-workflow-exception-scope-not-found?forum=sharepointadmin

    Thanks.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

    Monday, November 4, 2013 6:16 AM
    Moderator
  • We ended up installing it on another server and it worked out fine.

    We tried to upgrade to CU1 bur workflow manager wouldn't let me update../  All in all I spent a lot of time on nothing since

    Monday, November 4, 2013 5:45 PM
  • Hi Daniel,

    Is there any chance that one or both of the servers are using Windows Server 2012 R2? I'm having the same problem on a Server 2012 R2 box and I'm wondering if that might be the problem.

    Thanks

    Thursday, December 5, 2013 1:11 AM
  • Hum.  I am having this exact same issue.  My WF Manager 1.0 instance is also installed on a Windows 2012 R2 VM.  The SP Farm is all Windows 2012 (non R2) based.  I can browse to the WF manager status page no problem but I still get: Register-SPWorkflowService : The remote server returned an error: (404) Not Found.

    I guess I will spin up a Windows 2012 (Non R2) VM and install WF manager on that and see if it resolves the problem.  Did they make some sort of drastic change to IIS in R2?

    Thanks,-

    Matt

    Saturday, December 14, 2013 12:53 AM
  • Hum.  I am having this exact same issue.  My WF Manager 1.0 instance is also installed on a Windows 2012 R2 VM.  The SP Farm is all Windows 2012 (non R2) based.  I can browse to the WF manager status page no problem but I still get: Register-SPWorkflowService : The remote server returned an error: (404) Not Found.

    I guess I will spin up a Windows 2012 (Non R2) VM and install WF manager on that and see if it resolves the problem.  Did they make some sort of drastic change to IIS in R2?

    Thanks,-

    Matt

    Have you test it on your Windows 2012 (Non R2)? I have the same Problem on my R2 Server :(
    Wednesday, January 22, 2014 3:07 PM
  • I had the same exact problem. I could browse the config XML but could not run the WF to SP registration PowerShell command. It failed with the same exact error as above (The remote server returned an error: (404) Not Found.). I verified database/ server permissions, checked over IIS... everything I could think of. At this point I was certain there was some kind of incompatibility between my two servers. I didn't know if it was stemming from the Workflow Manger Server or the SharePoint 2013 Server (which is installed on Server 2012 R2). I can confirm (for those of you that were wondering from the last posts) that after installing WorkFlow Manager on a Server 2012 Standard (Non- R2) server, the Register-SPWorkFlowService command immediately succeeded.

    In talking with Microsoft about this, I was not able to get any information or support regarding this error because SharePoint 2013 is currently not supported on 2012 R2. It is now clear to me from this test that this error is not related to SP being installed on R2, but instead - WF Manager.

    In the end, it is still a mystery to me as to whether this issue will be resolved with SP1 for SharePoint 2013 because Workflow Manager and Service Bus Farm have different patching schemes.

    Hope this helps,

    John

    Wednesday, February 19, 2014 8:26 PM
  • The CU 2 of Workflow Manager 1.0 states that it supports Windows Server 2012 R2 : http://www.microsoft.com/en-us/download/details.aspx?id=42036

    Regards,
    -T.s


    Thuan Soldier
    A 23-year-old man loving Microsoft technologies and making crazy ideas on business journey.
    SharePoint Vietnam | Blog | Twitter


    • Edited by Thuan SoldierMVP Sunday, April 20, 2014 1:53 AM Update patch that supports Windows Server 2012 R2
    Saturday, April 19, 2014 4:26 AM