Unsolved
This post is more than 5 years old
1 Rookie
•
25 Posts
0
156271
January 10th, 2013 10:00
Connection Broker: "Server lookup didn't find a server"
Hi,
I have an issue with a vWorkspace 7.5 environment. It's an environment with 2 Connection Brokers and several RD Session Hosts. All Windows Server 2008 R2.
When building up the user session, the RD Session Host servers are contacted to calculate the server with the least load.
Sometimes the Connection Broker log Shows:
1652 : 2160 - Username = ***\*******
1652 : 2160 - Client IP Address = ***.***.***.***
1652 : 2160 - Client IP Name = *********
1652 : 2160 - Trusted End Point IP Address = ***.***.***.***
1652 : 2160 - Two Factor Authenticate = 0
1652 : 2160 - OU List = OU=*****,DC=local
1652 : 2160 - Checking for disconnected session on server *********1...
1652 : 2160 - Checking for active session on server *********1...
1652 : 2160 - Server=*********1, Evaluator=Advanced RD Session Host, Score=787
1652 : 2160 - Checking for disconnected session on server *********2...
1652 : 2160 - Checking for active session on server *********2...
1652 : 2160 - Server=*********2, Evaluator=Advanced RD Session Host, Score=788
1652 : 2160 - Checking for disconnected session on server *********3...
1652 : 2160 - Checking for active session on server *********3...
1652 : 2160 - Server=*********3, Evaluator=Advanced RD Session Host, Score=803
1652 : 2160 - Checking for disconnected session on server *********4...
1652 : 2160 - Checking for active session on server *********4...
1652 : 2160 - Server=*********4, Evaluator=Advanced RD Session Host, Score=785
1652 : 2160 - Server lookup didn't find a server (servername=*********5)
This happens on both Connection Brokers servers and several different Session Host Servers, but not all the time and it's not consistently.
This could potentially cause a user to end up with multiple sessions if he has an active or disconnected session on the server that the Connection Broker marks as "does not find". We have experienced this on multiple occasions.
My question is what does the status "Server lookup didn't find a server" exactly mean? Did DNS lookup fail? Does it perform a ping? Does it check a certain port? Is the agent on the RD Session Host perhaps sometimes not responding?
What could cause this issue? Any suggestions on how to debug or fix this?
DELL-Andrew W1
378 Posts
0
January 10th, 2013 12:00
Hi Freek,
The Connection Broker tries to talk to the RDSH server on 5203. This port is what the Data Collector Service listen on.
That error means that the Data Collector service was not available. It can be because the machine is rebooting, the ip address/dns lookup is wrong, the port is blocked... But the most likely reason is a problem with the Data Collector service that can be fixed with a hotfix.
The Data Collector service often stops. Normally the service is set to automatically restart so you don't really notice unless you're looking in the logs like above.
The way to prevent it happening again is to install the following hotfix for 7.5:
https://support.quest.com/SolutionDetail.aspx?id=SOL97296
The release notes within that download will tell you how to install it.
If anyone reading this thinks they may have the same problem but have 7.6 installed, this is the 7.6 hotfix.
https://support.quest.com/SolutionDetail.aspx?id=SOL97293
Those solutions above state that this only happens if you have the quickprep/instant provisioning tools installed. This is not always the case in my experience and you really should install that fix.
Thanks, Andrew
fberson
1 Rookie
•
25 Posts
0
January 10th, 2013 13:00
Thanks Andrew, we'll give that a go!