Unable to Launch Published Applications from XenApp 6.x

You are unable to open published applications from XenApp 6 and the following error messages are displayed:

“Cannot connect to the Citrix XenApp server.
The Citrix XenApp servers are reporting full load and cannot accept your connection at this time.
Try to connect again after a few minutes. If you continue to receive this message, contact your Citrix administrator.”

“Unable to Launch your application, Contact your help desk with the
following information: Cannot connect to the Citrix XenApp server.

Protocol Driver error”

Cause

Several configuration options might prompt these errors.

There may be important XenApp connection ports (1494, 2598, etc.) that need to be opened on the firewall

Refer to CTX101810 – Communication Ports Used By Citrix Technologies

Consider one of the following resolutions to resolve the errors:

Resolution 1

Complete the following procedure to check that the Web Interface XML configuration is set properly:

Open Citrix Web Interface Management.




Select XenApp Web Sites.




Click Server Farms, as displayed in the following screen shot:

Click Edit, as displayed in the following screen shot:

a. Ensure that the correct XML broker(s) are listed under server.
b. Verify that the correct XML port is entered in XML Service Port, as displayed in the following screen shot:

Resolution 2

Complete the following procedure to ensure that both RDP and ICA listeners are not set to a specific network adapter.

From the XenApp Server(s) open Administrative Tools.




Remote Desktop Services.




Remote Desktop Session Host Configuration




Select RDP listener.




Right click, go into properties and verify all network adapters are selected, as displayed in the following screen shot:

After verifying all Network Adapters are selected, review the ICA adapters (only applies to XenApp 6 / Windows 2008 R2 x64). Click on Start > All Programs > Citrix > Administrative Tools > ICA Listener Configuration.

Resolution 3

Complete the following procedure to ensure XenApp 6 policies are configured correctly:

Open Citrix Delivery Services Console.




Click Policies.




Navigate to the Computer tab and Edit the unfiltered policy, as displayed in the following screen shot:

When the Identify your policy window opens, click Next.




Review your policies and enable the following settings, as displayed in the screen shot:

a. License Server Host
b. License Server Port
c. XenApp Product Edition
d. XML Service Port

Save the Policy.




Run gpupdate /force from server command prompt, as displayed in the following screen shot:

Resolution 4

Complete the following procedure to ensure that you have registered the correct the port on the XenApp 6 server(s):

From the XML broker(s) (XenApp Server) open Services.msc.




Ensure the Citrix XML service is started.
Note:If the service is not started, you might need to register the correct XML port on the server and restart the service:

Resolution 5

Always clear Local Host Cache on all servers in farm to ensure a fresh copy of the datastore subset is applied to the XenApp and Zone Data Collectors.

Resolution 6

Investigate CDF Tracing using CTX111961 – CDFControl

A customer had a scenario in which all of the servers did not have the application installed. Trace Analysis displayed the following information:

Got the client address from the connection: a.b.c.d

CAppSub::ResolveApplication3(internal) - BrowserName = SGSP4 entered.

QueryZoneMaster[Zone1]: Zone master is [XYZ1].

Entered. InitialProgram = "c:\program files (x86)\netmanage\rumba\AS400\Rumbawsf.Exe" C:\Strategy.wda

SearchPath failed with error 00000002. This could indicate the application is not installed.

CTX_ValidateInitialProgram returned error -3. App may not be installed on the local server.

CAppSub::CrossSubsystemResolveApplication - failed resolve request: 80110200h

CAppSub::ResolveApplication3 (Internal) CrossSubsystemResolveApplication failed: 80110200h

CXMLResponse::ErrorId - Error: mfserver-overloaded

More Information

Though IIS and XML can share the same port by default during an initial installation of XenApp 6, it is recommended as a best practice to assign a different port, for example: 8080 to XML.