Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,470 questions
Service Bus 1.1 Add-SbHost PrincipalServerDown
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 15%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMV%3C/text%3E%3C/svg%3E)
Matthew Vonhofen
0
Reputation points
Hello,
I have been having an issue with service bus 1.1, and adding a host. Here is a snip of the command & error:
Add-SBHost -SBFarmDBConnectionString $SBFarmConnectionString -RunAsPassword $SBRunAsPassword -EnableFirewallRules $true -Verbose;
Add-SbHost : The server could not be contacted
+CategoryInfo : OperationStopped (:) [Add-SbHost], PricipalServerDownException
+FullyQualifiedErrorID : WindowsFabricConfigurationFailed,Microsoft.ServiceBus.Commands.AddSBHost
In this scenario, I am working along side a vendor that provides the DC and the server infrastructure. I have reported this issue to them and they are not actively aware of what is interfering here.
Server : Windows Server 2019.
This is service bus 1.1 - NOT Azure Service Bus. (Yes I know it will be out of support soon).
The environment was established for the ongoing project, and the Active Directory configuration is basically "the default" according to the vendor.
We have checked LDAP ports - everything appears open.
We have used LDAP tools to successfully bind several users to the DC.
Is anyone aware of what is going on under the hood for Add-SBHost that could clue me into how it failing? Has anyone run into this before?