VMware AppVolume – Troubleshooting

This blog provides details on troubleshooting an App Volumes environment using the App Volumes logs.

Here are the log files that you can look at in order to troubleshoot:

  • App Volumes Manager logs
  • App Volumes Agent log files

App Volumes Manager logs :

The App Volumes Manager log files are:

  1. svmanager_server.log
  2. production.log

These log files are located at C:\Program Files(x86)\CloudVolumes\Manager\Log on the App Volumes Manager server.

Here are the details about Production and SVManager logs:

production.log :

The App Volumes Manager server contains logging from the main modules of App Volumes. Use the production.log file to identify a variety of issues in an App Volumes environment.

Here is a description of the main modules to search for in the production.log file.

  1. RADIR : RubyActiveDIRectory classes – Responsible for AD connection
  2. Cvo : App Volumes logic classes
  3. RvSphere : RubyvSphere wrapper classes
  4. SQL : Database queries (Default logging captures only errors. Debug logging captures queries and errors)
  5. PowerShell : App Volumes PowerShell interface classes
  6. NTLM : App Volumes NTLM handler

svmanager_server.log :

The svmanager_server.log file captures App Volumes Manager server actions. You can correlate these actions with the Agent log files by checking time stamps from both the server and agent logs. The svmanager_server.log file also captures information relating to the App Volumes infrastructure.

App Volumes Agent log files :

The App Volumes Agent log files are:

  • svservice.log
  • svdriver.log
  • svcapture.log – “This log file is present only on a capture machine”

Locations for Agent log files :

In releases earlier than App Volumes 2.9, the App Volumes Agent logs are located at C:\Windows on the Agent machines. The svcapture.log file is also located at C:\Windows , on the capture machine.

“For App Volumes 2.9 and later, the Agent log locations have changed”

The svservice.log file is located at C:\Program Files (x86)\CloudVolumesAgent\Logs on the Agent machines.

The svcapture.log file is located at C:\Program Files (x86)\CloudVolumesAgent\Logs on the capture machine.

Here are details on the Agent log files:

svservice.log: 

SvService is the service responsible for communication between the App Volumes Agent and the App Volumes Manager, including the preparation of volumes, the running of post-attach scripts, refresh of variables, and registration of fonts. The log tracks this communication.

svcapture.log: 

The SvCapture service performs provisioning and editing functions during application capture, such as generating policy files and metadata. The SvCapture reports this information to the App Volumes Agent and App Volumes Manager. The log tracks this activity and is available only on the capture machine.

svdriver.log:

SvDriver is a policy-driven driver file responsible for the virtualization of volume contents into the desktop OS. The policy file snapvol.cfg controls the files, directories, registry keys, and processes that are virtualized during application capture on each volume. The log tracks this activity.

I hope this is informative for you. Thanks for Reading!!!. Be Social and share it in social media, if you feel worth sharing it. 

Related Posts:

  1. What is VMware App volumes?
  2. VMware App Volumes Components
  3. System Requirements for App Volumes? 
  4. VMware App Volumes documentation
  5. VMware App Volumes, Installation & Configuration
  6. VMware App Volumes – How to Create a New App Stack?
  7. VMware App Volumes – How to Assign and unassign an appstack?
  8. VMware App Volumes – About Writable Volumes?
  9. VMware App Volumes snapvol.cfg – Explained
  10. Introducing VMware AppVolume 3.0 and whats new ?