Service Bus Message Broker stuck in "Starting" state suddenly


  • Service Bus Message Broker stucks in Starting State. I kill the process from task manager and tried again but it still gets in to starting mode. I try to leave the farm and re join at that time. I am getting the following error.

    I am also getting some error logs in Event Viewer.

    Faulting application name: Microsoft.ServiceBus.MessageBroker.exe, version: 2.0.20922.0, time stamp: 0x505e1bad

    Faulting module name: KERNELBASE.dll, version: 6.3.9600.17415, time stamp: 0x54505737

    Exception code: 0xe0434352

    Fault offset: 0x0000000000008b9c

    Faulting process id: 0x5588

    Faulting application start time: 0x01d298981e8e4fe7

    Faulting application path: C:\Program Files\Service Bus\1.0\Microsoft.ServiceBus.MessageBroker.exe

    Faulting module path: C:\Windows\system32\KERNELBASE.dll

    Report Id: 334baf86-048c-11e7-80df-001e67da5af9

    Faulting package full name:

    Faulting package-relative application ID:

    Please help.

    • Edited by SrK12345 Thursday, March 9, 2017 6:01 AM Issue
    Thursday, March 9, 2017 5:57 AM

All replies

  • Hi SrK12345,

    Please make sure that the Windows Fabric Host Service is running.

    If the Windows Fabric Host Service is not running, please start it, then try to start the Service Bus Message Broker again.

    If you cannot stop the broker service while starting, got to task manager and kill Microsoft.ServiceBus Message Broker process.

    Best Regards,

    Linda Zhang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Friday, March 10, 2017 5:28 AM
  • Hi All,

    I have the same issue. I've been trying to figure out how to fix it since 4 days ...

    In my case the Windows Fabric Host Service is running.

    Anybody has a workaround to this error?

    Friday, April 21, 2017 5:37 PM
  • Yup same here ...
    Apparently This stuff just doesn't work on a machine not attached to a domain from what i can tell.

    You also can't install this on a windows 10 PC either.

    ... apparently devs all work directly on production domain servers now I guess?


    Hmm it seems the answer is a little more brutal ...

    Since this product is no longer supported we can't expect a solution to this .. EVER!

    • Edited by TehWardy Friday, April 20, 2018 4:49 PM
    • Proposed as answer by TehWardy Friday, April 20, 2018 4:49 PM
    Friday, April 20, 2018 4:40 PM