Table of Contents
Advertisement
3
(Optional) Capture logs for a specific duration to troubleshoot an exact issue.
a
Select the Suspend check box.
b
Start the captured application and let it run to the point where the error occurs or the performance
problem starts.
c
In Log Monitor, deselect the Suspend check box to resume the logging process.
You can check the application behavior to isolate the issue.
d
Select the Suspend check box to stop the logging process.
4
(Optional) Select a file in the trace file list to delete and click Delete File.
5
(Optional) Click Kill App to stop a running process.
6
(Optional) Click the Compress check box to decrease the size of a trace file.
This operation slows the performance of the application.
7
(Optional) Generate a trace file report.
a
Select a trace file in the file list, type a trace filename, or click Browse to select a trace file on your
system.
b
(Optional) Type or change the name of the output report.
c
Click Generate text trace report to create a report.
You can view the file with a text editor that supports UNIX‐style line breaks.
Locating Errors
ThinApp logging provides a large amount of information. The following tips might help advanced users
investigate errors:
Review the Potential Errors Detected section of the .txt trace file.
Entries might not indicate errors. ThinApp lists each Win32 API call where the Windows error code
changed.
Review exceptions that the applications generate.
Exceptions can indicate errors. Exception types include C++ and .NET. The trace file records the exception
type and DLL that generates the exception. If the application, such as a .NET or Java application, creates
an exception from self‐generating code, the trace file indicates an unknown module.
The following example is a .trace entry for an exception.
*** Exception EXCEPTION_ACCESS_VIOLATION on read of 0x10 from unknown_module:0x7c9105f8
If you find an exception, scan the earlier part of the trace file for the source of the exception. Ignore the
floating point exceptions that Virtual Basic 6 applications generate during typical use.
Review child processes.
Log Monitor produces one .trace file for each process. If an application starts several child processes,
determine which process is causing the problem. Sometimes, such as in circumstances involving
out‐of‐process COM, a parent application uses COM to start a child process, runs a function remotely, and
continues to run functions.
When you run applications from a network share that generates two processes, ignore the first process.
ThinApp addresses the slow performance of Symantec antivirus applications by restarting processes.
VMware, Inc.
Chapter 10 Monitoring and Troubleshooting ThinApp
129
Advertisement
Table of Contents
Troubleshooting
