Home > SharePoint 2013 > How to Fix “Error occurred in deployment step ‘Activate Features’: System.TimeoutException:”

How to Fix “Error occurred in deployment step ‘Activate Features’: System.TimeoutException:”

Problem:

When deploying a SharePoint2013 workflow using Visual Studio, I got the following Error:

Error occurred in deployment step ‘Activate Features’: System.TimeoutException: The HTTP request has timed out after 20000 milliseconds. —> System.Net.WebException: The request was aborted: The request was canceled.

at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)

at Microsoft.Workflow.Client.HttpGetResponseAsyncResult`1.OnGotResponse(IAsyncResult result)

— End of inner exception stack trace —

at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)

at Microsoft.Workflow.Client.Ht

Analysis:

After reading AC’s blogpost and I find out the issue is to do with the service bus. Then I found out the following services are not started


Solution:

So I start the Service Bus Gateway and Service Bus Message Broker and the problem goes away.

References:

SharePoint 2013 Workflow – Advanced Workflow Debugging with Fiddler

Advertisements
  1. March 24, 2013 at 10:06 pm

    I am getting the same exception, however both these services are also running, still issue is there, Any idea how to resolve this?

    • Lucas
      August 23, 2013 at 6:16 am

      I have the same problem (the services are already running), someone find the solution for this cenario?

    • October 20, 2014 at 7:31 pm

      Did you find a solution for this issue? I also have the same scenario.. The services are running, however getting the below mentioned error:

      Error 1 Error occurred in deployment step ‘Activate Features’: Microsoft.Workflow.Client.ActivityNotFoundException: The activity named ‘WorkflowXaml_27ef747f_7f9a_433a_9e58_14d9d8bf7484’ from scope ‘/SharePoint/default/03917f60-568a-4cba-be77-e0e074a73dce/e8e06602-c471-4fe8-b076-79d86bbca942’ was not found.
      HTTP headers received from the server – ActivityId: 5b2ebc7c-bc6f-4672-818f-71d35c0a0499. NodeId: MNM-DEV. Scope: /SharePoint/default/03917f60-568a-4cba-be77-e0e074a73dce/e8e06602-c471-4fe8-b076-79d86bbca942.
      Client ActivityId : 280903d7-5aae-4f40-a397-9
      0 0 HRLeaveApplicationWorkflow

  2. October 16, 2013 at 12:22 am

    sorted, thanks man. Started the services

  3. Srikanth
    December 19, 2013 at 8:34 pm

    That’s great. Saved my time. Thank you.

  4. August 27, 2014 at 1:52 am
  5. January 29, 2015 at 10:20 pm

    if that’s does not work restart Workflow Manager Backend Service by
    CMD command
    Net stop “Workflow Manager Backend”
    Net Start “Workflow Manager Backend”

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: