1) Logged in as me(Sukesh Dash) Local Admin and also Sys Admin in SQL 2) Created a Domain account(ds\ DEV_SP_FarmWF) as Workflow RunAs account 3) Allocated Workflow run as account as Sys admin in SQL server Following is the recommendation from Microsoft https://msdn.microsoft.com/en-us/library/jj193478.aspx Helpful videos and resources https://www.youtube.com/watch?v=6haTejk98hU http://www.slideshare.net/roykimtoronto/development-server- workflow-manager-10-setup-reference Troubleshooting blogs:
Transcript
1) Logged in as me(Sukesh Dash)
Local Admin and also Sys Admin in SQL
2) Created a Domain account(ds\ DEV_SP_FarmWF) as Workflow RunAs account
3) Allocated Workflow run as account as Sys admin in SQL server
App Management service should be provisioned and running
System Requirements (Workflow Manager 1.0)
Updated: October 22, 2012This document describes the requirements for installing and configuring Workflow Manager 1.0.SQL ServerThe SQL Server instance that is used for various databases configured as a part of Workflow Manager must meet the following requirements.
TCP/IP, shared memory, or named pipes must be enabled.
Port 1443 on the firewall must be open to inbound and outbound communications.
If named pipes are used, the name of the machine on which the SQL Server instance is running should have a name with no more than 16 characters. Named pipes use NetBIOS names, which carry that restriction.
If TCP/IP connections are used, the SQL Browser service should be running on the SQL server.
SQL Server service should be running on the SQL server.
The following collation types are supported.
o Default Collation
o SP Collation
o Binary Collation
Supported Authentication
1. Integrated Authentication
2. SQL Authentication
Current User(Sukesh Dash)The user that is configuring Workflow Manager must meet following requirements.
If the machine is domain joined, the user must be a domain user; otherwise the user must be a local user.
The user must be an administrator on the computer on which the configuration is running.
The user must have SysAdmin privilege on this SQL Server instance, otherwise, the databases should be pre-created and the Sql logon for the RunAs Account User should be created manually, before running the configuration, on all Sql instances.
RunAs Account User(ds\ DEV_SP_FarmWF)The RunAs account is provided during Workflow Manager configuration and is used as the RunAs account by the Workflow Manager services. The Workflow Manager supports the ability to have the RunAs account user as a domain user or a local user. In both cases, this user must have access to the SQL Server instances. Alternatively, SQL Server databases can be accessed using SQL Authentication.The RunAs account user will be granted a log on as a service privilege during configuration.If all the machines in a farm share the same service account and the security policy requires the service account password to be changed at regular intervals, you must perform specific actions on each machine in the farm to be able to continue adding and removing nodes in the farm. See the section titled Handling Service Password Changes for this procedure.
Workflow Manager does not support built-in accounts (for example, NETWORK SERVICE) as RunAs accounts.
The following blog says and confirms to install newer Service Bus 1.1 and Workflow Manager refresh(which is itself workflow manager with CU2)
When using the Web Platform Installer to download and/or install Workflow Manager you can no longer download and install Workflow Manager 1.0 and Workflow Manager 1.0 CU1. The only option is to download Workflow Manager 1.0 Refresh (which essentially is CU2). So when installing a new Workflow Manager farm for SharePoint or just because you want to rock some workflows you have to use Workflow Manager (WFM) 1.0 Refresh. Unless you’ve been smart and previously downloaded and saved the original Workflow Manager. When using WFM 1.0 Refresh you also need to download Service Bus 1.1.
Sharepoint 2013 Workflow in Designer(This ends up in error while publishing)
System.InvalidOperationException: Operation failed with error Microsoft.Workflow.Client.WorkflowCommunicationException: The request was aborted: The request was canceled. Client ActivityId : 5d1d399d-2e07-60ea-8482-87723fa60e4d. ---> System.Net.WebException: The request was aborted: The request was canceled. ---> System.ServiceModel.ServiceActivationException: The requested service, 'net.pipe://localhost/SecurityTokenServiceApplication/appsts.svc' could not be activated. See the server's diagnos
Resolution
This is not a recommended approach to install Workflow Manager only on WFE however I observed APP server was quite restrictive in terms of accepting Workflow manager requests(Firewall and Network level adjustments were necessary)
It came to my notice earlier when I tried to join the Workflow Farm that I created in App server from WFE and it was declined.
Thus I completely uninstalled every trace of Workflow from APP server and reinstalled Workflow Farm in WFE servers and also have joined the other WFE to the Farm.
After configuring the farm in WFE ,resetting IIS and clearing Designer cache I am finally able to Publish a 2013 Workflow.
