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:
- Start \ Programs \ Workflow Manager 1.0 \ Workflow Manager Configuration \ Remove from Farm (not to be confused with SharePoint “farm”)
- Drop SQL databases for Workflow Manager. (SbGatewayDatabase, SbManagementDB, SBMessageContainer01, WFInstanceManagementDB, WFManagementDB, WFResourceManagementDB)
- Start \ Programs \ Workflow Manager 1.0 \ Workflow Manager Configuration \ Configure Workflow Manager with Default Settings (Recommended)
- Two things I did differently on the next pass:
- 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.
- 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.
- 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.
- 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
=========================================================================
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
=========================================================================
# To be run in Workflow Manager PowerShell console that has both Workflow Manager and Service Bus installed.
# Create new SB Farm
$SBCertificateAutoGenerationKey = ConvertTo-SecureString -AsPlainText -Force -String '***** Replace with Service Bus Certificate Auto-generation key ******' -Verbose;
New-SBFarm -SBFarmDBConnectionString 'Data Source=SP15.demo.com;Initial Catalog=SbManagementDB;Integrated Security=True;Encrypt=False' -InternalPortRangeStart 9000 -TcpPort 9354 -MessageBrokerPort 9356 -RunAsAccount 'spfarm@DEMO' -AdminGroup 'BUILTIN\Administrators' -GatewayDBConnectionString 'Data Source=SP15.demo.com;Initial Catalog=SbGatewayDatabase;Integrated Security=True;Encrypt=False' -CertificateAutoGenerationKey $SBCertificateAutoGenerationKey -MessageContainerDBConnectionString 'Data Source=SP15.demo.com;Initial Catalog=SBMessageContainer01;Integrated Security=True;Encrypt=False' -Verbose;
# To be run in Workflow Manager PowerShell console that has both Workflow Manager and Service Bus installed.
# Create new WF Farm
$WFCertAutoGenerationKey = ConvertTo-SecureString -AsPlainText -Force -String '***** Replace with Workflow Manager Certificate Auto-generation key ******' -Verbose;
New-WFFarm -WFFarmDBConnectionString 'Data Source=SP15.demo.com;Initial Catalog=WFManagementDB;Integrated Security=True;Encrypt=False' -RunAsAccount 'spfarm@DEMO' -AdminGroup 'BUILTIN\Administrators' -HttpsPort 12290 -HttpPort 12291 -InstanceDBConnectionString 'Data Source=SP15.demo.com;Initial Catalog=WFInstanceManagementDB;Integrated Security=True;Encrypt=False' -ResourceDBConnectionString 'Data Source=SP15.demo.com;Initial Catalog=WFResourceManagementDB;Integrated Security=True;Encrypt=False' -CertificateAutoGenerationKey $WFCertAutoGenerationKey -Verbose;
# Add SB Host $SBRunAsPassword = ConvertTo-SecureString -AsPlainText -Force -String '***** Replace with RunAs Password for Service Bus ******' -Verbose;
Add-SBHost -SBFarmDBConnectionString 'Data Source=SP15.demo.com;Initial Catalog=SbManagementDB;Integrated Security=True;Encrypt=False' -RunAsPassword $SBRunAsPassword -EnableFirewallRules $true -CertificateAutoGenerationKey $SBCertificateAutoGenerationKey -Verbose;
Try {
# Create new SB Namespace New-SBNamespace -Name 'WorkflowDefaultNamespace' -AddressingScheme 'Path' -ManageUsers 'spfarm@DEMO','spfarm@DEMO' -Verbose;
Start-Sleep -s 90
} Catch [system.InvalidOperationException] { }
# Get SB Client Configuration
$SBClientConfiguration = Get-SBClientConfiguration -Namespaces 'WorkflowDefaultNamespace' -Verbose;
# Add WF Host $WFRunAsPassword = ConvertTo-SecureString -AsPlainText -Force -String '***** Replace with RunAs Password for Workflow Manager ******' -Verbose;
Add-WFHost -WFFarmDBConnectionString 'Data Source=SP15.demo.com;Initial Catalog=WFManagementDB;Integrated Security=True;Encrypt=False' -RunAsPassword $WFRunAsPassword -EnableFirewallRules $true -SBClientConfiguration $SBClientConfiguration -CertificateAutoGenerationKey $WFCertAutoGenerationKey -Verbose;
=========================================================================
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…
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.
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 https://www.spjeff.com/2013/01/03/two-ways-to-check-sql-aliases-for-sharepoint/
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.
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.
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
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!
Configuration operation partially succeeded. Use ‘Join an Existing Farm’ to complete the configuration. What you have done after this.