Although SpeedTrace does profile Remote Desktop sessions, trial versions do not allow the use of this feature. However, if you are interested in RDC, please contact us.

If the settings are changed to "1" even though you have modified them, SpeedTrace has found a lack of hard disk space. Please be sure to provide at least 1GB free space or change to a different unit by using the "Output Storage Directory" field.

Due to the new workspace management in 3.1, in order to recover the workspace used in previous versions, it is necessary to select Open Workspace from the File menu and to browse to the folder were projects are saved (Usually: P:\Documents and Settings\[your user]\Application Data\SpeedTrace Pro 3.0\Config\Projects\). Select All Files (*.*) from the Files of type drop down list and locate the file named: "Workspace.xml". Open to load your previous workspace.

It is mandatory for users to have 'administrator privileges'. SpeedTrace needs these privileges in order to perform the process of creating projects and recording .NET applications.

The whole trace is kept in memory until the profiling and tracing is stopped. This is necessary to minimize overhead. Hard disk access is slower than writing to memory, however, you can use the 'Save to disk' option if you want to profile and trace large applications.

You can set the size of the tracing buffer in the SpeedTrace user interface. Switch to the 'General' tab and use the input field 'Max. Buffer-Size' You can also choose between a 'Limited' and 'Wrap Around' buffer mode (available only in Pro version). The second option will force SpeedTrace Pro to overwrite the buffer whenever the size limit is reached. The Save to disk option is another alternative to adjust the memory usage. 'Max. Trace File Size (MB)' sets the maximum size that can be written to the disk and 'Write Cache Size (MB)' sets the maximum size of temporarily stored data until it can be permanently written to the disk.

In the limited buffer mode, profile and trace recording may stop before your tested application carries out the functions and methods from which you want to get information. In the wrap-around mode, recording is not stopped, but the buffer is always overwritten. Depending on the buffer size and profiling time, the functions and methods that were carried out at the beginning might not be present within the profile and trace results because the data was overwritten. The Save to disk option will help you to profile and trace larger applications, since the buffer size constraints no longer apply. 'Max. Trace File Size (MB)' sets the maximum size that can be written to the disk and 'Write Cache Size (MB)' sets the maximum size of temporarily stored data until it can be permanently written to the disk.

If the buffer size is set larger than the available memory, SpeedTrace will readjust size automatically according to your available memory. The Save to disk option is another alternative in order to control memory usage. 'Max. Trace File Size (MB)' sets the maximum size that can be written to the disk and 'Write Cache Size (MB)' sets the maximum size of temporarily stored data until it can be permanently written to the disk.

Make sure that enough memory is available for profiling and tracing. Shut down all applications that are not involved in the tracing process. To work properly with SpeedTrace Pro we suggest at least 1GB of physical memory. Use Recording Filters and Triggers to reduce recording data (available only in Pro version). Try to focus on specific methods and name spaces you are really interested in. This will also increase clarity since your analysis is not excessively loaded with system calls you cannot optimize at all. An alternative solution is to use the Save to disk option. It will help you to optimize your profiling and tracing results by setting proper values within the 'Max. Trace File Size (MB)' and 'Write Cache Size (MB)' fields.

Yes, SpeedTrace Basic and Pro versions run on 32/64 bit x86 processor architecture as long as it runs in a 32 bit operating system environment.

No, at the moment SpeedTrace Pro does not support 64 bit operating systems.

In order to use SpeedTrace for this framework, you have to create a configuration file. Please refer to Known Issues for more details (Support for .NET Framework V2.0)

Check whether the specified process name is specified correctly and the tracee process has been started. Check the Tracee environment, see Known Issues

In order to start recording, SpeedTrace Pro must shut down the service and restart it. This is only possible if you have sufficient access rights. In some cases it might be possible to run a service in the limited user account to prevent this problem.

In order to start recording, SpeedTrace Pro must shut down the webserver and restart it. This is only possible if you have sufficient access rights. Another solution is using the Cassini webserver included in Visual Studio. It doesn't run as a service and therefore does not require special access rights.

Open the trace profile and have a look at the Functions view, search for the desired function to verify whether the given function (trigger/filter) name matches the full qualified name of the function. You may copy the complete function name from the TraceAnalyzer and use it for trigger/filter settings.

Ensure thet SpeedTrace Pro is recording. Check your Filter settings (only available in Pro version). In case of using include filters (available in Pro version), try to disable the include filter and repeat the recording process. If the trace was not empty, then please read troubleshooting item Function name mismatch.

Refer to "How To: Reduce the Amount of your Recorded Data" in the SpeedTrace Pro User Guide in order to focus on specific function calls (available only in Pro version). Moreover, Save to disk option is another alternative in order to record every single required function. 'Max. Trace File Size (MB)' sets the maximum size that can be written to the disk and 'Write Cache Size (MB)' sets the maximum size of temporarily stored data until it can be permanently written to the disk.

Decrease the Trace Buffer size, use filters & triggers (available only in Pro version). Refer to "How To: Reduce the Amount of your Recorded Data" in the User Guide (only available in Pro version) or use the Save to disk option.

It is mandatory for users to have 'administrator privileges'. Using SpeedTrace requires these privileges in order to perform the process of creating projects and recording .NET applications.

If there are any annoying problems that can not be solved, please restart SpeedTrace Pro and send us a detailed report. We will appreciate your feedback.