Following are some of the common debug issues that you might encounter when deploying DAS:
The action names are case-sensitive. Ensure that you follow a common naming convention, such as always using lowercase.
The DASlog.txt file indicates the syntax errors (if any) in the actions.xml file. If the syntax errors are not indicated, run each section separately to determine the error while parsing the actions.xml is executed.
Enable the log file and set the log level to 4 (verbose) on development workstations to help debug the issues. After you have completed the testing, set the log level to zero to have minimal logging.
Delete the DASlog.txt file after you have tested at log level 4 because the file size is large.
eDirectory can centrally store different workstation behaviors that require different DAS configuration files.
Configure the client in the registry to point to the desired DAS configuration object in the eDirectory.
You can also have the different actions.xml files managed locally on the unique workstations and have the other common workstations point to eDirectory.
When forcing the ICA Client to shut down with DAS, you should provide a pause before forcing the shutdown.
When DAS tries to shut down the ICA Client, it sends a WM_CLOSE message to the Citrix client. The Citrix client resends the message to the published application t If there is a timeout or if the application is slow to respond, DAS quickly forces the shutdown and does not allow the Citrix application to gracefully shut down. Adding a pause addresses the timing requirement.
Add pauses in the actions.xml file if you notice any unusual behavior or observe that some use cases are not met as expected. There might be some timing issues with certain event executions, so you should ensure that you set the correct values for the serial = true or false parameters.