When you click Start Profiling for an ASP.NET web application (IIS), profiling may not start, and a "Cannot start IIS" error may be displayed. This can indicate that:
This page describes how to fix these issues.
ANTS Performance Profiler starts the IIS application pool with permissions inherited from the currently logged-in user account, rather than using the IIS application settings.
To fix this issue:
The error may also occur when using "Manually specify ASP.NET account details". Check that the specified account is a valid user, has administrator privileges, and has read access to %ProgramFiles%\Red Gate\ANTS Performance Profiler 8\RedGate.ProfilerCore.dll and %ProgramFiles%\Red Gate\ANTS Performance Profiler 8\X64\RedGate.ProfilerCore.dll
If the bindings in IIS have been changed from the default, ANTS Performance Profiler may be unable to resolve your site's hostname. This error message may be shown:
Couldn't determine the IIS Site associated with URL 'http://< URL>:port'. Please check that the URL is serviced by the instance of IIS running on this machine. |
To fix this issue:
This is usually caused by enabling line-level timings with code using the SecurityTransparent attribute. For more information, see Profiling SecurityTransparent and partially-trusted assemblies.
IIS can fail to start if ANTS Performance Profiler encounters a conflict with another performance profiler. We recommend uninstalling other profilers while profiling with ANTS Performance Profiler. You can tell if another product is profiling IIS using the free Microsoft Process Explorer (download here):
If you had ANTS Performance Profiler version 7.0 and installed the early access build of the continuous profiling tool, an IIS module installed by the continuous profiler may be preventing profiling. To re-enable other profilers with IIS, uninstall the IIS Profiler Module:
If you still can't fix your problem using the information in this topic, please contact support, and supply as much information as you can, including: