none
Service Bus Message Broker stuck starting RRS feed

  • Question

  • As described in topicname the Service Bus Message Broker stucks at starting with error below.
    I followed all post on technet, blogs etc. restarting services, restart service, hosts file, no proxy, no net 4.6 is installed but all no success and services still stuck starting.

    Windows Fabric service registration failed. Exception System.Fabric.FabricException: Service type is already registered. ---> System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x80071BD1
       at System.Fabric.Interop.NativeRuntime.IFabricRuntime.RegisterStatefulServiceFactory(IntPtr serviceType, IFabricStatefulServiceFactory factory)
       at System.Fabric.FabricRuntime.InternalRegisterServiceFactory(Boolean isStateful, String serviceType, ServiceFactoryBroker serviceFactoryBroker)
       at System.Fabric.FabricRuntime.RegisterServiceTypeHelper(Boolean isStateful, String serviceTypeName, Type serviceTypeImplementation)
       at System.Fabric.Interop.Utility.<>c__DisplayClassad.<WrapNativeSyncInvoke>b__ac()
       at System.Fabric.Interop.Utility.WrapNativeSyncInvoke[TResult](Func`1 func, String functionTag)
       --- End of inner exception stack trace ---
       at System.Fabric.Interop.Utility.WrapNativeSyncInvoke[TResult](Func`1 func, String functionTag)
       at Microsoft.Cloud.ServiceBus.MessageContainerHost.Ring.Join()

    TrackingId: a3d58b4c-5363-4952-a500-cc7a6c55ff56_BAPP28, SubsystemId: NoSystemTracker. Failed to open Messaging Host Component System.Fabric.FabricException: Service type is already registered. ---> System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x80071BD1
       at System.Fabric.Interop.NativeRuntime.IFabricRuntime.RegisterStatefulServiceFactory(IntPtr serviceType, IFabricStatefulServiceFactory factory)
       at System.Fabric.FabricRuntime.InternalRegisterServiceFactory(Boolean isStateful, String serviceType, ServiceFactoryBroker serviceFactoryBroker)
       at System.Fabric.FabricRuntime.RegisterServiceTypeHelper(Boolean isStateful, String serviceTypeName, Type serviceTypeImplementation)
       at System.Fabric.Interop.Utility.<>c__DisplayClassad.<WrapNativeSyncInvoke>b__ac()
       at System.Fabric.Interop.Utility.WrapNativeSyncInvoke[TResult](Func`1 func, String functionTag)
       --- End of inner exception stack trace ---
       at System.Fabric.Interop.Utility.WrapNativeSyncInvoke[TResult](Func`1 func, String functionTag)
       at Microsoft.Cloud.ServiceBus.MessageContainerHost.Ring.Join()
       at Microsoft.Cloud.ServiceBus.MessageContainerHost.MessageContainerHostComponent.Open()

    ServiceBus Broker service failed to start, retry count 3.  Exception message: Service type is already registered..  Stack Trace:    at System.Fabric.Interop.Utility.WrapNativeSyncInvoke[TResult](Func`1 func, String functionTag)
       at Microsoft.Cloud.ServiceBus.MessageContainerHost.Ring.Join()
       at Microsoft.Cloud.ServiceBus.MessageContainerHost.MessageContainerHostComponent.Open()
       at Microsoft.Cloud.HostingModel.ComponentHost.OpenComponent(IComponent component, RequestTracker tracker)
       at Microsoft.Cloud.HostingModel.ComponentHost.Open()
       at Microsoft.ServiceBus.MessageBroker.Backend.OnStart(String[] args)

    and further in application log

    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()

    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: 0x00007fff32b90392
    Faulting process id: 0x19a0
    Faulting application start time: 0x01d16e5c9c05e329
    Faulting application path: C:\Program Files\Service Bus\1.0\Microsoft.ServiceBus.MessageBroker.exe
    Faulting module path: unknown
    Report Id: 70ee2d3b-da52-11e5-80c8-005056bc5c8a
    Faulting package full name: 
    Faulting package-relative application ID: 

    get-sbfarm

    FarmType                      : SB
    SBFarmDBConnectionString      : Data Source=workflow;Initial Catalog=SbManageme
                                    ntDB;Integrated Security=True;Encrypt=False
    ClusterConnectionEndpointPort : 9000
    ClientConnectionEndpointPort  : 9001
    LeaseDriverEndpointPort       : 9002
    ServiceConnectionEndpointPort : 9003
    RunAsAccount                  : contoso\sa-wflow
    AdminGroup                    : contoso\SG wflowadmin
    GatewayDBConnectionString     : Data Source=workflow;Initial Catalog=SbGatewayD
                                    atabase;Integrated Security=True;Encrypt=False
    HttpsPort                     : 9355
    TcpPort                       : 9354
    MessageBrokerPort             : 9356
    FarmCertificate               : Thumbprint: 7B64670F9A39D011B32C9C23245438EB836
                                    CE850, IsGenerated: True
    EncryptionCertificate         : Thumbprint: 7B64670F9A39D011B32C9C23245438EB836
                                    CE850, IsGenerated: True
    Hosts                         : {Name: WF01.network.contoso.com, Configuration Sta
                                    te: HostConfigurationCompleted}

    get-sbfarmstatus

                 HostId HostName            ServiceName                      Status
                 ------ --------            -----------                      ------
                      1 wf01.network.co... Service Bus Gateway             Running
                      1 wf01.network.co... Service Bus Mess...        StartPending
                      1 wf01.network.co... FabricHostSvc                   Running

    Single server and all self signed certificates. Certificates all trusted and in trusted root ca auth store in MMC certificate snapin.
    Port 9000 is not in use by other service, when i kill service bus message broker and run stop-sbfarm and then run netstat -ano i cannot find a process that listens on port 9000 (0.0.0.0:9000) so its not in use. Then Fabric service starts and is running but service bus message broker hangs on starting.



    Tuesday, February 23, 2016 5:21 PM

Answers

All replies

  • Hi,

    We are facing exactly the same issue. I guess, the workaround would be to leave the farm and reconfigure it.

    I wonder what would happen with the workflows that are already running?

    Regards,


    -Ahmed Khan

    Wednesday, February 24, 2016 4:03 AM
  • I left the farm (single server) and rejoined.

    All is well now.

    Saturday, March 5, 2016 6:04 PM
  • What if my TFS server is stand alone?
    Wednesday, March 20, 2019 4:14 PM
  • I tried rejoin, reinstalling service bus no luck. Also updated fix pack. Any other suggestions?
    Sunday, May 26, 2019 5:19 PM