This chapter will discuss some ways to troubleshoot your App Volumes enviroment.

This module contains the following lessons:

Launch Google Chrome

If you are still logged into App Volumes from the previous lab please click here.

  1. Launch Google Chrome, located on the Main Console desktop.

Sign into App Volumes Manager

  1. Enter Username: administrator
  2. Enter Passowrd:  VMware1!
  3. Click on Login
  1. Click on the Home button

Dashboard Overview

The dashboard overview page provides a good place to go to get an overview of the general health of your enviroment.   Information includes AppStack Utilization, licensing, and recent activities.

Navigate to Troubleshooting Tab

  1. From the App Volumes Manager, go to Activity
  2. Click on the Troubleshooting tab
  3. Click on Create


Create an Archive

An Archive is a log bundle that can be comprised of various logs and configuration files that can help you troubleshoot your App Volumes environment.  The Archive will be saved to a directory of the App Volumes Manager that you are connected to when running the creation process.  

  1. Un-check all the options but application_logs
  2. Click on Create

Note: More information on App Volumes logs can be found in KB 2091590

Confirm Archive has been Created


  1. Click on the + sign next to the Archive you just created.
  2. A variety of information is provided, including the location of the log file.
  3. Notice where the Archive is stored by default.  This cannot be changed.


Review Logon Segment Timing

Informational Only

Sometimes it can be difficult to determine if slow login time is being caused by App Volumes or your Horizon Desktop.  You can use the Horizon Help Desk Tool to troubleshoot slow logins.  To learn more about this tool please visit Tech Zone to review this video.  The tool will show how long each segment of the login takes.  To see this information in the Help Desk Tool, you will need to enable the timing profiler on each Horizon  Connection Server.

Use the following vdmadmin command to enable the timing profiler on each Horizon Connection Server:

vdmadmin -I -timingProfiler -enable

Use the following vdmadmin command to enable the timing profiler on a Connection Server instance that uses a management port:

vdmadmin -I -timingProfiler -enable -server {ip/server}

AppStack Not Attaching at Logon

Informational Only

If one or more host in vSphere cluster does not have access to the shared datastore where the AppStack resides, the AppStack will not consistently attach.   In the example above, you can see a "vmdk was not found" in the production*.log, as shown above.


Add your comment

E-Mail me when someone replies to this comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.