How to Enable the Streaming Client Debug Console

How to Enable the Streaming Client Debug Console

book

Article ID: CTX112472

calendar_today

Updated On:

Description

This article describes how to enable the Streaming Client Debug Console.

The Citrix Streaming Client is responsible for opening the application package, streaming the files, building the sandbox, and executing the application. The Streaming Client Debug console can be enabled to troubleshoot the client-side streaming issues.


Instructions

Note: The following procedure must be completed on the server if “Streaming to Server” is required and on the workstation if “Streaming to Client” is required.

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

To enable the Streaming Client Debug Console on a 32-bit device

Make the following changes to the registry on the machine that is running the Streaming Client:
Under HKEY_LOCAL_MACHINE/Software/Citrix/Rade/
ADD DWORD “EnableDebugConsole”
ADD Value  =1

To enable the Streaming Client Debug Console on a 64-bit device

Make the following changes to the registry on the machine that is running the Streaming Client:
Under HKEY_LOCAL_MACHINE/Software/Wow6432/Citrix/Rade/
ADD DWORD “EnableDebugConsole”
ADD Value  =1
Note: The Streaming Client Debug Console sends the real-time information to the command prompt and not to a text file.

To save the data

  1. Use the MARK/COPY/PASTE options. Use MARK, then select ALL, and then COPY.

  2. Paste the text into Notepad.

Note: For large applications, it might be necessary to increase the buffer in the command prompt before running the Streaming Client Debug console (edit the properties of the command prompt).

To disable the Streaming Client Debug Console

To disable the debugger, change the EnableDebugConsole value from 1 to 0.

Environment

Caution! Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.

Issue/Introduction

This article describes how to enable the Streaming Client Debug console.

Additional Information

The Streaming Client Debug console shows which RAD file is being read and which package is being opened. It logs the amount of time it takes to complete each step. It also tracks the license request and response.

The following is a sample output from the client-side Streaming Client Debug console when a license was unavailable:
User-added image

"Starting RADE application...
Starting RAD file "C:\Documents and Settings\Administrator\Application Data\Citrix\PNAgent\ResourceCache\15190515.RAD"...
User configuration information completed at 156 ms
Attaching to \\CPS45\streams\Acrobat\68389cbb-4554-452c-ac84-2edb1b9ddad9_1.cab...
Target acquired at 515 ms
Target Upgrade completed at 515 ms
Target Creation completed at 515 ms
Launch timing started
Launching app Device\c\program files\adobe\acrobat 5.0\reader\acrord32.exe...
Virtual Exe Name: c:\program files\adobe\acrobat 5.0\reader\acrord32.exe
Progress bar: 0
Progress bar: 5
Target Attach completed at 32 ms
Full command line:
Command line merge completed at 32 ms
Sandbox rules extracted and prepared at 47 ms
Sending license request to WI server.
Progress bar: 10

License requested at 328 ms
Extracting application "Device\c\program files\adobe\acrobat 5.0\reader\acrord32.exe"...
Executable extraction completed at 328 ms
Progress bar: 15
Getting license response...
Sending app-stopped message to WI server...
Running post-exit package-level scripts...

Error starting RAD file – There are no licenses available."
Or 
You might see the following output instead at the end of the log:  
"Error starting RAD file - The Web Interface server returned an unspecified error.
License requested at 328 ms
Extracting application "Device\c\program files\adobe\acrobat 5.0\reader\acrord32.exe"...
Executable extraction completed at 328 ms
Progress bar: 15
Getting license response...
Sending app-stopped message to WI server...
Running post-exit package-level scripts...

Application terminated - press any key to close..."