Crashing Terminal Session with Latest Citrix Receiver
Posted by William Diaz on August 17, 2012
After installing the latest Citrix Receiver 3.3, one of our techs began to experience crashes of their terminal sessions after about 1-2 minutes. I connected to my lab and installed the latest Citrix Receiver and was able to reproduce. In my case, the following error was generated: “WFICA32.EXE – Application Error. The exception Breakpoint. A breakpoint has been reached…”
An error may not always be produced, though, on the desktop. If you examine the Windows Event Viewer > Application logs you should see some type of error, either in the Visual C++ Runtime 2005 or in the actual Citrix module where the fault is being encountered in. For example:
Faulting application wfica32.exe, version 22.214.171.124, faulting module msvcr80.dll, version 8.0.50727.6195, fault address 0x0001574d.
Faulting application wfica32.exe, version 126.96.36.199, faulting module vd3dn.dll, version 188.8.131.52, fault address 0x00001021
After a little research, the most common culprit seems to be caused by printers that the workstation (XP SP3) cannot resolve to. These often have a status of “Unable to connect” and\or “Printer not found on server”:
After removing the offline printers on both the lab and the tech’s workstation, the issue went away. That being said, it might be more practical to downgrade to an earlier version of the Citrix Receiver. It’s not uncommon for network printers to be taken offline in large enterprises or decommissioned. Worse, imagine mobile users who will show all network printers as unable to connect when outside the network and trying to connect remotely to their virtual desktops. This seems specific to only Windows XP clients.
I ran into this again today issue where this was happening on a user workstation even after the disconnected printers were removed. Crash dumps pointed to hpcui6dn.dll. Using the Windows local print server on the workstation, we could see that the print driver belonged to one the disconnected printers. Apparently, an “orphaned” print driver could cause the problem as well. Resolving was a simple matter of stopping and restarting the print spooler and from the local print server properties selecting Remove for the printer driver that was no longer connected.
Application exception occurred:
FAULT ->35257cb2 c4b3029b1db1 les esi,[ebx+0xb11d9b02] ds:0023:b130883a=????????????
*—-> Stack Back Trace <—-*