How can we help you today? How can we help you today?

ants profiler couldn't attach to the process you selected, because another profiler is already attac

- downloaded trial version 8/7
- started profiling by attaching to process
- checked back in on the profiling session and saw no UI
- cannot restart profiling due to the above error
How can I overcome this ?

Note: no registry (ala 2017) suggestions please
syackey
0

Comments

6 comments

  • Russell D
    Well if the profiler has crashed mid run then it won't have cleaned up after itself so I would look in the registry first for the COR flags I'm afraid.
    Russell D
    0
  • syackey
    Neither COR_ENABLE_PROFILING nor COR_PROFILER is in the registry.
    I used regedit and then find starting at ALL of the root items for the search.
    I'm thinking that should have found one/both if they are in there.
    syackey
    0
  • Russell D
    What other, if any, profilers/test harnesses have you got running?
    Russell D
    0
  • Jessica R
    Hi @syackey,

    If you use Process Explorer, run it as admin, right-click on the process you need to profile, and then click on the Environment tab, what are the environment variable values there? 

    For example:

    Jessica R
    0
  • syackey
    Thanks for taking the time to respond.
    Here is the environment. I don't think the 'cor' items are in there.

    syackey
    0
  • Jessica R
    Thanks @syackey!

    Ah, how odd though that the profiler variables aren't set. Can you please check if there's any related errors in Event Viewer>Windows log>Application?
    Jessica R
    0

Add comment

Please sign in to leave a comment.