I've 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.

Does anyone have a consistent fix for this?

Thank you

• Edited by computerpaul Friday, January 16, 2015 4:20 PM more information included

Hi,

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 to
task manager  and kill Microsoft.ServiceBus Message Broker process. Then start the broker service.

http://developers.de/blogs/damir_dobric/archive/2012/09/18/servicebus-message-broker-service-is-starting-and-starting.aspx

Regards

PT

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: 0x0000000000057609
Faulting process id: 0x102c
Faulting application start time: 0x01d031b01cd077de
Faulting application path: C:\Program Files\Windows Fabric\bin\Fabric\Fabric.Code.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: 



Hi,

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?

Regards,

I don't remember being prompted for a certificate during the installation of Workflow Manager so I'm assuming a self-signed certificate was used.

Other then the consistent Fabric.exe error, I've found a few of these:

Log Name:      Application
Source:        .NET 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: Microsoft.ServiceBus.MessageBroker.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, System.Threading.ContextCallback, 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()

Followed by one of these:

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: 

Also, occasionally there is one of these:

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: 0000000000057609
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: 

Thank you for your assistance

Hi,

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?

Regards,

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.

Hello,
 
This is a quick note to let you know that we are performing research on this issue.
 
Thank you for your understanding and support.
 
Regards,
Forum 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, contact tnmff@microsoft.com .

Hi,

Please follow the steps below for troubleshooting:

1.Check services in SharePoint

• In CA, distributed cache service is start.
• Run->services.msc, AppFabric Caching service is running.

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

• Check DistributedLogonTokenCache settings:

$settings = Get-SPDistributedCacheClientSetting -ContainerType DistributedLogonTokenCache

$settings

Run the command to change the settings

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

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

• Check DistributedViewStateCache settings:

$settingsvs = Get-SPDistributedCacheClientSetting -ContainerType DistributedViewStateCache
$settingsvs

Set DistributedViewStateCache

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

$settingsvs.MaxBufferSize = 33554432
Set-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 DistributedLogonTokenCache<o:p></o:p>

Get-SPDistributedCacheClientSetting -ContainerType DistributedViewStateCache

Regards,

Thanks for these troubleshooting steps. Unfortunately it didn't seem to do the trick.