RD Connection Broker Availability

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.

Events

Event ID	Source	Message
832	Microsoft-Windows-TerminalServices-SessionBroker	The plugin loaded successfully. Following properties were loaded: Provider = %1 CLSID = %2 IsEnabled = %3.
833	Microsoft-Windows-TerminalServices-SessionBroker	The %1 plugin failed to load. HRESULT = %2.
834	Microsoft-Windows-TerminalServices-SessionBroker	The %1 plugin has an invalid sub key in the registry. Sub key for this plugin should be a positive integer that determines priority for that plugin (order in which plugins are called by the RD Connection broker). Please check the registry value for this plugin.
865	Microsoft-Windows-TerminalServices-SessionBroker	Access to registry subkey failed (%1). Please ensure that the registry subkey exists and Network Service has full access to the subkey.
898	Microsoft-Windows-TerminalServices-SessionBroker	RD Connection Broker service failed to start. HRESULT = %1.
901	Microsoft-Windows-TerminalServices-SessionBroker	RD Connection Broker service failed to start because of a problem during database initialization. Error code: %1.
902	Microsoft-Windows-TerminalServices-SessionBroker	The %1 group is empty. For the Remote Desktop Connection Broker service to work correctly, you must add the computer accounts of Remote Desktop Session Host servers to this group.
944	Microsoft-Windows-TerminalServices-SessionBroker	RD Connection Broker cluster initialization succeded. Cluster Network Name = %1 Cluster Uses Shared Disk = %2.
946	Microsoft-Windows-TerminalServices-SessionBroker	RD Connection Broker will not run as a part of cluster.

RemoteApp and Desktop Connection Management

Remote Desktop Services

Last updated on 2010-01-15