![]() And in the event log, there are to many something like invalid address issues. It creates the FabricHostSetting.xml file (under the C:\PorgramData\Microsoft\SF) but content of the file is incomplete. I investigated further and found that when configuring Microsoft Service Fabric Host Service, the important xml file is not created as it should be. ![]() But the Service Bus Message Broker stuck on starting. 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. If i add the wm.service as a member of local admin group, and re-run the script, the service starts successfully. When i use this script, Service Bus Message Broker stuck on starting. 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 Īdd-SBHost -SBFarmDBConnectionString "Data Source=spsql Initial Catalog=$sbManagementDB Integrated Security=True Encrypt=False" -RunAsPassword $wmServiceAccountPass -EnableFirewallRules $true -CertificateAutoGenerationKey $CertAutoGenerationKey -Verbose The script that i use to configure and create Service Bus is as below: SP.Farm and SP.Setup accounts are member of the WM.Admins Security Group.WM.Setup is member of the Local Admin Group.I've 2 AD accounts and a AD Security Group. ![]()
0 Comments
Leave a Reply. |