March 14, 2014
Highlights of Transaction Trace Analysis 12.2
Task Cleanup Guide
The Task Cleanup Guide walks you through simple steps for cleaning up trace data so that you can focus on the problem you are trying to solve.
Network Forensics Extensions in Trace Trimmer
Trace Trimmer has been updated to integrate with the new Network Forensics functionality on the CAS.
Network forensics functionality enables you to analyze and diagnose the cause of a known and observed network problem by examining detailed packet trace data. Once a monitoring system has detected a network problem, the network forensics process can then take over to drill down to the root cause of the issue.
To support this, DC RUM provides not only near real time performance monitoring, but also convenient and efficient access to historical packet level data (also referred to as back-in-time data). When a subtle or intermittent problem occurs, the network administrators can quickly go back in time to discover the root cause. This verification process typically involves checking the end user's recent network activity and looking up any operations recently run by that host, to discover, for example, why the network is slow for that user, or what is causing high RTT, or what is causing packet drop.
Compuware APM enables network and infrastructure operators to immediately isolate faults that affect application performance and end-user experience across web, middleware, database, and network tiers. This end-to-end view encompassing detailed network, client, and server fault domains streamlines the process of identifying and isolating a problem's root cause, and is now supplemented by the ability to initiate, collect, and analyze packet trace data in the context of APM reports.
Using the Endace high-speed lossless data acquisition architecture, you can now automate the collection, retrieval, and display of trace file level data from both the EndaceProbe and Compuware AMD by selecting the relevant user as reported in the CAS reports and analyzing the trace data in Transaction Trace Analysis (TTA) or in third-party analyzers such as Wireshark.
Also Included in This Release
Additional Improvements and Changes
SMB 3.0 decode
TTA for SMB 3.0 traces decodes a transaction as SMB3.
SAP RFC decode
TTA for a SAP task now shows one thread instead of many for a trace.
Transaction Trace Analysis Documentation on the APM Community
As an alternative format to the installed product helps and downloadable PDF books, an online version of the Transaction Trace Analysis documentation is now available on the APM Community in a native wiki format. This online resource contains the latest documentation updates and provides you with the ability to quickly search across the entire Transaction Trace Analysis documentation set. For more information, refer to the APM Community Transaction Trace Analysis documentation.
Table 1. Transaction Trace Analysis 12.2 Resolved Issues
None ofsettings have been preserved after TTA 12.0.GA to 12.1 upgrade.
“Internal error” received when trying to open a trace in Performance Overview.
Transaction Trace Agent installation is interrupted when a later version of Microsoft Visual C++ is already installed.
“Transaction Trace Analysis has experienced unhandled exception. The application will shutdown. Detail info has been written to log file.” error when working in trace.
Packet Trace Details: IPv6 over MPLS is not decoded.
Packet Trace Details: Ethernet frame over MPLS is not recognized and decoded.
“Open in Wireshark” menu item enabled when no Wireshark is installed.
Expert Guide Editor does not handle documents containing empty pages.
Console crashes during trace import.
Local machine registry settings not preserved after upgrade.
Thread View: Cannot change order or invisible columns.
Thread View: Misleading number of threads in column header.
Transaction Trace Agent may crash when used in UCM after attended capture.
Windows Authentication should be default for console installation.
Fatal errors seen after starting Red Hat Linux Transaction Trace agent.
Simple Capture Utility "fatal error" in log file.
copies NSD rate column with wrong values.
Application tree does not get refreshed after renaming baseline task.
Copying large number of packet descriptions from Packet Trace may cause TTA to freeze.
Transaction Trace Agent is not running after installation in a certain Windows configuration.
Help button does not work on Select Transaction Trace Analysis Agents window in TTA Agent Manager.
Table 2. TTA Known Issues
If you modify an existing TTA installation by choosing Uninstall/Change from the “Control Panel\Programs\Programs and Features” list:
the TTA console and Trace Trimmer fail to load and initialize properly. A capture driver is erroneously removed during this installation modification.
During Windows upgrade to Windows 8.1, Internet Explorer is upgraded to Internet Explorer 11. With this release, Enhanced Protected Mode is enabled by default, and BDC (which requires Enhanced Protection Mode to be disabled) fails to load and is marked as incompatible in the Manage add-ons dialog.
To use BDC in Internet Explorer 11, you must turn off Enhanced Protected Mode in Internet Explorer:
RTP calculations and configurations are not visible on reports:
This problem occurs if you set up a proxy server for your browser but you do not select Bypass proxy server for local addresses.
DT 00000 46418
Cannot change password for SQL database user delta when CAS or ADS and Trace Trimmer are installed on the same machine
If you install TTA with Trace Trimmer on the same machine as a CAS or ADS installation, you cannot change the password for SQL database user “delta”.
DT 00000 74124
Trace Trimmer does not start (error message “Failed to initialize Trace Trimmer”)
Workaround: Run Trace Trimmer on an account with elevated privileges (run as administrator) and recreate the Trace Trimmer database.
DT 00000 71929
DT 00000 71923
On Windows Vista, installation fails or is incomplete.
On a Windows Vista machine that has not received all current critical Windows updates, installation may fail or be incomplete. For example, a firewall exception may not be created for the agent, or SQL Server Express may not be installed.
You should apply all current critical Windows updates to the target Vista machine and then reinstall the TTA software on the target machine.
DT 00000 68071
Agent crashes with “/usr/lib/dld.sl: Unresolved symbol: getaddrinfo (code) from /opt/avagt/avagt” message displayed.
When this occurs in an HP-UX environment, it indicates that the OS on the agent machine needs to be updated to maintain compatibility with libpcap updates.
Apply all available operating system patches that affect usr/lib/dld.sl on the agent machine.
DT 00000 67931
When filtering is applied to a UNIX agent, “Frames seen” always equals “Frames”.
Starting with TTA 11.7, when traffic filtering is applied to a UNIX agent, Frames Seen and Frames in the Capture window are always the same. This is because filtering is now performed as soon as possible, on the kernel level, by the packet capture driver, which then passes to the application only those frames that satisfy the filter. The advantage of this approach is that traffic filtering performance is greatly improved, and it is now possible to avoid potentially massive packet drops on an underperforming machine just by applying a strict filter. Although you cannot see how many frames were discarded because of the filter, this behavior is in alignment with other libpcap-based software such as tcpdump.
DT 00000 67496
SQL Server 2005 Management Studio distributed with TTA is not Windows 7 compatible.
On a 64-bit Windows 7 machine, problems were observed when installing the SQL Server 2005 Management Studio that is bundled with TTA and installed with the TTA setup application.
Workaround: Install the 64-bit “SQL Server Management Studio Express Service Pack 2” available from Microsoft.
DT 00000 64693
NIC sometimes is not visible (so no capture is possible) after TTA console update on Windows Vista 32-bit edition.
After updating TTA from an earlier version to TTA 11.7 on a Vista 32-bit platform, TTA sometimes fails to recognize any NIC the first time you run the updated console. This problem appears to be related to user rights management.
This workaround is not required in subsequent TTA sessions.
Compuware APM Database Utility displays “The file mscomctl.ocx was not found.” and fails to start in some configurations
When running the Compuware APM Database Utility on a Windows XP or Windows 2003 Server machine, if the user does not have administrative rights a Windows Common Controls ActiveX Control window will display the message “The file mscomctl.ocx was not found.” and the Compuware APM Database Utility will fail to start.
Workaround: Run the Compuware APM Database Utility as an administrator or on an account with administrative rights.
Message “This program has known compatibility issues” when installing Microsoft SQL Server 2005 can be ignored.
When installing TTA on a 32-bit Windows 7 machine, if you choose to install Microsoft SQL Server Express, the Program Compatibility Assistant will display the message “This program has known compatibility issues.”
These issues do not affect TTA. Click Run program and continue with the installation.
User option settings may revert to default settings during upgrade.
This may occur when upgrading TTA on a non-administrator account. Your database will not be affected.
On 64-bit systems, Agent Manager cannot change agent promiscuous mode
There are two workarounds:
“This task does not have a trace”
A TTA database name cannot contain anything but numbers, letters, or underscore.
If you give a TTA database a name containing any characters other than numbers, letters, or the underscore character, you will receive the message “This task does not have a trace” when you try to access a task.
Workaround: Use Microsoft SQL Server Management Studio Express to give the database a new name that conforms to the following rules:
After the database name change, reprofile all tasks in the database. In Expert Guide, select.
TTA database migration fails if the database name has invalid characters.
If you attempt to migrate a version earlier than 11.5 of the TTA database (usingor ) to TTA 11.5, the migration will fail if the database name has invalid characters.
Workaround: Use Microsoft SQL Server Management Studio Express to give the database a new name that conforms to the following rules:
VMware and TTA.
With TTA (console, agent, and Simple Capture) running on VMware ESX(i) 3.5 (or later) or VMware Workstation 6.5 (or later), you can now configure the driver to read the current time from the underlying host machine instead of depending on the (virtualized) operating system's time, which may be unsynchronized with real time.
Installing TTA using the silent install option on Windows Vista, Windows 7, or Windows 2008
On a Windows Vista, Windows 7, or Windows 2008 machine, when installing TTA, the User Account Control (UAC) functionality may prevent installation. This may occur when you have not made Compuware a trusted publisher and you attempt a silent installation or an installation without administrator privileges.
A TTA Agent installation started directly from the msi file or using silent installation must be performed with elevated privileges. To do so, right-click on cmd, choose Run as, and run it an an administrator. From that command line, you can then execute msiexec /I <properPath>\Transaction Trace Agent to install the software.
You can use one of the following methods to install the driver manually:
In either case, [INSTALLDIR] is the product directory, which by default is:
C:\Program Files\Compuware\Transaction Trace Analysis\
To prevent this problem, however, you should install a Compuware certificate in the Trusted Publishers certificate store before installing the agent. The certificate file Compuware.cer is located in the Transaction Trace Agent Installer folder in the TTA distribution. The certificate can be distributed to multiple remote machines using Microsoft Group Policy management or similar tools. This certificate has already expired, but it was used to sign the driver before the certificate expired, so it can still be used to prevent the Compuware APM packet capture driver installation problem. For more information, see Installing a Compuware Certificate.
Trace Trimmer installation occasionally fails.
Trace Trimmer normally is installed automatically as part of a TTA installation. Occasionally, the Trace Trimmer portion of the installation fails. If this occurs, uninstall TTA and then restart the TTA installation from the beginning.
Browser Data Collection (BDC) is not available for 64-bit Internet Explorer.
Browser Data Collection (BDC) does not work in the 64-bit version of IE. To use BDC on a 64-bit operating system, run the 32-bit version of IE.
BDC is not enabled by default on Windows 2008 Server.
To enable Browser Data Collection (BDC), the TTA installer adds a browser extension to Internet Explorer. By default, Windows 2008 Server does not allow such third-party browser extensions. To allow the BDC extension (and other third-party browser extensions) to operate:
Content is blocked by Internet Explorer Enhanced Security Configuration
In Windows Server 2003 or Windows Server 2008, you may see an IE window that states:
Content within this application coming from the web site listed below is being blocked by Internet Explorer Enhanced Security Configuration. about:security_AppVantage.exe
If so, you should add TTA to IE's list of trusted sites:
TTA cannot properly import traces with sliced frames.
TTA will not properly import third-party traces that don't have a full payload. If you use a third-party sniffer, you need to save traces with the whole packet payload.
Memory is not released until closing TTA.
When you open a view for any task, a certain amount of memory is allocated to TTA. When you close the view, not all memory is released. If you run TTA for a long period without closing it, memory allocated to it will rise and may affect application and operating system performance. Close TTA to release the memory.
Some TTA report features may not be viewable in web browsers other than Internet Explorer
TTA reports generally are viewable in popular web browsers such as Internet Explorer, Firefox, and Chrome, but some report features in some reports may not be viewable in some browsers other than Internet Explorer.
In order for TTA to function properly on a non-US regionalized machine, these two settings on the machine must match:
These can be set through the Windows Control Panel. If the two settings do not match, local language characters may not appear correctly in the views.
Save Database as File and Open Database from File functions
The GttaLogin has limited access rights. It only opens database files that you saved on the same machine. If you want to open a database file saved to another machine, GttaLogin does not have the right to convert the internal SID of another machine to this machine, so it displays a warning message to tell you that GttaLogin cannot open the database. However, the sa login opens database files saved to another machine. Compuware recommends using the sa login when you want to open database files that were saved to another machine.
NIC array support
Automatic Latency Detection and syncing do not work for NIC arrays. NIC arrays are separate NICs working together. NIC arrays are different than Team NICs.
Cancel button on Status Bar
The Status Bar Cancel button does not work. The Cancel button is used to cancel profiling.
DT 00000 78323
TTA Agent installation from an ISO image causes an error.
When Transaction Trace Agent is installed from an ISO image, the following error message is displayed:
SetFileAttributes() failed on file: "D:\TRAN#WV~\TRAN#~72\vbrun60.inf"
To install the agent correctly, you should copy the ISO image to a local drive or a network drive and then install the agent from that copy.
For a complete list of system requirements, see Transaction Trace System Requirements.
Customer Support Information
Contacting Customer Support
USA and Canada: 1-800-538-7822 or 1-313-227-5444.
All other countries: Contact your local Compuware office. Contact information is available at http://go.compuware.com.
You can report issues via the Report and Track Calls tab on the FrontLine home page.
- Customer Support
- Compuware Corporation
- One Campus Martius
- Detroit, MI 48226-5099
You can find product documentation, forums with product experts, product fixes and more information at the Compuware APM Community. You must register and log in to access the Community.
To access the Compuware website, go to http://www.compuware.com. The Compuware site provides a variety of product and support information.
Reporting a Problem
When contacting APM Customer Support, please provide as much information as possible about your environment and the circumstances that led to the difficulty.
You should be ready to provide:
Client number. This number is assigned to you by Compuware and is recorded on your sales contract.
The version number of the AMD, report servers, and RUM Console with RUM Console Server.
In the report server GUI, select, or .
In the RUM Console GUI, selectand select an AMD from the device list to determine the version.
RUM Console and RUM Console Server
In the RUM Console GUI, select.
In the TCAM GUI, select.
Environment information, such as the operating system and release (including service pack level) on which the product (AMD, report server) is installed, memory, hardware/network specifications, and the names and releases of other applications that were running.
Problem description, including screen captures.
Exact error messages, if any (screen captures recommended).
Whether or not the problem is reproducible. If it is, include a sequence of steps for problem recreation. If it is not, include a description of the actions taken before the problem occurred.
A description of the actions that may have been taken to recover from the problem, and their results.
Debug information for specific components obtained from RUM Console.
Information about the RUM Console itself.
To export all the information, from the RUM Console menu, selectin the RUM Console.
Information about the report servers.
To export the information for a specific ADS or CAS, select Export diagnostic information from the context menu of the particular device., and choose
Probe config. and samples
Select this option to include diagnostic information on data collectors attached to the report server.
Select this option to include installation information logged and saved on the server.
SQL trace logs
Select this option to include trace logs of SQL queries.
Enter the destination path and file name for the diagnostic package file.
Information about the AMD.
To export the information for a specific AMD, select Export diagnostic information from the context menu of the particular device., and choose
Include data files
Select this option to include fragments of traffic data.
Begin and End
Select this option to include the time range of the monitoring data to be included with the diagnostics.
Data file filter (RegEx)
Use this regular expression filter for monitoring data files generated during the defined time range.
Enter the destination path and file name for the diagnostic package file.
Information from the TCAM
Include the System Event log of the machine where the TCAM is operating.
Include the TCAM logs which by default are stored in:
C:\Documents and Settings\All Users\Compuware\VTCAM (for Windows Server 2003)
%programdata%\Compuware\VTCAM (for Windows Server 2008 and later)
Compuware values your comments and suggestions about the Compuware APM products and documentation. Your feedback is very important to us. If you have questions or suggestions for improvement, please let us know.
Get Support File
Get Support File is an Transaction Trace Analysis function for gathering various log files and system reports into one zip file that can be sent to support when you are debugging an Transaction Trace Analysis installation.
When you are troubleshooting an Transaction Trace Analysis console or agent installation, you can use the Get Support File function to automatically gather information about the systems involved. This information is packaged in one compressed file that you can send to your Compuware representative for analysis.
There are two ways to use Get Support File to gather system information about a machine on which you have installed the Transaction Trace Agent:
If you run Get Support File directly from an agent machine, Get Support File will generate a system report focused strictly on that machine. For more information, see Agent File Contents.
If you run Get Support File from the Transaction Trace Analysis console machine, Get Support File will generate a system report on the console machine and on any or all of the selected Windows and Unix machines running the Transaction Trace Agent. The resulting report will concern the console machine and all selected agent machines. For more information, see Console File Contents.
You could gather most of this information yourself by locating the right log files, running the right system reports, and zipping all of the results together, but Get Support File makes the process easier and faster.