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 cannot find usable .pdb files for your application
• ANTS Performance Profiler cannot find any code to profile
• ANTS Performance Profiler cannot read a performance counter

This page describes how to resolve these problems.

If your results are only missing SQL or HTTP call profiling data, see Troubleshooting SQL and HTTP call profiling.

You may also receive no results, or incomplete results, if the application you are profiling crashes. For more information, see Troubleshooting application crashes.

ANTS Performance Profiler cannot find usable .pdb files for your application

See Troubleshooting .pdb problems.

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.

  It is not possible to profile remotely using ANTS Performance Profiler. Ensure 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 any method that contributes less than 1% of your application's total CPU time. To display all profiled methods, clear the 'Hide insignificant methods' checkbox.

• Your application contains no managed code.

  Line-level and method-level timings are not available for unmanaged code. If all your application's code is unmanaged, it cannot be profiled.
  Method-level timings for unmanaged methods can be shown if the methods are declared with extern within your managed code.

For web applications and WCF services running in IIS:

• The application is using an unprofiled port.

  If you are profiling on an unused port, configure your application to communicate on the same port that you selected on the Application Settings dialog 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 Server 2008 and Windows 7: see How to rebuild performance counters (MSDN)

Contacting Redgate support

If you are still unable to resolve this 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.

  More information about locating log files for ANTS Performance Profiler can be found here.