I'm having a problem enabling the HA function in Server 2012 R2 RDS.
Error:
The Remote Desktop Connection Broker server could not install the database named RDSBroker by using the connection string:
DRIVER=SQL Server Native Client 11.0;SERVER=BCS12;Trusted_Connection=Yes;APP=Remote Desktop Services Connection Broker;DATABASE=master.
The database name in the connection string is shown as [master] because in order to create a new database with admin specified name, a connection must be made to master database.
Error: Database is offline.
I have tested using a DSN from odbcad32 both 32 and 64 bit items. Tests for connectivity are successful.
TCP/IP is enabled for the default instance.
I have completely disabled the firewall.
I appear to have the correct permissions for my security group for RDS Brokers in SSMS, my group has the appropriate computer added as broker.
Instance is running and has been restarted since most recent changes
SQL Native Client is installed.
I have reinstalled the RDS Session Collection roles
I have tried SQL Express 2012, 2012 SP2, and 2014 (modifying the connector to the corresponding native client)
I have hosted the DB on the local server (broker), as well as another server.
I have previously set up RDS 2012 R2 Broker HA successfully using either SQL Express or SQL Standard, using either default instances or named instances.
Two out of Seven of my RDS collections will not enable Broker HA.
I have set up a new session collection from scratch in a test environment successfully, since trying to get this other one going. It works just fine.
A SEPARATE POINT (perhaps linked to the root cause of this problem)
Both of these collections appear to have problems initializing the actual RDP session when the Broker is not in HA mode. Connection from some locations will hang at "Initializing remote session" after successfully authenticating and directing to
the correct Session Host.
Eventlogs support successful connection to the Broker and Successful assignment to the Session Host, but the Remote Desktop never loads. ON OTHER PCs, it loads fine. I have some vendors and remote users complain of getting stuck at the initializing stage, and
I have experienced it myself at my work PC. Using my home PC, I am able to connect without issue.
I can't draw a definitive connection, but this problem is ONLY occurring on the session collections that I cannot convert to HA.
I see very few reports of this online (and very little assistance), which leads me to think it may be some configuration issue, but I simply cannot figure out what has gone missing.
***Please help troubleshoot this****