Workflow issue- Service Bus Message Broker Stuck on Starting

Question

We are facing Service Bus Message Broker Stuck on Starting issue in SharePoint 2016 Workflow Manager farm. We don't want to reconfigure Workflow farm.
I also came across few blogs with similar issue-
https://spgeeks.devoworx.com/service-bus-message-broker-stuck-on-starting/
https://spgeeks.devoworx.com/workflow-manager-port-is-blocked/

Following is our troubleshooting approach-

1. TLS 1.2 is installed on Workflow server with latest security update and DOWRS “SchUseStrongCrypto” with 1 value.
2. No another web application program using service bus port.
3. Checked the status of Workflow Manager and Service Bus Services.
   Service Bus Gateway- running
   Windows Fabric Host Service- running
   Workflow Manager Backend- running
   Service Bus Resource Provider- running
4. We have already tried to kill and restart the service but unfortunately it didn't worked
5. Firewall is completely disabled, and we cannot check port status for Service Bus Message Broker 9356 in Resource monitor listening port.
6. updated Service Bus for .Net Framework 4.6.
7. The App Management Service is started.
8. The Workflow Manager Farm status is running.
9. The SharePoint Workflow Manager Proxy is connected.
10. The Workflow Manager web service is not browsable.

Awaiting your valuable feedback please.

Answer 1

I encountered similar error and my resolution was this:

Note: I am running on a single computer workflow farm

1. Open Workflow Config, Leave workflow farm using the account used to configure it. Copy the WF and SB Farm Info especially the DB names
2. Check your DB to make sure there are no entries under these tables, if you see your machine name under it please delete the row it will perform a cascade delete and remove all other references to the machine
   • SBManagementDB: Nodes table
   • WFManagementDB: Nodes table
     This step ensures that you do not see a "Machine already part of farm" error while adding server back to Farm
3. Open Workflow Config, join existing farm using Existing DB names from (1)
4. Once joined, check all services are running using Get-WFFarmStatus & Get-SBFarmStatus

Hope this helps!

Answer 2

@Ava Tomlinson

We have already tried to kill and restart the service but unfortunately it didn't worked

Have you tried to force stop Service Bus Message Broker as the blog you mentioned?

we cannot check port status for Service Bus Message Broker 9356 in Resource monitor listening port.

If checking the service in Resource Monitor Listening port, what is displaying?

Besides, please check the account that runs for Windows Fabric Host Service, make sure it is a farm account.

If this issue still occurs, please go to Windows Event Viewer to check if there is any clue about this issue.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

I can not really understand the steps to fix similar issue , but our company win server have probably same issue ?

we have service bus mesage broker and service bus gateway no starting and thisbelow is from event viewer !