5.3

Troubleshooting the VMware Horizon
View Agent Direct-Connection Plugin 3
When using the Horizon View Agent Direct-Connection Plugin, you might encounter some known issues
and have to troubleshoot them.
When you investigate a problem with the Horizon View Agent Direct-Connection Plugin, make sure that
the correct version is installed and running. In the example above, the plugin version details are
version=e.x.p build-855808, buildtype=release. The plugin name VMware View Agent XML API
Handler Plugin is logged.
If a support issue needs to be raised with VMware, always enable full logging, reproduce the problem, and
generate a Data Collection Tool (DCT) log set. VMware technical support can then analyze these logs. For
details on generating a DCT log set, refer to Collecting diagnostic information for VMware View KB article
http://kb.vmware.com/kb/1017939.
Enabling Full Logging to Include TRACE and DEBUG information
The Horizon View Agent Direct-Connection plugin writes log entries to the standard View Agent log.
TRACE and DEBUG information is not included in the log by default.
Problem
The Horizon View Agent Direct-Connection Plugin writes log entries to the standard View Agent log.
TRACE and DEBUG information is not included in the standard View Agent logs by default.
Cause
Full logging is not enabled. You must enable full logging to include TRACE and DEBUG information in the
View Agent logs.
Solution
1
Open a command prompt and run C:\Program Files\VMware\VMware View\Agent\DCT\support.bat
loglevels
2 Enter 3 for full logging.
The debug log files are located in %ALLUSERSPROFILE%\VMware\VDM\logs. The file debug*.log has
information logged from the View Agent and the plugin. Search for wsnm_xmlapi to find the plugin log
lines.
When the View Agent is started, the plugin version is logged:
VMware, Inc. 17