rds failed to join the connection broker server manager 2016

Question

Pedro Steyn 0

current async message was dropped by async dispatcher, because there is a new message which overide the current one

Victor Meyer 0 Reputation points

2026-03-10T00:49:21.06+00:00

Make sure RPC communication is open between the Session Host and the broker in order to complete registration. This is not called out in their documentation unfortunately.

1 answer

Victor Meyer 0 Reputation points

2026-03-10T00:49:21.06+00:00

Make sure RPC communication is open between the Session Host and the broker in order to complete registration. This is not called out in their documentation unfortunately.

Answer 1

Hello,

Thank you for posting in Q&A forum.

Based on the error information you provided and according to Microsoft documentation, to solve this problem, please use one of the following methods:

Set up RDS without Connection Broker for a single-server installation.
Don't disable TLS 1.0 on a single Connection Broker deployment.
Configure a high availability Connection Broker deployment that uses dedicated SQL Server.
Upgrade the computers that run the RDS services to Windows Server 2019.

I hope the information above is helpful.

Best regards

Zunhui

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.