Error - HDX Engine stopped working

  • CTX135585
  • Created onMar 26, 2014
  • Updated onMay 23, 2014
Article Topic Performance

Symptoms or Error

When users log on to a Published Desktop in XenApp 6.5 environment with UPS enabled and RES Power fuse installed and enabled and start another Published Desktop in the session they receive the error “HDX Engine stopped working”.

The following is displayed in the event viewer on the server where the user first logged on:

Log Name: Application Source: Application Error Date: 11/1/2012 4:25:08 PM Event ID: 1000 Task Category: (100) 
Level: Error Keywords: Classic User: N/A Computer: fqdn servername Description: Faulting application name: 
WFICA32.EXE, version:, time stamp: 0x4f7d9dd8 Faulting module name: MSVCR80.dll, version:
 8.0.50727.6195, time stamp: 0x4dcddbf3 Exception code: 0xc000000d Fault offset: 0x000225bc Faulting process 
id: 0x1e24 Faulting application start time: 0x01cdb845015a0862 Faulting application path: C:\PROGRA~2
\Citrix\ICACLI~1\WFICA32.EXE Faulting module path: 
Report Id: 516af520-2438-11e2-ab1f-005056985145 Event Xml: 
<Event xmlns=""> <System> <Provider Name="Application 
Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <
Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2012-11-01T15:25:08.000000000Z" /> <
EventRecordID>41687</EventRecordID> <Channel>Application</Channel> <Computer>fqdn 
servername</Computer> <Security /> </System> <EventData> <Data>WFICA32.EXE</Data> <
Data></Data> <Data>4f7d9dd8</Data> <Data>MSVCR80.dll</Data> <
Data>8.0.50727.6195</Data> <Data>4dcddbf3</Data> <Data>c000000d</Data> <Data>000225bc</Data> <
Data>1e24</Data> <Data>01cdb845015a0862</Data> <Data>C:\PROGRA~2\Citrix\ICACLI~1\WFICA32.EXE</Data> <

Data>C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll</Data> <
Data>516af520-2438-11e2-ab1f-005056985145</Data> </EventData> </Event>


When checking the user's printers in RES Powerprint it was noticed that one printer that was removed from the print server was still configured for the user in the Powerprint list.

To resolve the issue delete the removed printer from the list in Powerprint and restart the computer.

Automatic translation

Important: This article was translated by an automatic translation system (also referred to as Machine Translation, or MT) and has not been translated or reviewed by people. Citrix offers a machine translated version of this article to allow for greater access to the support content. However, automatic translation is not always perfect and may contain errors of vocabulary, syntax or grammar. Citrix is not responsible for inconsistencies, errors or damage incurred as a result of the use of MT articles from our customers.Thank you.
Click here to see the English version of this article.
Was this helpful?
Thank you for your feedback

Share your comments or find out more about this topic

Citrix Forums