Reporting session failures specific to an application launch or a running application is now made easy with Citrix Director.
A XenApp and XenDesktop administrator uses Director to monitor failures but finds it difficult to determine why a session failed, it could be due to issues in the XenApp and XenDesktop stack or with the application. 
This feature addresses this by collecting and displaying session failures due to applications. Administrators can generate reports on collected data and share with Application vendors to address the failures.
Application failures are categorized into two types based on their severity: Application Faults and Application Errors. An Application Fault indicates a significant problem, usually a loss of functionality or data. An Application Error indicates a problem that is not immediately relevant; they signify conditions that might cause future problems.

Q. Where can you find this feature on the Director console?

Log in to Director -> Click Trends -> Click Application Failures

Q.What filters can be applied to the data collected?

The Director console queries failures from the Monitor service and displays them in a tabular format.
The following filters are supported for Faults and Errors:

• Application Name (Name given for Admin on Studio)
• Process Name (Ex: outlook.exe)
• Delivery Group
• Time range: Last 2 hours, Last 24 hours, Last 7 days, Last month, Custom Time Period

Application Faults

Application Errors

Q.What do the table column names indicate?

Both Application Faults and Application Errors have the following columns:

• Time: Time of failure occurrence. You can sort the table by this column.
• Published Application Name: Name given to the application by the admin on Studio.
  Note: Published Application name is displayed as “Unknown” when the corresponding application name can’t be derived. This typically occurs when the launched application fails due to an unhandled exception caused by a dependent executable.
• Process Name: Executable involved in the failure
• Version: Version of the Executable involved in the failure
• Description: Failure details with the Executable name, path, version, exception code, module in which failure occurred
• User Name: User for whom the failure occurred
• Machine Name: Machine on which the failure occurred

Q.Which Export format is supported?

You can export the table data and generate reports in CSV, Excel or PDF formats. You have the flexibility to either include or exclude User details in the reports generated. While generating the report, select the Include User Details checkbox to include User information. This functionality is available for both Faults and Errors.

 

Q.Which versions of VDA supports this feature?

VDAs must be of version 7.14 or later. Desktop OS VDAs Windows Vista and later, Server OS VDAs Windows 2008 and later are supported.

Q.What is the default retention period and how to change it?

The retention period is as follows:

To configure retention period for Application Faults, run PowerShell command “Set-MonitorConfiguration -GroomApplicationFaultsRetentionDays ” on the Delivery Controller.
To configure retention period for Application Errors, run PowerShell command “Set-MonitorConfiguration -GroomApplicationErrorsRetentionDays ” on the Delivery Controller.

Q.Which are the Group policies to be applied to collect failures on VDAs?

By default, Application Faults on Server OS VDAs are collected. You can modify the collection settings through Group Policies: Enable monitoring of Application Failures, Enable monitoring of Application Failures on Desktop OS VDAs and List of applications excluded from failure monitoring.
Note: A registry key addition is required to enable this feature on VDA. Under registry hive, HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\VirtualDesktopAgent, create a key FeatureToggle and add DWord value ApplicationLaunchFailureTracking and set it to 1.