XenApp 6.x QFARM /load Reports 20000

XenApp 6.x QFARM /load Reports 20000

book

Article ID: CTX126868

calendar_today

Updated On:

Description

After creating and configuring your new XenApp 6 farm, you receive the following error message when trying to launch applications:

“An error occurred while making the requested connection”.

The output from a Qfarm /load command prompt on a XenApp 6 server indicates a server load of 20000.
User-added image

Resolution

Follow the instructions below to resolve this issue:

  • Method 1: Remote Desktop
    1. Click Start.

    2. Right-click Computer.

    3. Go to Remote tab.

    4. Ensure the option Allow Remote connections from computers running any version of Remote Desktop (less secure) is selected.

      User-added image

  • Method 2: Licensing 
    1. Ensure the Licensing information for the farm is set correctly in Group Policy.
    2. Ensure the correct license server and license ports are configured.
      1. Open the Citrix Delivery Services Console > Policies node.
      2. Assuming the Unfiltered policy is used, select the Computer tab and edit the Unfiltered Policy.
      3. Click Licensing on the left and ensure the correct license server and port details are entered.
    3. Ensure the correct XenApp product version you have licenses for is configured. Click Server Settings and select the product version you have licenses for in the drop down as below in the screen shot below. This should be the version you have licenses for on the license server.
    4. Select Save to save the policies.
    5. On the problem server, run gpupdate /force to apply the policies.

Problem Cause

This error might occur if the Remote Desktop connections are not enabled on the XenApp 6 server or it can be related to XenApp Licensing

 

Issue/Introduction

This article explains the resolution to the error "An error occurred while making the requested connection" which occurs when trying to launch XenApp 6 farm applications.

Additional Information

XenApp 6 QFarm/load of 20000 and Policy Information is Removed from the Registry