2

I am attempting to register workflow manager with SharePoint 2013 and am running into the following error: (comment for response)

> Register-SPWorkflowService -site 'http://<site collection>/' -WorkflowHostUri "https://<workflow endpoint>:12290" -force
 'Register-SPWorkflowService : The HTTP request has timed out after 200000 milliseconds.'

Register-SPWorkflowService returns HTTP request has timed out after 200000 milliseconds

I have (currently) a 3 server build (not including domain controllers):

  • SharePoint 2013 on Windows Server 2012 R2
  • SQL 2012 on Windows Server 2012 R2
  • Workflow Manager 1.0 Refresh on Windows Server 2012 R2

The SharePoint site collection is over http; and the Workflow manager endpoint is https.

The certificate is installed in the SharePoint server and is added under "Manage Trust"

Workflow Manager was initially installed on the SharePoint server; however it was later decided that it should be rolled out on its own server. Whilst it probably would have been a better idea to just leave the farms, then join them from the new server, I instead completely rebuilt the farms from scratch.

Workflow applications were removed from the SharePoint server:

  • Workflow Manager 1.0
  • Service Bus
  • Windows Fabric

(Workflow Manager Client 1.0 was left on the server; version is 2.0.40131.0, which matches the version that ends up on the workflow manager server)

The databases were dropped from the database server. Workflow Manager 1.0 Refresh was then installed on the WFM server, with a service account used as the "Run As" account. The rest of the settings were left as default.

It took a while, but the Configuration Wizard ran with no errors.

The Workflow and service bus farm services are running (I had an issue with these earlier, which I thought might have been the cause, but no...)

Workflow and Service Bus Farm Status: all services are running

However, when running the Register-SPWorkflowService powershell cmdlet, I am receiving the above error.

Running Fiddler at the time of registration shows the error occurs when calling the URL /SharePoint/$Activities. This call hangs for a very long time (much longer than powershell is willing to wait for it) and eventually returns 503 - Service Unavailable with the following message:

/SharePoint/$Activities: 503 Service Unavailable. The data or message layer is unavailable. Please retry after 300 seconds

Waiting five minutes and trying again has not remedied the problem.

Examining the Event log on the Workflow Manager server also shows the problem:

Microsoft-Workflow Operational Error: Could not successfully send message to scope '/WF_Management' despite multiple retries.

Here it shows a call made to /$Activities (as opposed to /SharePoint/$Activities) and is sending a message to /WF_Management scope.

I have not been able to find any more information about this issue.

Can anyone identify what might be causing this timeout, and how I could resolve this issue?

Improve this question
1
  • Dis you try to register it WITHOUT Fiddler running?
    – Slaven Semper
    Commented Dec 26, 2015 at 20:35

5 Answers 5

Reset to default
0

First make sure that UPS synchronization is working and check the workflow services as described in this link:

http://www.techrevmarrell.com/register-spworkflowservice-timing-out/

If all services are working and this issue still persists, remove the workflow manager configuration and don't forget to delete databases

SbGatewayDatabase
SbManagement
SbMessageContainer01
WFInstanceManagement
WFManagement
WFResourceAutomation

then reconfigure it again.

Improve this answer
1
  • 1
    Please quote main points of the article as links tend to go down.
    – Paul Strupeikis
    Commented Nov 30, 2015 at 16:14
0

Make sure you have the latest version of Workflow Manager and Workflow Manager Client installed (CU 3). These come with some database upgrade scripts which you need to run manually.

Improve this answer
0

I had the same issue when registering WFM on a SharePoint 2016 farm. My issue was that on Windows server 2016, the WFM farm wizard (powershell as well) is not granting the proper permissions to the WFM site. I had to grant them manually for the service account and the Domain Users after the WFM farm was created then it registered without issue. Hope that helps.

Improve this answer
0

Since your SharePoint web application/site is running HTTP you should/must run the Register-SPWorkflowService cmdlet with the –AllowOAuthHttp. I am a bit surprised though that you get a timeout. Usually you get this error message:

Failed to query the OAuth S2S metadata endpoint at URI ...

Because you already executed the Register-SPWorkflowService cmdlet before, you should add the -AllowOAuthHttp and -Force switches.

Improve this answer
0

I know this is late, but doing below fixed my issue. Since you have a Separate SharePoint Farm and Workflow Manager Farm, make sure of enabling the following ports before running the Register-SPWorkflowService command:

Make sure firewall is not blocking the following Ports

  • WorkFlow Manager Ports 12290 & 12291
  • Service Bus Ports:
  • HTTPS 9355
  • TCP 9354
  • Message Broker Port 9356
  • Internal Communication Port Range 9000 - 9004
  • AMQP 5671-5672

I think the "Message Broker" port is the most relevant since we have the event viewer error saying this clearly: enter image description here

These prerequisites may also help

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.