Service Bus Message Broker is not starting/ Struck on Stating / Stopped.
Error 1:
Service
Bus Message Broker Stopped / Stating stage on workflow Manager server.
The
Service Bus Message Broker service hung on starting
Solution
1:
Verify the below steps.
1.
Verify TLS 1.0 and TLS 1.1 are enabled or
not.
1. Enable
TLS 1.0 and TLS 1.1 in the registry under the path
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS
1.0\Client]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS
1.0\Server]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS
1.1\Client]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS
1.1\Server]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:00000001
2.
If not enable and reset the server.
3.
Verify whether Service Bus Message Broker
Started or not.
4.
If not proceed to the next steps.
1.
Verify ServiceBus RusAs Account and
Workflow Manager Run As Account added in the below group.
- Login to WFM primary
server with Rus as Account/administrator/ farm account/
Service account.
- Verify Run as Account has farm account is
part of below groups, if not need to be added.
c.
Open Run and type the below command.
d.
Command: lusrmgr.msc
e.
"Go to groups"
f.
Examine your login account in the
groups listed below, if not need to be added.
i.
Administrator
ii.
Distributed COM users
iii.
Remote Desktop Users
iv.
Windows Fabric Administrator
v.
Windows Fabric allows users
vi.
IIS users
vii.
Azure fabric Administrator
viii.
Azure Fabric allowed users.
- The installation account must have the
"sysadmin" role on the SQL server.
Please
find the references:
https://docs.microsoft.com/en-us/previous-versions/service-bus-archive/jj193011(v=azure.100)
3. Click
these links and verify these points
4.
Open the Workflow Manager configuration
wizard and click on leave farm.
5.
We have to leave the host from the workflow manager farm and rejoin.
Or
Leave
farm or Remove SB farm using the below command.
1.
Remove-WFHost -verbose;
2.
Remove-SBHost -verbose;
OR
3.
Remove-WFHost-HostName Hostname
-WFFarmDBConnectionString 'Connection String' -verbose
4.
Remove-SBHost-HostName Hostname
-SBFarmDBConnectionString 'Connection String' -verbose
Ex:
Remove-SBHost-HostName
ServerName
-SBFarmDBConnectionString 'Data
Source=vvvvvv;initilal catlog=wfmnanagementDB database name;Integrated
Security=True; Encrypt=False' -verbose
Note: Data Source you need to copy from
Get-WFFarm output value.
6.
Manually edit SQL database WFManagementDB
and SBManagementDB database table Store. Nodes table to remove a node.
Solution
2:
1.
Run the below command in Workflow Manager
PowerShell with Run As Administrator Account.
Remove-SBHost
2.
Download IIS Crypto:
1. You can
run this on the server and Set "Client" and "Server" to TLS
1.2 only
- De-Select TLS 1.0 for both(empty)
2. The
server will reboot
3.
Join back the farm to the workflow
manager.
Reference Articles:
https://docs.microsoft.com/en-us/previous-versions/Service-bus-archive/dn659461(v=azure.100)
https://spgeeks.devoworx.com/service-bus-message-broker-stuck-on-starting/
0 Comments