Service Bus Message Broker stuck in "Starting" / "Start Pending" RRS feed

  • Question

  • Hi Everybody,

    we are currently facing an issue with the Workflow Manager 1.0. We managed to install the Workflow Manager (Singel Server Farm) to the SharePoint 2016 Application server last year and everything seemed to be fine (we did not publish any 2013 Wokflows but had the option in SharePoint Designer).

    Last week we decided to make use of the Workflow manager but noticed that the "Service Bus Message Broker" Windows Service was stuck in "Starting" and failed after a couple of minutes. The IT department recently decided to force TLS 1.2 and we think this issue might be related because of SChannel Errors in Eventviewer.

    We decided to upgrade Service Bus KB4077554 and install Workflow Manager CU5 (KB4055730) to enable support for TLS 1.2.

    We followed the instructions and used WebPI for the Installation but when trying to rejoin the Server to the existing Service Bus / Workflow Manager Farm, the deployment gets stuck when trying to start the Service Bus Message Broker. Microsoft Service Fabric Host Service (FabricHostSvc) is started. There are less SChannel errors after the upgrade but the errors for the failing Message Broker Service started to increase.

    Is there anything else we can do? We could reinstall the Workflow Manager Farm but think the issue might persist.

    Thanks in advance!

    Our SharePoint 2016 environment:
    Web Front End server (Windows Server 2012 R2)
    Application server (Windows Server 2012 R2)
    Office Online server (Windows Server 2012 R2)
    SQL 2017 server

    Eventviewer entries:

    Event 1000 (Application Error) - Every 2 Minutes (or similar):
    Faulting application name: Microsoft.ServiceBus.MessageBroker.exe, version: 2.0.20922.0, time stamp: 0x5a0a1de1
    Faulting module name: unknown, version:, time stamp: 0x00000000
    Exception code: 0x80131623
    Fault offset: 0x00007ffc151a2cf0
    Faulting process id: 0x24f8
    Faulting application start time: 0x01d60292d6ad3609
    Faulting application path: C:\Program Files\Service Bus\1.1\Microsoft.ServiceBus.MessageBroker.exe
    Faulting module path: unknown
    Report Id: 4ad13f0f-6e86-11ea-81e7-00155d180a1c
    Faulting package full name:
    Faulting package-relative application ID:

    Event 1025 (.NET Runtime) - Every 2 Minutes:
    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.

    Event 36871 - SChannel (not regularly but around 10 times a day since we updated - previously ocurred multiple times per minute, beginning with the force of TLS 1.2)
    A fatal error occurred while creating a TLS client credential. The internal error state is 10013.

    Note: After Removing Service Bus 1.1 and Upgrading with the new package, I found the Service Bus for Windows Server 1.1 for .NET Framework 4.6 update package (KB3086798) was still installed. Just in case this is relevant.

    Friday, March 27, 2020 3:41 PM