Export (0) Print
Expand All

Connection Request Management

Published: January 8, 2010

Applies To: Windows Server 2008 R2

Connection requests in RD Connection Broker include user connection requests and redirection connection requests.

Events

Event ID Source Message

770

Microsoft-Windows-TerminalServices-SessionBroker

RD Connection Broker failed while adding Target %1.
Farm Name = %2.
HRESULT = %3.

771

Microsoft-Windows-TerminalServices-SessionBroker

RD Connection Broker failed while removing Target %1.
Farm Name = %2.
HRESULT = %3.

785

Microsoft-Windows-TerminalServices-SessionBroker

RD Connection Broker failed while changing session state for user %1 (on target %2). New State: %3
Farm Name = %4
Session ID = %5
HRESULT = %6

800

Microsoft-Windows-TerminalServices-SessionBroker

RD Connection Broker received connection request for user %1.
Hints in the RDP file (TSV URL) = %2
Initial Application = %3
Call came from Redirector Server = %4
Redirector is configured as %5

801

Microsoft-Windows-TerminalServices-SessionBroker

RD Connection Broker successfully processed the connection request for user %1. Redirection info:
Target Name = %2
Target IP Address = %3
Target Netbios = %4
Target FQDN = %5
Disconnected Session Found = %6

802

Microsoft-Windows-TerminalServices-SessionBroker

RD Connection Broker failed to process the connection request for user %1.%3
HRESULT = %2.

803

Microsoft-Windows-TerminalServices-SessionBroker

RD Connection Broker has successfully determined the end point for this connection request.
Endpoint name = %1
Endpoint type = %2
Resource plugin name = %3

804

Microsoft-Windows-TerminalServices-SessionBroker

RD Connection Broker could not find an assigned Personal Desktop for user %1. HRESULT = %2

805

Microsoft-Windows-TerminalServices-SessionBroker

Processing of the connection request is being paused for the previous request to finish.

806

Microsoft-Windows-TerminalServices-SessionBroker

Processing of the connection request has been resumed.

807

Microsoft-Windows-TerminalServices-SessionBroker

RD Connection Broker has found a disconnected session for user (%2) with session ID (%1) on end point (%3). Load balancing will be skipped.

808

Microsoft-Windows-TerminalServices-SessionBroker

A disconnected session could not be found for this user. HRESULT = %1.

809

Microsoft-Windows-TerminalServices-SessionBroker

(%1) Plugin successfully processed the connection request for Load Balancing. Target Name = %2.

810

Microsoft-Windows-TerminalServices-SessionBroker

(%1) Plugin successfully placed the target.

811

Microsoft-Windows-TerminalServices-SessionBroker

(%1) Plugin successfully orchestrated the target.

812

Microsoft-Windows-TerminalServices-SessionBroker

Remote Desktop Connection Broker will monitor this connection request and send appropriate notification to the plugin.
Sweep frequency = Once every %1 sec
Connection request timeout = %2 sec

813

Microsoft-Windows-TerminalServices-SessionBroker

Remote Desktop Connection Broker will not monitor this connection request. By default, only connection requests with farm type endpoints are monitored. To enable monitoring for a non farm type endpoint, add TargetClientConnectionMonitoring boolean property (value = true) to its target propertyset.

814

Microsoft-Windows-TerminalServices-SessionBroker

This connection request has %1. Remote Desktop Connection Broker will stop monitoring this connection request.

815

Microsoft-Windows-TerminalServices-SessionBroker

RD Connection Broker received connection request for user %1.
Hints in the RDP file (TSV URL) = %2
Call came from Redirector Server = %3

816

Microsoft-Windows-TerminalServices-SessionBroker

RD Connection Broker is about to call %1 for %2.

896

Microsoft-Windows-TerminalServices-SessionBroker

RD Connection Broker failed to delete all the log files in the "%SystemRoot%\System32\tssesdir\" directory. The error code was %1.

899

Microsoft-Windows-TerminalServices-SessionBroker

RD Connection Broker service failed to set the working directory retrieved from the registry.
Error code: %1.

900

Microsoft-Windows-TerminalServices-SessionBroker

RD Connection Broker had to switch the compression state in its directory to uncompressed.
Error code: %1.

945

Microsoft-Windows-TerminalServices-SessionBroker

RD Connection Broker cluster initialization failed.
HRESULT = %1.

1016

Microsoft-Windows-TerminalServices-SessionBroker

RD Connection Broker service denied the remote procedure call (RPC) from an unauthorized computer %1.

1022

Microsoft-Windows-TerminalServices-SessionBroker

Remote Desktop Session Host server %1 is not configured properly for redirection from legacy servers and should report only a single IP address to RD Connection Broker.

1024

Microsoft-Windows-TerminalServices-SessionBroker

RD Connection Broker failed to call Remote Desktop Session Host server %1 to propagate farm credentials.
Error code: %2.

1026

Microsoft-Windows-TerminalServices-SessionBroker

RD Connection Broker failed to update password of %1 farm account.
Error code: %2.

1280

Microsoft-Windows-TerminalServices-SessionBroker

RD Connection Broker failed to find Personal Desktop (%1) assigned to user %2 in RD Connection Broker database. Hr=%3

1281

Microsoft-Windows-TerminalServices-SessionBroker

RD Connection Broker failed to find any available VM in the farm %1.
User name = %2. Hr=%3

1282

Microsoft-Windows-TerminalServices-SessionBroker

VM Type mismatch: User's TS Client is requesting VM (%1) as type (%4); this does not match the VM type in the system, which is type (%3). This may have been caused by configuring the VM as both types (%3) and (%4).
User name = %2. Hr=%5

1285

Microsoft-Windows-TerminalServices-SessionBroker

Failed to spin VM %1 on host %2. Hr=%3

1297

Microsoft-Windows-TerminalServices-SessionBroker

VM Manager webservice failed to query the environment for the VM. Error code: %1 , Description: %2

1298

Microsoft-Windows-TerminalServices-SessionBroker

VM Manager webservice failed to create the environment for the VM. Error code: %1 , Description: %2

Related Management Information

RD Connection Broker

Remote Desktop Services

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft