When profiling an ASP .NET web application, the profiling may yield no results. When examining the application event log, the following entry is shown:

Event Type: Error
Event Source: .NET Runtime
Event Category: None
Event ID: 1022
Date: 14/10/2008
Time: 14:38:17
User: N/A
Computer: MINE
Description:
.NET Runtime version 2.0.50727.1433 - Failed to CoCreate profiler. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

One possible cause for this error is that the ASPNET user does not have read permissions to the ANTS Profiler program directory. The ASP .NET worker process needs to load ProfilerCore.dll (RedGate.Memory.Core.dll for memory profiler) in order to send profiling metrics from the worker process to ANTS Profiler.

By default, ASP .NET web applications run under the local machine's ASPNET user account in IIS version 5. This is configurable, however, in the processModel section of the machine.config file. For example, if the ASP .NET web application uses the .NET 2.0 runtime, the location for the configuration file will be "%systemroot%\microsoft.net\framework\v2.0.50727\config\machine.config" If the processModel is set to "Autoconfig=Yes", then ASP .NET is also using the ASPNET account.

In IIS version 6 and 7, the web application pool's Windows user is configurable. It's normally the user that runs the application pool (for instance NT AUTHORITY\NETWORK SERVICE).

Once you have determined the correct account that runs ASP .NET code, you may use Windows Explorer to grant READ permissions to the Profiler installation folder (%programfiles%\red gate\ants profiler x).