I’ve been wrestling all weekend with the setup of a new training lab environment for my Citrix XenApp 5 certification studying. To quickly built my Citrix servers, I disabled the Windows firewall and run the developed scripts to auto install all prerequisites and the Citrix components. Everything seemed to be installing without problems and I quickly had my test environment up and running ….. at least so I thought.
When I tried to start a published application through the Web Interface I was presented with a vague error and a event log stating the XML service was too busy.
As I’m studying for the A08 Advanced Administration for XenApp, I figured I’d dive right into troubleshooting and get my hands-on experience with some tooling
So I started running some tests …
With the QFARM command, you can check the load for each server and see if access is granted to the server:
qfarm /load Server Name - Server Load ----------- ------------ CTXSVR_____ - 20000
Unfortunately for me, this was bad news, as it showed a load of 200% (or 20000) on my XenApp server, which excluded it from the available server pool for my application.
According to CTX111964 – Load Manager Values Explained a license mismatch was causing the error.
No startup license checked out
So I checked the license server and discovered no startup license was checked out for the CTXSVR. Back to Google to find more answers…
Fortunately for me posts on the subject could be found at the Citrix forums, so I started to follow the suggested solutions to the problem. I ensures my TS License configuration was set, ensured the Citrix licenses were in place and looked to see if that would solve the problem
One more solution
As all suggestions found so far failed to solve my problem, I found a remark regarding the installation of the Terminal Server role by dsearcy112. It stated that the Terminal Server role was not correctly installed if the Windows Firewall was disabled.
I did disable that firewall as I figured it would allow me to quickly set up my environment without having to take different acces rules into account. So I decided to just try this one as well, uninstalled the Terminal Server role, rebooted the server, enabled the Windows Firewall, installed the Terminal Server role and checked again.
Keep that firewall running!
To my surprise, it did work. You have to have an enabled Windows firewall if you want to correctly install the Terminal Server role and keep from mysterious loads on your Citrix XenApp servers! After the reboot I could see the load being dropped (could be dropped to 10000 or 100% first and than 0 or 0%), a startup license being claimed at the license server and a normal result from my qfarm command:
qfarm /load Server Name - Server Load ----------- ------------ CTXSVR_____ - 0
So ensure that Windows firewall is turned on when you install the Terminal Server or you might just get some unexpected results.
Check those Remote Desktop connection settings!
If you do not want to re-install the Terminal Server role, you can manually check the Remote Desktop connection settings.
|My second server had the same problem after running my scripts with the firewall turned on. I checked my Remote Desktop connection settings and discovered it was turned off.|
|After turning it on, the load evaluator for my server, dropped to 100% and after a few seconds dropped even further down, back to 0%.
No reboot or re-installation were required, as the manual change made windows add the required firewall rule to the system.
The following sources have be used to create this post:
CTX111964 – Load Manager Values Explained
CTX126868 – XenApp 6 QFARM /load Reports 20000
Citrix Forums – Thread: qfarm /load = 20000
Pingback: John Carey
Pingback: Solved: 200% Load on XenApp 5 for Windows 2008 « VirtuEs.IT | Citrix Certification , Citrix Exams , Citrix Practice Tests
This is due to a build in dependency in the installation routine in the Windows 2008. While setting the Terminal Server role someone at Microsoft made an assumption, using a WMI – Firewall call, and doesn’t handle the error well.
Extra info can be found at this url:
Olav, thank you for providing me with the additional information and KB article. With my scripted install no error was shown, so this helps in understanding why.