Quantcast
Channel: Remote Desktop Services (Terminal Services) forum
Viewing all articles
Browse latest Browse all 1106

RDP Connection Broker used without load balancing giving Error event 802 in normal operation.

$
0
0

I am using RDP Connection Broker's as a session directory for RDP sessions. 

We do not use the load balancing feature of connection broker as we have a hardware load balance that is aware of connection broker redirection tokens which is doing the balancing of initial connections.

As i understand it, whichever session host is given the initial connection is where the user should stay if there is not already a session for them on some other host in that farm. If there is already a session they should be redirected. 

This is how my setup is working, however we get an error in the SessionBroker event log on the Connection Broker server every time a user connects to a new sessions. 

Here's an example event log when a user connects without an existing session in the farm.

EventID = 800
RD Connection Broker received connection request for user username.
Hints in the RDP file (TSV URL) = tsv://MS Terminal Services Plugin.1.farmname
Initial Application =
Call came from Redirector Server = serverFQDN
Redirector is configured as Farm member


EventID = 803
RD Connection Broker has successfully determined the end point for this connection request.
Endpoint name = farmname
Endpoint type = Farm
Resource plugin name = MS Terminal Services Plugin

ERROR EventID = 802
RD Connection Broker failed to process the connection request for user username.
Load Balancing failed OR Specified endpoint could not be found.
HRESULT = 0x80070515.


EventID = 787
Session for user username successfully added to RD Connection Broker's database.
Target Name = serverFQDN
Session ID = 35
Farm Name = farmname

the error 802 is what is bothering me, we don't use load balancing so why should it be attempting to balance. we can see the session host successfully accepts the connection regardless and registers the new session with the broker. 

Here's an example of the user returning after disconnecting and happening to be balanced to another session host. 

EventID = 800
RD Connection Broker received connection request for user username.
Hints in the RDP file (TSV URL) = tsv://MS Terminal Services Plugin.1.farmname
Call came from Redirector Server = differentServerFQDN
Redirector is configured as Farm member


EventID = 803
RD Connection Broker has successfully determined the end point for this connection request.
Endpoint name = farmname
Endpoint type = Farm
Resource plugin name = MS Terminal Services Plugin

EventID = 807
RD Connection Broker has found a disconnected session for user (username) with session ID (36) on end point (originalServerFQDN). Load balancing will be skipped.

EventID = 801
RD Connection Broker successfully processed the connection request for user username. Redirection info:
Target Name = originalHost
Target IP Address = 10.0.0.150
Target Netbios = originalHost
Target FQDN = originalHostFQDN
Disconnected Session Found = 0x1

eventID = 786
Session state for user username changed to: Session Reconnected.
Target Name = originalHostFQDN
Farm Name = farmname
Session ID = 35


Everything is working happily as i expect it, but the event log is nagging us with errors constantly. 

should we expect this event 802 to occur in normal operation when load balancing is not used ?

or am I missing something else. 

-----------------

The connection broker is running in cluster services, active/passive on a pair of windows 2008r2 Enterprise servers. 

The session hosts are all 2008r2 standard. 

the farm name resolves to an IP on our hardware load balancer, a BigIP F5.


-Derek @ TempWorks Software



Viewing all articles
Browse latest Browse all 1106

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>