There is already a profiler attached to this process

kshyju

I am trying to run the current version of ANTS perf profiler against a w3wp process(which is my ASP.NET web app). I selected the correct w3wp process(I found out the correct process id using appcmd list wp command). But when i do that, i get this error message "There is already a profiler attached to this process".

I am running only one instance of the profiler.



Is there any way i can know which profiler process is already attached to this process ? Or how to proceed further ?

Env : Win Server 2012 R2

chaituprince

kshyju wrote: »

I am trying to run the current version of ANTS perf profiler against a w3wp process(which is my ASP.NET web app). I selected the correct w3wp process(I found out the correct process id using appcmd list wp command). But when i do that, i get this error message "There is already a profiler attached to this process".

I am running only one instance of the profiler.



Is there any way i can know which profiler process is already attached to this process ? Or how to proceed further ?

Env : Win Server 2012 R2

Same is the case with me... Any solution yet?

Russell D

This normally means that some system flags on your system are set incorrectly, or they've been modified by another program. ANTS needs to set the COR_PROFILER and COR_ENABLE_PROFILING environment variables.

There are some tools that will always automatically hook into your application and do this (for example, New Relic does this, and its possible to setup the VS profiler to do this). There could also be leftover environment variables from a previous ANTS profiling session if one did not end cleanly.

You can try searching the registry for the above flags and deleting them, although if you use New Relic for example this can insert these flags automatically, and you'd need to disable the test automation (as I believe it's usually this) in NR.

xing

I experienced the same problem, but could not find the COR_PROFILER and COR_ENABLE_PROFILING keys in Registry

fffgggfee

You won't believe it, but I have the same problem