Score:0

Incorrect server identified as a broker when enabling HA for RDS 2019 deployment

fr flag

We've recently deployed a Windows Server 2019 RDS farm and this has all tested out perfectly, we're able to connect to collections without issue via RDWeb and connect to our collections.

So now it's all tested, we've tried to enable HA for the brokers. SQL aspect of it seems fine, the database is part of an AG and the listener is reachable over port 1433 from the brokers (worth noting all servers re in same subnet). The AG is also multisubnet so that's taken into account in the connection string and all the necessary roles/mappings are present on the database. However when it fails to connect, the server it mentions in the error isn't actually a broker, it's one of the session hosts in the farm. Error message thrown when attempting to connect to SQL

Has anyone seen this before as I literally have no idea where to start. If it was to name the broker that's trying to connect to SQL then I'd have something to go on but I've never seen it list a session host that it's somehow identified as a broker. I can only assume there's a config setting somewhere or registry that's causing this but any pointers would be appreciated.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.