Event ID 865 — RD Connection Broker Availability
Published: January 8, 2010
Applies To: Windows Server 2008 R2
The RD Connection Broker must be available to accept connection requests from user sessions, RD Session Host servers in a farm, and RD Session Host servers running in redirection mode.
|Product:||Windows Operating System|
|Message:||Access to registry subkey failed (%1). Please ensure that the registry subkey exists and Network Service has full access to the subkey.|
Fail over to another node
This issue can happen if the Remote Desktop Connection Broker service is manually restarted on the active node. To resolve this issue, you must fail over to another node by using Failover Cluster Management.
To verify that the RD Connection Broker server is available, ensure that the Remote Desktop Connection Broker service is running.
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To check that the Remote Desktop Connection Broker service is running:
- On the RD Connection Broker server, open the Services snap-in. To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.
- If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
- In the Services pane, locate the service named Remote Desktop Connection Broker.
- Confirm that the Status column for the Remote Destktop Connection Broker service displays Started.