How to use Director to troubleshoot application launch errors
book
Article ID: CTX223927
calendar_today
Updated On:
Description
Director extends the Trends view with the Application Failures tab to display historical failures associated with published applications. Administrators can see faults and errors (crashes and unhandled exceptions) that have occurred while launching or running of a selected application or process during a selected time period. This information enables you to comprehend and troubleshoot application-specific issues.
The application failures that are logged to the Event Viewer with source “Application Errors” are monitored.
This feature requires Delivery Controller(s) and VDAs version 7.15 or later.
Instructions
- By default, application failures are only captured on Server OS VDAs. In order to capture application faults and errors on Desktop OS VDAs, enable the policy “Enable monitoring of application failures on Desktop OS VDAs.”
- In addition, you can also configure whether application faults, errors, or both faults and errors are collected by selecting the policy “Enable monitoring of application failures” and selecting the appropriate drop down.
- To exclude applications from being monitored, select the policy “List of applications excluded from failure monitoring” and add the processes in the Values box.
- When an application fails to launch, log into Director and select the Trends tab. Then select the Application Failures tab.
- Select either Application Faults or Application Errors and search for the failure that just occurred. A detailed description will be available to assist with determining the cause of the event.
Note: The Published Application Name will display “Unknown” when the corresponding application name cannot be derived. This typically occurs when the launched application fails due to an unhandled exception caused by a dependent executable.
Was this article helpful?
thumb_up
Yes
thumb_down
No