Forum Discussion
Workflow Manager Setup and Configuration Error
I've a problem with Workflow Manager Configuration and Setup.
My environment is as below:
- Service Bus 1.1 with TLS 1.2 Support installed
- Service Bus 1.1 with TLS 1.2 Support prerequisite Microsoft Azure Service Fabric installed
- I've 2 AD accounts and a AD Security Group
- WM.Setup AD User Account
- WM.Service AD User Account
- WM.Admins Security Group
- WM.Setup is member of the Local Admin Group
- WM.Service is RunAsAccount
- WM.Admins is Admin Group
- SP.Farm and SP.Setup accounts are member of the WM.Admins Security Group
The script that i use to configure and create Service Bus is as below:
New-SBFarm -SBFarmDBConnectionString "Data Source=spsql;Initial Catalog=$sbManagementDB;Integrated Security=True;Encrypt=False" -InternalPortRangeStart 9000 -TcpPort 9354 -MessageBrokerPort 9356 -RunAsAccount $wmServiceAccount -AdminGroup $adminGroup -GatewayDBConnectionString "Data Source=spsql;Initial Catalog=$sbGatewayDB;Integrated Security=True;Encrypt=False" -CertificateAutoGenerationKey $CertAutoGenerationKey -MessageContainerDBConnectionString "Data Source=spsql;Initial Catalog=$sbMessageContainer;Integrated Security=True;Encrypt=False" -Verbose;
Add-SBHost -SBFarmDBConnectionString "Data Source=spsql;Initial Catalog=$sbManagementDB;Integrated Security=True;Encrypt=False" -RunAsPassword $wmServiceAccountPass -EnableFirewallRules $true -CertificateAutoGenerationKey $CertAutoGenerationKey -Verbose;
My Problem:
When i use this script, Service Bus Message Broker stuck on starting. If i add the wm.service as a member of local admin group, and re-run the script, the service starts successfully.
Clues:
If the wm.service account is not member of the local admin group; when the script that i used above, is configuring Microsoft Service Fabric Host Service, its run as account is wm.service and the service seems as running. But the Service Bus Message Broker stuck on starting. I investigated further and found that when configuring Microsoft Service Fabric Host Service, the important xml file is not created as it should be. It creates the FabricHostSetting.xml file (under the C:\PorgramData\Microsoft\SF) but content of the file is incomplete. And in the event log, there are to many something like invalid address issues. If i add the wm.service account to the local admin group, Microsoft Service Fabric Host Service created the correct xml file as it sholud be. And Service Bus Message Broker start successfully.
Final:
Is the wm.service account has to be member of the Local Admin Group? If not, what i have to do?
Thanks.
WesleyWuMicrosoft
Hasan Köroğlu Microsoft Workflow Manager 1.0 is no longer supported already, and the successor is SharePoint Workflow Manager (SPWFM). For SPWFM, the Service Bus module is packaged into it so you would not need to install and configure SB separately while setting up SPWFM. Currently, we cannot support any SPWFM configuration method other than using the Workflow Manager Configuration Wizard, please refer to here for more information. Thanks.
Here is the logs i've collected. Running this installation with wmservice account is not member of the local admin group.
After adding wm.service to local admin group, the FabricHostSettings.xml file:
If i add the wmservice account to the local admin group, setup completes without any error.
The error logs as below:
Log Name: Microsoft-ServiceFabric/Admin Source: Microsoft-ServiceFabric Date: 4/5/2022 10:31:28 PM Event ID: 23041 Task Category: Hosting Level: Warning Keywords: Default User: Domain\Sp.WMService Computer: WFM01.Domain.local Description: GetActivationContextAsyncOperation called for invalid HostType NonActivated Log Name: Microsoft-ServiceFabric/Admin Source: Microsoft-ServiceFabric Date: 4/5/2022 10:30:58 PM Event ID: 23041 Task Category: Hosting Level: Warning Keywords: Default User: Domain\Sp.WMService Computer: WFM01.Domain.local Description: End(EnsureApplicationHost): ErrorCode=FABRIC_E_INVALID_ADDRESS Log Name: Microsoft-ServiceFabric/Admin Source: Microsoft-ServiceFabric Date: 4/5/2022 10:30:58 PM Event ID: 23041 Task Category: Hosting Level: Warning Keywords: Default User: Domain\Sp.WMService Computer: WFM01.Domain.local Description: End(OpenApplicationHost): ErrorCode=FABRIC_E_INVALID_ADDRESS Log Name: Microsoft-ServiceFabric/Admin Source: Microsoft-ServiceFabric Date: 4/5/2022 10:30:58 PM Event ID: 23041 Task Category: Hosting Level: Warning Keywords: Default User: Domain\Sp.WMService Computer: WFM01.Domain.local Description: IPC Client Open: ErrorCode=FABRIC_E_INVALID_ADDRESS Log Name: Microsoft-ServiceFabric/Admin Source: Microsoft-ServiceFabric Date: 4/5/2022 10:30:58 PM Event ID: 4353 Task Category: IPC Level: Warning Keywords: Default User: Domain\Sp.WMService Computer: WFM01.Domain.local Description: 2a492730390: demuxer_.Close() failed: FABRIC_E_INVALID_OPERATION Log Name: Microsoft-ServiceFabric/Admin Source: Microsoft-ServiceFabric Date: 4/5/2022 10:30:58 PM Event ID: 4352 Task Category: IPC Level: Error Keywords: Default User: Domain\Sp.WMService Computer: WFM01.Domain.local Description: 2a492730390: IPC requires loopback addresses, 0.0.0.0:0 is not Log Name: Microsoft-ServiceBus/Operational Source: Microsoft-ServiceBus Date: 4/5/2022 10:37:10 PM Event ID: 30712 Task Category: (34822) Level: Critical Keywords: Host component User: domain\Sp.WMService Computer: WFM01.domain.local Description: TrackingId: 68539237-fdf3-44a6-9b8b-2fe56438bd39_BWFM01, SubsystemId: NoSystemTracker. Failed to open Messaging Host Component System.Fabric.FabricInvalidAddressException: The supplied address was invalid. ---> System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x80071BBD at System.Fabric.Interop.NativeRuntime.FabricEndCreateRuntime(IFabricAsyncOperationContext context) at System.Fabric.FabricRuntime.NativeFabricRuntimeFactory.<>c__DisplayClass1b.<InitializeFabricRuntimeAsyncHelper>b__1a(IFabricAsyncOperationContext callback) at System.Fabric.Interop.AsyncCallOutAdapter2`1.Finish(IFabricAsyncOperationContext context, Boolean expectedCompletedSynchronously) --- End of inner exception stack trace --- at System.Fabric.FabricRuntime.Create(Action fabricExitCallback) at Microsoft.Cloud.ServiceBus.MessageContainerHost.Ring.Join() at Microsoft.Cloud.ServiceBus.MessageContainerHost.MessageContainerHostComponent.Open() Log Name: Microsoft-ServiceBus/Operational Source: Microsoft-ServiceBus Date: 4/5/2022 10:37:10 PM Event ID: 62002 Task Category: (3532) Level: Error Keywords: Broker User: domain\Sp.WMService Computer: WFM01.domain.local Description: Service Bus Broker service failed to start, retry count 2. Exception message: The supplied address was invalid.. Stack Trace: at System.Fabric.FabricRuntime.Create(Action fabricExitCallback) 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)Additionally, i tried uninstalling Service Fabric and installing latest version -8.2.1571-. The result was same. But this time error logs changed.
Log Name: Microsoft-ServiceBus/Operational Source: Microsoft-ServiceBus Date: 4/6/2022 3:15:39 AM Event ID: 30712 Task Category: (34822) Level: Critical Keywords: Host component User: Domain\Sp.WMService Computer: WFM01.domain.local Description: TrackingId: 3c46349b-60f6-4eff-af5a-6cb677595683, SubsystemId: NoSystemTracker. Failed to open Messaging Host Component System.Fabric.FabricException: An error occurred during this operation. Please check the trace logs for more details. ---> System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x80071CC0 at System.Fabric.Interop.NativeRuntime.FabricEndCreateRuntime(IFabricAsyncOperationContext context) at System.Fabric.FabricRuntime.NativeFabricRuntimeFactory.<>c__DisplayClass6_0.<InitializeFabricRuntimeAsyncHelper>b__1(IFabricAsyncOperationContext callback) at System.Fabric.Interop.AsyncCallOutAdapter2`1.Finish(IFabricAsyncOperationContext context, Boolean expectedCompletedSynchronously) --- End of inner exception stack trace --- at System.Fabric.FabricRuntime.Create(Action fabricExitCallback) at Microsoft.Cloud.ServiceBus.MessageContainerHost.Ring.Join() at Microsoft.Cloud.ServiceBus.MessageContainerHost.MessageContainerHostComponent.Open() Log Name: Microsoft-ServiceBus/Operational Source: Microsoft-ServiceBus Date: 4/6/2022 3:15:39 AM Event ID: 62002 Task Category: (3532) Level: Error Keywords: Broker User: domain\Sp.WMService Computer: WFM01.domain.local Description: Service Bus Broker service failed to start, retry count 1. Exception message: An error occurred during this operation. Please check the trace logs for more details.. Stack Trace: at System.Fabric.FabricRuntime.Create(Action fabricExitCallback) 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)
Steve ZhangThank you for the detail logs. We will take a look!
