Ive done quite a bit of searching on this issue and have found a reasonable amount of potential fixes, all of which I tried and none of which have worked.

This service simply is stuck in the Starting status. The only way to stop it is to kill the process in Task Manager.

I have tried reinstalling Workflow Manager and the Service Bus and starting from scratch. All of the databases get created successfully (on the same server as the rest of the SharePoint dbs) and the firewall is disabled via group policy.

Im not sure if I like this, but installing Workflow Manager on a separate server worked. I hope Microsoft can find a fix so that people with single server farms will be able to take advantage of workflow manager, specifically SharePoint 2013 workflows.

Take a look on status of Windows Fabric Host Service. You will probably notice that this service is not running. If so start it, stop the broker and start the broker again. If you cannot stop the broker service while starting, got totask manager and kill Microsoft.ServiceBus Message Broker process. Then start the broker service.

Thanks for the reply, but unfortunately this is another one of the things I have checked.

After going through the configuration wizard, I copied the Powershell commands so I could run them one by one.

The one that it gets stuck on is the Add-SBHost. The Windows Fabric service gets successfully started however, I then see that it crashes and produces an Application Error in the event log:

Faulting application name: Fabric.exe, version: 1.0.960.0, time stamp: 0x50415e97 Faulting module name: msvcrt.dll, version: 7.0.9600.17415, time stamp: 0x545055fe Exception code: 0x40000015 Fault offset: 0x9 Faulting process id: 0x102c Faulting application start time: 0x01d031b01cd077de Faulting application path: C:\Program Files\Windows de.1.0\Fabric.exe Faulting module path: C:\Windows\system32\msvcrt.dll Report Id: 5a8e50d5-9da3-11e4-944c-005056b54be1 Faulting package full name: Faulting package-relative application ID:

Are you using Self signed certificate during Workflow Manager installation? If not, where did you generate the certificate?

Could you please locate more error information to help narrow down the issue?

I dont remember being prompted for a certificate during the installation of Workflow Manager so Im assuming a self-signed certificate was used.

Other then the consistent Fabric.exe error, Ive found a few of these:

Log Name: Application Source: Runtime Date: 1/17/2015 10:27:15 PM Event ID: 1025 Task Category: None Level: Error Keywords: Classic User: N/A Computer: SERVER.URBANSCIENCE.NET Description: Application: ssageBroker.exe Framework Version: v4.0.30319 Description: The application requested process termination through System.Environment.FailFast(string message). Message: Failed to start Service Bus Broker Service. Stack: at System.Environment.FailFast(System.String, System.Exception) at Microsoft.ServiceBus.MessageBroker.Backend.OnStart(System.String[]) at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, ntextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch()

Log Name: Application Source: Application Error Date: 1/17/2015 10:27:15 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: SERVER.URBANSCIENCE.NET Description: Faulting application name: Microsoft.ServiceBus.MessageBroker.exe, version: 2.0.20922.0, time stamp: 0x505e1bad Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0x80131623 Fault offset: 0x00007ffe98880392 Faulting process id: 0x1258 Faulting application start time: 0x01d032cb6fff9cc1 Faulting application path: C:\Program Files\Service Bus\1.0\Microsoft.ServiceBus.MessageBroker.exe Faulting module path: unknown Report Id: e5c10ccf-9ec1-11e4-944c-005056b54be1 Faulting package full name: Faulting package-relative application ID:

Log Name: Application Source: Windows Error Reporting Date: 1/17/2015 10:44:24 PM Event ID: 1001 Task Category: None Level: Information Keywords: Classic User: N/A Computer: SERVER.URBANSCIENCE.NET Description: Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Fabric.exe P2: 1.0.960.0 P3: 50415e97 P4: msvcrt.dll P5: 7.0.9600.17415 P6: 545055fe P7: 40000015 P8: 9 P9: P10: Attached files: These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_Fabric.exe_dff3396dfc7088bc83825f6fab39b69ed8dcbf3d_35c2c815_3e49d45b Analysis symbol: Rechecking for solution: 0 Report Id: 4b139b86-9ec4-11e4-944c-005056b54be1 Report Status: 0 Hashed bucket:

From your post, error The application requested process termination through System.Environment.FailFast(string message) occurs along with Event ID 1000 and Event ID 1001.

Did you install CU or updates to your workflow server before? Could you please provide the source you download workflow manager?

I will admit, getting the right version was a little confusing. Using the Web Platform Installer 5.0, I installed the Workflow Manager and Client 1.0 (2.0.40131.0) and Service Bus 1.0 (2.0.20922.0).

As far as windows updates, the server has the latest.

This is a quick note to let you know that we are performing research on this issue.

Thank you for your understanding and support.

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, .

Please follow the steps below for troubleshooting:

2.If issue persists, please run the command in SharePoint 2013 Management Shell

$settings = Get-SPDistributedCacheClientSetting -ContainerType DistributedLogonTokenCache

$settings.ChannelOpenTimeOut =10000$settings.RequestTimeout=10000

$settings.MaxBufferSize = 33554432Set-SPDistributedCacheClientSetting -ContainerType DistributedLogonTokenCache -DistributedCacheClientSettings $settings

$settingsvs = Get-SPDistributedCacheClientSetting -ContainerType DistributedViewStateCache$settingsvs

$settingsvs.ChannelOpenTimeOut = 10000$settingsvs.RequestTimeout=10000

$settingsvs.MaxBufferSize = 33554432Set-SPDistributedCacheClientSetting -ContainerType DistributedViewStateCache -DistributedCacheClientSettings $settingsvs

3.Try to restart distributed cache and AppFabric caching service to check if issue persists.

4.If issue persists, please collect the information to me for further research:

Get-SPDistributedCacheClientSetting -ContainerType DistributedLogonTokenCacheo:p/o:p

Get-SPDistributedCacheClientSetting -ContainerType DistributedViewStateCache

Please follow the steps below to clean i file:

1. Please stop SharePoint Timer Service.2. Please navigate to the cache.ini file location:a. Delete all the .xml file and only leave cache.ini in the file location.b. Edit the Cache.ini file and set it to 1.c. Save the Cache.ini file.3. Start SharePoint Timer Service. The cache file will be created autumnally.4. Wait one day and check if issue persists.

I have tried these steps and unfortunately still get the same results when attempting to configure the Service Bus Host. Not sure if it matters, but I noticed after I saved the i file with a value of 1, it got reupdated with the previous number once the SharePoint Timer service was started.

That is normal behavior when resetting the cache.

Check that your certificate is loaded into thetrusted root certification authoritieson your server.

If youre running Distributed cache on this server, make sure youre not running SQL server, project server, excel services, and / or search services on this machine, as this causes issues with distributed cache and might be related.

Im not sure if I like this, but installing Workflow Manager on a separate server worked. I hope Microsoft can find a fix so that people with single server farms will be able to take advantage of workflow manager, specifically SharePoint 2013 workflows.

This thread has lot of useful information. How did you resolved this issue, please advise.

I am having similar issue and last couple of weeks searching for a solution.

I am facing issue on my SP development machine, which is a single VM and everything in one box.

We are on the same boat as you were? Please let us know.