I’m trying to register workflow supervisor with SharePoint 2013 and am working into the next error: (remark for response)
> Register-SPWorkflowService -site 'http://<web site assortment>/' -WorkflowHostUri "https://<workflow endpoint>:12290" -force 'Register-SPWorkflowService : The HTTP request has timed out after 200000 milliseconds.'
I’ve (presently) a three server construct (not together with area controllers):
- SharePoint 2013 on Home windows Server 2012 R2
- SQL 2012 on Home windows Server 2012 R2
- Workflow Supervisor 1.Zero Refresh on Home windows Server 2012 R2
The SharePoint web site assortment is over http; and the Workflow supervisor endpoint is https.
The certificates is put in within the SharePoint server and is added beneath “Handle Belief”
Workflow Supervisor was initially put in on the SharePoint server; nonetheless it was later determined that it needs to be rolled out by itself server. While it in all probability would have been a greater concept to simply depart the farms, then be part of them from the brand new server, I as a substitute utterly rebuilt the farms from scratch.
Workflow functions had been faraway from the SharePoint server:
- Workflow Supervisor 1.0
- Service Bus
- Home windows Material
(Workflow Supervisor Consumer 1.Zero was left on the server; model is 2.0.40131.0, which matches the model that finally ends up on the workflow supervisor server)
The databases had been dropped from the database server.
Workflow Supervisor 1.Zero Refresh was then put in on the WFM server, with a service account used because the “Run As” account. The remainder of the settings had been left as default.
It took some time, however the Configuration Wizard ran with no errors.
The Workflow and repair bus farm providers are working (I had a difficulty with these earlier, which I assumed might need been the trigger, however no…)
Nonetheless, when working the
Register-SPWorkflowService powershell cmdlet, I’m receiving the above error.
Working Fiddler on the time of registration exhibits the error happens when calling the URL /SharePoint/$Actions. This name hangs for a really very long time (for much longer than powershell is keen to attend for it) and ultimately returns 503 – Service Unavailable with the next message:
Ready 5 minutes and making an attempt once more has not remedied the issue.
Inspecting the Occasion go browsing the Workflow Supervisor server additionally exhibits the issue:
Right here it exhibits a name made to /$Actions (versus /SharePoint/$Actions) and is sending a message to /WF_Management scope.
I’ve not been capable of finding any extra details about this concern.
Can anybody establish what may be inflicting this timeout, and the way I might resolve this concern?