SharePoint, Office 365, Azure, and Front end JS geek. – Chicago IL
SharePoint, Office 365, Azure, and Front end JS geek. – Chicago IL

Configuring Workflow Manager 1.0 on SharePoint 2013 (screenshots)

During my first attempt to enable Workflow Manager 1.0 on a local VM I ran into the following error:

—> System.InvalidOperationException: Program C:\Program Files\Windows Fabric\bin\Fabric\Fabric.Code.1.0\FabricDeployer.exe exited with error: Windows Fabric deployment failed.DeploymentValidator: warning: The Fabric Data Collection Agent is disabled for this deployment.
None of the declared nodes is for the current machine.

The steps I took to resolve were:

  1. Start \ Programs \ Workflow Manager 1.0 \ Workflow Manager Configuration \ Remove from Farm     (not to be confused with SharePoint “farm”)
  2. Drop SQL databases for Workflow Manager.   (SbGatewayDatabase, SbManagementDB, SBMessageContainer01, WFInstanceManagementDB, WFManagementDB, WFResourceManagementDB)
  3. Start \ Programs \ Workflow Manager 1.0 \ Workflow Manager Configuration \ Configure Workflow Manager with Default Settings (Recommended)
  4. Two things I did differently on the next pass: 
    1. I used the SQL alias “SPSQL” instead of the FQDN machine names.   I’m using that for SharePoint and prefer SQL aliases for management flexibility.
    2. I formatted the user name as “DEMO\SPFARM” instead of “SPFARM@DEMO” (default text value).   That seems to make more sense for AD login credentials and I didn’t understand why the default was more of an email syntax.
    3. I commented out all of the HOSTS file entries.  While this may not be related, I wanted to simplify the connections as much as possible.   I had “127.0.0.1” entries for the local machine to ensure connectivity even as a change VM host network settings, but removed while running the WF configuration wizard.
  5. Ran the wizard just like before and it completed successfully this time.

 

Now I can continue the steps outlined at http://technet.microsoft.com/en-us/library/jj658588(v=office.15) and run the PowerShell cmdlet Register-SPWorkflowService

 

image
image
image
image
image
image
image
image
image
image
image
image
image
image
image
image
image
image
image
image

 

 

=========================================================================

Configuration for Workflow Manager
Management Database SQL Instance    SP15.demo.com
Enable SSL connection with SQL Server instance    False
Authentication    Windows Authentication
Management Database Name    WFManagementDB
Instance Management Database SQL Instance    SP15.demo.com
Enable SSL connection with SQL Server instance    False
Authentication    Windows Authentication
Instance Management Database Name    WFInstanceManagementDB
Resource Management Database SQL Instance    SP15.demo.com
Enable SSL connection with SQL Server instance    False
Authentication    Windows Authentication
Resource Management Database Name    WFResourceManagementDB
RunAs Account    spfarm@DEMO
RunAs Password    ***********
Certificate Generation Key    ***********
Workflow Manager Outbound Signing Certificate    Auto-generated
Service SSL Certificate    Auto-generated
Encryption Certificate    Auto-generated
Workflow Manager Management Port    12290
HTTP Port    Disabled
Enable firewall rules on this computer    True
Administrators Group    BUILTIN\Administrators
Configuration for Service Bus
Management Database SQL Instance    SP15.demo.com
Enable SSL connection with SQL Server instance    False
Authentication    Windows Authentication
Management Database Name    SbManagementDB
Gateway Database SQL Instance    SP15.demo.com
Enable SSL connection with SQL Server instance    False
Authentication    Windows Authentication
Gateway Database Name    SbGatewayDatabase
Message Container SQL Instance    SP15.demo.com
Enable SSL connection with SQL Server instance    False
Authentication    Windows Authentication
Message Container Database Name    SBMessageContainer01
RunAs Account    spfarm@DEMO
RunAs Password    ***********
Certificate Generation Key    ***********
Farm Certificate    Auto-generated
Encryption Certificate    Auto-generated
HTTPS Port    9355
TCP Port    9354
Message Broker Port    9356
Internal Communication Port Range    9000 – 9004
Enable firewall rules on this computer    True
Administrators Group    BUILTIN\Administrators

 

=========================================================================

=========================================================================

Configuration operation partially succeeded.  Use ‘Join an Existing farm’ to complete the configuration.

[Error] [3/27/2013 9:53:08 AM]: System.Management.Automation.CmdletInvocationException: Program C:\Program Files\Windows Fabric\bin\Fabric\Fabric.Code.1.0\FabricDeployer.exe exited with error: Windows Fabric deployment failed.DeploymentValidator: warning: The Fabric Data Collection Agent is disabled for this deployment.
None of the declared nodes is for the current machine.

