While working on a new environment I built a dedicated server to run the new Windows Azure Workflow components. All went well with except when I got to the part where you run the PowerShell on the SharePoint 2013 server I hit a problem.
Register-SPWorkflowService –SPSite “http://{sitecollectionurl}” –WorkflowHostUri “http://{workflowserve}:12290″ –AllowOAuthHttp
This was the error:
For easier reading here is the message:
“Register-SPWorkflow : Could not load file or assembly
‘Microsoft.Workflow.Client, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35′ or one of its dependencies. The system cannot find the file specificed.
At line:1 char:1″
After trawling the internet and coming back with nothing, I rechecked the installation instructions found here. In this article there is a little section that I am sure you have all read that states the following:
Caution
You must run the Register-SPWorkflowService cmdlet on a computer that is running SharePoint Server. For the cmdlet to run successfully, either Windows Azure Workflow or the Workflow Client SDK must be installed on the SharePoint Server computer on which the cmdlet is run.
Notice it states that you either need “Windows Azure Workflow or the Workflow Client SDK” installed to actually run the command. So I went straight to the internet to find the “Workflow Client SDK” but could not find anything. So my next though was let me run the installer for the full-blown workflow services and see what it offers. So I downloaded the following: http://go.microsoft.com/fwlink/?LinkID=252092. I then ran the executable “workflow.3f.3f.3fnew.exe” and there was my answer.
As I did not want to install everything I clicked the direct link and downloaded just that one link that I needed that I could not find anywhere. In case you need it here it is: http://go.microsoft.com/fwlink/?LinkID=251617&CLCID=0×409. And now my command run perfectly and I have a dedicated workflow server. To check if your SharePoint Server is now connected to the Workflow Service access Central Administration, Application Management, and Manage Service Applications. You should now see a new Proxy added, called the “App Fabric Application Proxy” which if you see the type is set to “Workflow Services Application Proxy”.
When clicking on this it should say you are connected.
In my environment I have it configured to work over SSL, so accessing the service URL is done over SSL and when running the PowerShell command you use the SSL address instead.
Register-SPWorkflowService –SPSite “http://{sitecollectionurl}” –WorkflowHostUri “https://{workflowserve}:12290″ –AllowOAuthHttp
Hope this helps anyone else who is also running the Workflow Services on a different server.
This article was originally posted here, on the Liam Cleary blog.
Thanks! This probably solved an issue we had getting the connection from SP 2013 to Azure Workflow to work. (Interesting how you blacked out the hostname in the address bar but not on the tab in the screen shot though :) )