SharePoint 2013 Workflows


  1. Web platform installer: as per on APP1
  2. Ran script on app1
    # 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 ‘workflow farm password’ -Verbose;New-SBFarm -SBFarmDBConnectionString ‘Data Source=sp13db;Initial Catalog=PROD_Workflow_SbManagement;Integrated Security=True;Encrypt=False’ -InternalPortRangeStart 9000 -TcpPort 9354 -MessageBrokerPort 9356 -RunAsAccount ‘[email protected]’ -AdminGroup ‘DOMAIN\SP13 Workflow Service Bus Admins’ -GatewayDBConnectionString ‘Data Source=sp13db;Initial Catalog=PROD_Workflow_SbGateway;Integrated Security=True;Encrypt=False’ -CertificateAutoGenerationKey $SBCertificateAutoGenerationKey -MessageContainerDBConnectionString ‘Data Source=sp13db;Initial Catalog=PROD_Workflow_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 ‘workflow farm password’ -Verbose;New-WFFarm -WFFarmDBConnectionString ‘Data Source=sp13db;Initial Catalog=PROD_Workflow_WFManagement;Integrated Security=True;Encrypt=False’ -RunAsAccount ‘[email protected]’ -AdminGroup ‘DOMAIN\SP13 Workflow Admins’ -HttpsPort 12290 -HttpPort 12291 -InstanceDBConnectionString ‘Data Source=sp13db;Initial Catalog=PROD_Workflow_WFInstanceManagement;Integrated Security=True;Encrypt=False’ -ResourceDBConnectionString ‘Data Source=sp13db;Initial Catalog=PROD_Workflow_WFResourceManagement;Integrated Security=True;Encrypt=False’ -CertificateAutoGenerationKey $WFCertAutoGenerationKey -Verbose;

    # Add SB Host
    $SBRunAsPassword = ConvertTo-SecureString -AsPlainText -Force -String ‘AccountPassword’ -Verbose;

    Add-SBHost -SBFarmDBConnectionString ‘Data Source=sp13db;Initial Catalog=PROD_Workflow_SbManagement;Integrated Security=True;Encrypt=False’ -RunAsPassword $SBRunAsPassword -EnableFirewallRules $true -CertificateAutoGenerationKey $SBCertificateAutoGenerationKey -Verbose;

    # Create new SB Namespace
    New-SBNamespace -Name ‘WorkflowDefaultNamespace’ -AddressingScheme ‘Path’ -ManageUsers ‘[email protected]’,’[email protected]’,’[email protected]’ -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 ‘AccountPassword’ -Verbose;

    Add-WFHost -WFFarmDBConnectionString ‘Data Source=sp13db;Initial Catalog=PROD_Workflow_WFManagement;Integrated Security=True;Encrypt=False’ -RunAsPassword $WFRunAsPassword -EnableFirewallRules $true -SBClientConfiguration $SBClientConfiguration -CertificateAutoGenerationKey $WFCertAutoGenerationKey -Verbose;

  3. Installed workflow client on web1
  4. Exported workflow manager SSL cert from IIS
  5. Imported into trusted root cert authority on both WEB1 and APP1
  6. Installed into SharePoint trusted root
  7. New-SPTrustedRootAuthority -name “Workflow Manager” -Certificate “<file of exported workflow manager iis site cert>”
  8. Register-SPWorkflowService -SPSite “https://<site collection for workflows>” -WorkflowHostUri “https://<fqdn of workflow manager server>:12290”


Assisted by:



  • The list of workflow actions on the server references an assembly that does not exist. Some actions will not be available. The assembly strong name is {Actual Assembly strong name}. Contact your server administrator for more information.

    • Especially if assembly strong name is Microsoft.Activities; you need local administrator on the machine you’re using SharePoint Designer on, otherwise it cannot download the Workflow DLLs and install them in the local machine’s GAC in order to create the workflows using them. (as hinted to by
    • If you are a Local Admin, then it could be because custom actions have been added to the server, but not properly. See the rest of the stackoverflow question:

Geek, wanderluster, pochemuchka, wannabe-polyglot, photographer and UK-resident kiwi here for the travel.

Leave a Reply

Your email address will not be published. Required fields are marked *