Workflow manager fail on install RRS feed

  • Question

  • Hey

    I have followed this article for install and configuration of Workflow manager:

    However. When I run the configuration, I get an error on the last step " Add host to manager workflow farm" that says:

    "configuration operation partially succeeded. use join and exsitsting farm to complete the configuration"
    The above makes no sense, since this is the first server in the farm.

    Also in the log the following error is present:

    Error] [02-02-2016 10:48:04]: System.Management.Automation.CmdletInvocationException: The remote server returned an error: (400) Bad Request. The api-version in the query string is not supported. Either remove it from the Uri or use one of '2012-03'..TrackingId:5fa0ccea-ed79-4584-b257-ac0ebdc5ed99_GS*******,TimeStamp:02-02-2016 09:48:04 ---> System.ArgumentException: The remote server returned an error: (400) Bad Request. The api-version in the query string is not supported. Either remove it from the Uri or use one of '2012-03'..TrackingId:5fa0ccea-ed79-4584-b257-ac0ebdc5ed99_GS******,TimeStamp:02-02-2016 09:48:04 ---> System.Net.WebException: The remote server returned an error: (400) Bad Request.
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at Microsoft.ServiceBus.Messaging.ServiceBusResourceOperations.GetAsyncResult`1.EndGetResponse(GetAsyncResult`1 thisPtr, IAsyncResult ar)
       at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)
       --- End of inner exception stack trace ---

    Server stack trace:

    Exception rethrown at [0]:
       at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
       at Microsoft.ServiceBus.NamespaceManager.OnEndTopicExists(IAsyncResult result)
       at Microsoft.Workflow.Deployment.Commands.WorkflowServiceConfigHelper.SetWFRuntimeSettings(String resourceDBConnectionString, String config)
       at Microsoft.Workflow.Deployment.Commands.AddWFHost.CallWFRuntimeSettings(Service wfserviceInfo, String unencryptedResourceConnectionString)
       --- End of inner exception stack trace ---
       at System.Management.Automation.Runspaces.AsyncResult.EndInvoke()
       at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
       at Microsoft.Workflow.Deployment.ConfigWizard.CommandletHelper.InvokePowershell(Command command, Action`3 updateProgress)
       at Microsoft.Workflow.Deployment.ConfigWizard.ProgressPageViewModel.AddWFNode(FarmCreationModel model, Boolean isFirstCommand)

    Any ideas?


    Tuesday, February 2, 2016 9:54 AM

All replies

  • By "last step" you mean "Register-SPWorkflowService"?
    Wednesday, February 3, 2016 9:10 PM
  • Which version of SB and WFM is installed? Seems like SB client compat issue. 
    Wednesday, February 3, 2016 9:55 PM
  • HI,

    To get the connection string to connect to Service Bus Server, you can run Get-SBClientConfigurationfrom Service Bus Powershell.

    There is a known issue if this service account is a member of too many AD Groups.This leads to the Windows token that is generated for authentication by ServiceBus to be too large. The workaround is to either reduce the AD membership for this service account, or try the configuration with a new service account.

    Deepesh Yevle -MCP MCTS MCITP ITIL

    Tuesday, February 9, 2016 11:06 PM
  • It seems the WorklfowManager and ServiceBus installed is incompatible.

    Try this:

    1- Uninstall WorkflowManager and Service Bus. (and restart the server)

    Now, through WebPlataformInstaller, install:

    2 - Workflow Manager 1.0 Refresh (CU2)

    3 - Service Bus 1.1 Azure Pack

    4 - Workflow Manager 1.0 CU3

    5 - And this KB3086798 

    Restart the server again and execute REGISTER-SPWORKFLOWSERVICE with -FORCE and try again.


    Thursday, March 10, 2016 11:10 AM