—> System.InvalidOperationException: Program C:\Program Files\Windows Fabric\bin\Fabric\Fabric.Code.1.0\FabricDeployer.exe exited with error: Windows Fabric deployment failed.DeploymentValidator: warning: The Fabric Data Collection Agent is disabled for this deployment.
None of the declared nodes is for the current machine.

 

   at Microsoft.ServiceBus.Commands.Common.ProcessHelper.RunCommandInProcess(String exeName, String arguments, String errorString)
   at Microsoft.ServiceBus.Commands.AddSBHost.ProcessRecordImplementation()
   at Microsoft.ServiceBus.Commands.ServiceBusBaseCmdlet.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
   — End of inner exception stack trace —
   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.AddSBNode(FarmCreationModel model, Boolean isFirstCommand)

=========================================================================

Starting
Validating input and configuration parameters.
Installing auto-generated certificate.
Granting ‘Log on as Service’ privilege to the run as account.
Windows Fabric configuration started.
Running Windows Fabric deployment.
Program C:\Program Files\Windows Fabric\bin\Fabric\Fabric.Code.1.0\FabricDeployer.exe exited with error: Windows Fabric deployment failed.DeploymentValidator: warning: The Fabric Data Collection Agent is disabled for this deployment.
None of the declared nodes is for the current machine.

  • Great guide. It solved my identical problem. I found that all you really need is to comment out all of your 127.0.0.1 references in the HOST-file. It doesn’t matter if you use SPWAW@domain.local or domainSPWAW…

  • Daniel Christian

    Thanks for posting this guide. In my case, I left the ‘Enable firewall rules on this computer’ unchecked and was able to get through the entire installation successfully.

  • chow

    How to update a failover Database server to the existing Workflow Manager Database.. any idea on this??

    • Hi Chow,

      Great question. I personally like to use local SQL alias for ALL database connections. This way, Workflow Manager only “knows” about the alias (ex: “SPSQL” which points at “SQLREALNAME”) then I can update the alias for any SQL upgrade, failover, etc.

      More details at http://www.spjeff.com/2013/01/03/two-ways-to-check-sql-aliases-for-sharepoint/

      • chow

        Hi, Thanks for the reply
        could you please explain in detail.. we have nearly 40 content db’s including 3 for workflow manager. i can able to update all the db’s to a failover alias server by using PowerShell and through Central Admin except the Workflow manager db’s.. i searched for this a lot, but couldn’t able to find a solution.
        you mean to say that if I update the alias server in cliconfg.exe, that is enough no need to update any individual db’s??
        Thanks,

        • Great question. I see 3 ways to approach this. You’ll need to decide which fits best on your farm.

          1) Create a SQL alias (ex: “SPSQL”) before configuring SharePoint. When creating databases, always specify “SPSQL” as the destination server. This way SharePoint only knows about “SPSQL” from day one.

          2) Create a SQL alias (ex: “SPSQL”) and update all connection strings to point here. This would require modifying your current configs with Central Admin and PowerShell. Replace old reference with new alias.

          3) Create a SQL alias based identical to the current server name (ex: “SQLSRV01”) and point at IP address. Hybrid approach best of both worlds. You skip the config work in #2 and simply make an alias with the current server names so you can point at today’s IP address or a future different one.

          Hope that helps.

          • chow

            Hi, Thanks
            DB team gave SQL Alias(ex: “SPSQL”)and I updated all the content DB’s to failover alias SPSQL, some using central admin and for service application DB’s using PoerShell except WOrkflow Manager DBs
            is there any way like PoerShell or through Central admin or any other way that i can point the existing Workflow manager db’s to failover alias SPSQL. any help in this would be a great favour.
            thanks.

  • Pingback: Installing Workflow Manager. | Luis Valencia - Sharepoint Architect()

  • Prem

    Hi,
    Can you please let me know what happens to Workflow history when we re-install the Workflow Manager on the server farm? We have few InfoPath Farms and workflows in our SP2013 server.
    Could you please point me to any Detailed un-install steps for Workflow Manager, WFM Cleint and ServiceBus 1.0.

    Best Regards,
    Prem

  • Pingback: ​INSTALLING WORKFLOW MANAGER « Luis Valencia - Sharepoint Architect()

  • Step 4.C helped me to solve “Windows Fabric deployment failed.DeploymentValidator: warning: The Fabric Data Collection Agent is disabled for this deployment.” error. Thank you!

  • Pingback: Configuring Workflow Manager 1.0 on SharePoint 2013 (screenshots) | @SPJeff - Kênh công nghệ 360()

  • Bahrain Moss 2007

    Configuration operation partially succeeded. Use ‘Join an Existing Farm’ to complete the configuration. What you have done after this.

© Copyright 2016
@ SPJeff

Return to Top ▲Return to Top ▲