How to enable debug logging for Application Virtualization 5.0

S’applique à : App-V 5.0 for Windows Desktops

Summary


This article describes how to collect debug logging data for Microsoft Application Virtualization (App-V) products. This includes the App-V 5.0 desktop and RDP clients, the App-V 5.0 sequencer, and the App-V 5.0 server.

More Information


Use the following PowerShell commands to collect a debug trace on an App-V 5.0 client, sequencer, or server. Because traces can quickly grow very large, try to reproduce the issue as soon as possible after you are prompted by the "Please reproduce your issue now" message. To automatically enable and collect a trace, the App-V SDP is recommended. (You can download this tool from http://aka.ms/appvdiag.) The manual steps are provided here for reference.

Open an elevated PowerShell window, navigate to a temporary folder, and then run the following PowerShell commands to enable tracing and to reproduce your issue:
logman create trace AppVKB3037955Debug -o AppVDebug.ETL -cnf 01:00:00 -nb 10 250 -bs 16 -max 512 -ow -y
$providers = Get-WinEvent -ListProvider *Microsoft-Appv-* | Select-Object Name | Where-Object -Property Name -NotMatch "SharedPerformance"
foreach ($provider in $providers) { logman update trace AppVkb3037955Debug -p $($provider.Name) 0xe000000000ffffff 0x5 | Out-Null }
Logman Start AppVKB3037955Debug

cls
$nil = Read-Host "Please reproduce your issue now. Press [ENTER] when done."

Logman Stop AppVKB3037955Debug
dir *AppVDebug*.etl | foreach { netsh trace convert $_ overwrite=yes}
Logman Delete AppVKB3037955Debug
The trace files will be located in your temporary folder, and the file names will be in the AppVDebug_<Number>.txt format.

Note The <Number> placeholder represents an incremental number.