Skip to content

Could not successfully create management Service Bus entity ‘WF_Management/WFTOPIC’ with multiple retries within timespan of …

July 30, 2012

To enable SharePoint 2013 workflows on SharePoint 2013, the Windows Azure Workflow Installer must be downloaded and the Workflow component must be installed. After successful installation, the Windows Azure Workflow Configuration Wizard needs to be run to set up the workflow engine, but it may fail with the following exception:

System.Management.Automation.CmdletInvocationException: Could not successfully create management Service Bus entity ‘WF_Management/WFTOPIC’ with multiple retries within timespan of 00:02:05.6894775. —> System.TimeoutException: Could not successfully create management Service Bus entity ‘WF_Management/WFTOPIC’ with multiple retries within timespan of 00:02:05.6894775. —> System.UnauthorizedAccessException: The remote server returned an error: (401) Unauthorized. Authorization failed for specified action: Manage..TrackingId:511deade-c3a6-4393-a08f-816b15fb826a,TimeStamp:7/30/2012 8:54:59 AM —> System.Net.WebException: The remote server returned an error: (401) Unauthorized.

There are two things to check here:

First, make sure that the service account that you specified in the begining of the wizard is a Local Administrator on your server and member of the sysadmin Server Role on the SQL Server.

Second, make sure that you specified the service account with the FQDN domain name (like user@domain.com, and not just user@domain)

To resolve the error, you will need to

  1. run the Workflow Configuration wizard lo leave the farm
  2. delete the following databases on the SQL Server
    • SbGatewayDatabase
    • SbManagementDB
    • SBMessageContainer01
    • WFInstanceManagementDB
    • WFManagementDB
    • WFResourceManagementDB
  3. run the Workflow Configuration wizard to create a new farm. (make sure you use the full domain name for the Service Account)

The complete error message:

Processing completed
Validating input and configuration parameters.
Installing auto generated certificate.
Granting ‘Log on as Service’ privilege to the run as account.
Workflow configuration starting.
Configuring workflow runtime settings.
System.Management.Automation.CmdletInvocationException: Could not successfully create management Service Bus entity ‘WF_Management/WFTOPIC’ with multiple retries within timespan of 00:02:05.6894775. —> System.TimeoutException: Could not successfully create management Service Bus entity ‘WF_Management/WFTOPIC’ with multiple retries within timespan of 00:02:05.6894775. —> System.UnauthorizedAccessException: The remote server returned an error: (401) Unauthorized. Authorization failed for specified action: Manage..TrackingId:511deade-c3a6-4393-a08f-816b15fb826a,TimeStamp:7/30/2012 8:54:59 AM —> System.Net.WebException: The remote server returned an error: (401) Unauthorized.
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at Microsoft.ServiceBus.Messaging.ServiceBusResourceOperations.CreateOrUpdateAsyncResult`1.EndGetResponse(CreateOrUpdateAsyncResult`1 thisPtr, IAsyncResult ar)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)
— End of inner exception stack trace —

Server stack trace:

Exception rethrown at [0]:
at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.ServiceBus.NamespaceManager.CreateOrUpdateTopicAsyncResult.CreateDescription(CreateOrUpdateTopicAsyncResult thisPtr, IAsyncResult r)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)

Exception rethrown at [1]:
at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Management.ManagementEntitiesCreator.CreateManagementEntitiesAsyncResult.EndCreateTopic(IAsyncResult result)
at Microsoft.Workflow.Common.BackoffRetryAsyncResult.IsolateWithRetry(IAsyncResult result)
— End of inner exception stack trace —
at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Administration.ServiceUpdateManager.CreateManagementEntities(IList`1 namespaceManagerUris, ServiceBusClientCredentialType clientCredentialType, IDictionary`2 arguments, TimeSpan retryTimeout)
at Microsoft.Workflow.Deployment.Commands.WorkflowServiceConfigHelper.SetWFRuntimeSettings(String resourceDBConnectionString, String config)
at Microsoft.Workflow.Deployment.Commands.AddWFHost.CallWFRuntimeSettings(Service wfserviceInfo)
— End of inner exception stack trace —
at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Workflow.Deployment.ConfigWizard.CommandletHelper.InvokePowershell(Command command, Action`2 updateProgress)
at Microsoft.Workflow.Deployment.ConfigWizard.ProgressPageViewModel.AddWFNode(FarmCreationModel model, Boolean isFirstCommand)

Advertisements
3 Comments
  1. Steve permalink

    Like Ulysses Ludwig, I had to log in on the server as the RunAS account. Thanks Ulysses!

  2. I had the same problem, turns out that if I deleted everything and logged back in as the RunAs account everything installed correctly. Note that I tried different variations roughly 10 times before I stumbled upon that and I did make sure users were in the ServerAdmin and Local admin roles during the install — net effect is that logged in user should = RunAs in my case.

  3. Dave permalink

    I have the very same issue and of course I use fully qualified domain names. I went so far as creating an AD administrators group for both the workflow and service bus. I ensured my firewall is turned off on both servers and I still get this error. Has anyone got this to configure? I have went through this configuration three times already.

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: