[x]

Site Alert(s):

  • Server maintenance Saturday Nov 22, 2008, 12:00 PM - 3:00 PM. The Knowledge Center will be unavailable during this time.
Rate this Article:
You must be signed in to rate again
Article Feedback Print View
Alternate Languages: N/A

Explaining and Troubleshooting ICA Session Initialization and Published Application Launching

Document ID: CTX106250   /   Created On: May 2, 2005   /   Updated On: Jan 25, 2008
Average Rating: 3

Summary

Citrix Technical Support often receives calls about the launching and abnormal disconnecting of ICA sessions. This article provides a logic process with respect to troubleshooting the connectivity of an ICA session. Many of the referenced articles have additional links. Make note of the links within the referenced articles. In addition, search the Citrix Knowledge Base if there is a specific error message.

Connecting to a Published Application

The ICA client sends out request for a published application. The MetaFrame XP Data Collector, or MetaFrame 1.8 Master Browser resolves the connection to the least busy server. The QFarm and Qserver commands can help determine what server is the least loaded. Use the ICA Client Connection Center or open up the resulting ICA file in a text editor to determine the logon server. Citrix Support may ask customers to publish an individual copy of Notepad on each server to help in determining connectivity issues. Once the logon server is determined, compare a ICA Desktop connection versus a Published application connection and follow the below steps.

CTX104771 - Overview of the Presentation Server Client XML Communication Process and Web Interface XML Service Load Balancing

CTX101691 - Active Server Pages error ASP 0113 and Applications are slow to enumerate within NFuse

Troubleshooting

The Listener end waits on “ICA” string detect, Winstation state to CONNQ (Connection Request), attempts to get/verify a Windows license, accepts the connection (Gina), and queries the client configuration for available virtual channels.

1. Is the ICA-TCP listener defined in Citrix Connection Configuration, enabled, appearing in Terminal Server Administration (Tsadmin.exe) and editable? If the listener does not appear in Terminal Server Administration, check the Event Viewer for potential issues where Wsxica.dll failed to load. Wsxica.dll and RDPwsx.dll depend on TermSrv.exe. Ensure the RDP listener does not experience similar issues.

2. For Terminal Server Edition 4.0 and Windows 2000 are listening stacks available? Wdica.sys is dependant of Termdd.sys

3. Do basic ICA connectivity tests work?

    ⌂⌂ ICA⌂⌂ ICA⌂⌂ ICA⌂⌂ ICA⌂⌂ ICA⌂⌂ ICA⌂⌂ ICA⌂⌂ ICA⌂⌂ ICA⌂⌂ ICA⌂⌂ ICA⌂⌂ ICA⌂⌂ ICA⌂⌂ ICA⌂⌂ ICA⌂⌂ ICA
    ⌂⌂ ICA⌂⌂ ICA⌂⌂ ICA⌂⌂ ICA⌂⌂ ICA⌂⌂ ICA⌂⌂ ICA⌂⌂ ICA⌂⌂ ICA

4. Do you get a Microsoft or Novell Gina? Enable the prompt for password check box within the ICA listener. This determines if the listening stack is created within Terminal Server Administration. Crss.exe and winlogon.exe should be the only running process on the session. Common reasons for a failure at this step are either network or Terminal Server License related. Wsxica.dll verifies a user has rights to a published application. Winlogon.exe launches userinit.exe. Userinit.exe reads the appsetup key under:

HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/WindowsNT/CurrentVersion/Winlogon

and cmstart.exe is launched.Ctxnotif.dll is loaded in the context of the system account by Winlogon.exe. The following registry key is read:

HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/WindowsNT/CurrentVersion/Winlogon/Notify/MetaFrame

5. Citrix attempts to obtain a valid Citrix License. Search the Event Viewer and then the Citrix Knowledge Base to resolve any Citrix Licensing issues.

6. The logon processes, userinit.exe (profiles), usrlogon.cmd, cmstart.exe, icast.exe,and so on start to load. If some of the start up processes trap, the session is destroyed before the application is presented. When passing through credentials, this is often difficult to determine, that is why Step 4 is so important. Check the Event Viewer and enable Dr. Watson. Icast.exe (application launcher) waits for Wfshell.exe to complete before launching the initial program for the published application. If Cmstart.exe is not listed under AppSetup value, Wfshell.exe is not launched and Icast.exe times out. When the userinit.exe hangs (a Microsoft process), you cannot start a new application from the same server until the userinit.exe process has completed.

Pmonitor.exe is affecting session start-up

7. DLL Loading Order:

    • Current directory of the image file

    • The process's current directory

    • Windows system directory

    • Windows directory

    • Directory listed in PATH variable

8. Trace the session, if needed, with Citrix and/or Networking utilities.

9. Once the session is established, the session may become disconnected.


Search
Knowledge Center
XenApp
XenApp Plugins (Clients)
XenServer
XenDesktop
NetScaler Application Delivery
Access Gateway
EdgeSight
Provisioning Server
WANScaler
Password Manager
Does it work with Citrix? Verify it - introducing the new Citrix Ready Community Verified