Troubleshooting missing results
Published 14 May 2018
ANTS Performance Profiler may show no profiling results, may show no results for some methods, or may show the error message "The profiler did not find any methods with source code", when:
- ANTS Performance Profiler can't find usable .pdb files for your application
- ANTS Performance Profiler can't find any code to profile
- ANTS Performance Profiler can't read a performance counter
- You are profiling a Windows Store Application with trivial methods
This page describes how to fix these problems.
If your results are only missing SQL or HTTP call profiling data, see Troubleshooting SQL call and HTTP request profiling.
If the application you are profiling crashes, you may also receive no results, or incomplete results. For more information, see Troubleshooting application crashes.
ANTS Performance Profiler cannot find usable .pdb files for your application
ANTS Performance Profiler cannot find any code to profile
ANTS Performance Profiler may be unable to find your code if:
- The application you are profiling is not installed on the same computer as ANTS Performance Profiler.
You can't profile remotely using ANTS Performance Profiler. Make sure that the profiler is installed on the computer running the application you want to profile.
- You are profiling with 'Hide insignificant methods' selected.
This setting hides methods that contribute less than 1% of your application's total CPU time. To display all profiled methods, go to Tools -> Advanced Options, and clear the Avoid profiling extremely trivial methods checkbox.
- Your application doesn't contain any managed code.
Line-level and method-level timings aren't available for unmanaged code. If all of your application's code is unmanaged, it can't be profiled.
Method-level timings for unmanaged methods can be shown if the methods are declared with
externwithin your managed code.
For web applications and WCF services running in IIS:
- The application is using an unprofiled port.
If you're profiling on an unused port, configure your application to communicate on the same port that you selected on the settings screen in ANTS Performance Profiler. By default this is port 8013.
For more information, see Profiling ASP.NET applications running on IIS.
ANTS Performance Profiler cannot read a performance counter
If any performance counters are missing from profiling results, rebuild the counters and try profiling again.
To rebuild performance counters:
- For Windows 2000, Windows XP and Windows Server 2003: see How to manually rebuild Performance Counter Library values (MSDN)
- For Windows Vista, Windows 7, and Windows Server 2008 and later: see How to rebuild performance counters (MSDN)
Profiling Windows Store Applications with trivial methods
When profiling Windows Store Applications, some methods don't appear in profiling results because ANTS Performance Profiler ignores trivial methods for Windows Store Applications.
A method is trivial if it is smaller than 192 bytes of IL, doesn't contain any branches or loops, and doesn't contain any calls to other methods.
Contacting Redgate support
If you still can't fix your problem, contact Redgate support. Ensure that you include:
- the version of ANTS Performance Profiler you are using
- your computer's operating system
- the steps you have already tried
- any error messages ANTS Performance Profiler has generated, including any in the log files