dotTrace 4 Performance won't start profiling web applications running under IIS

There are several reasons why dotTrace 4.x Performance is sometimes unable to profile web applications under Internet Information Services (IIS). These include lack of permissions over dotTrace bin directory; conflicts with other profilers such as YourKit; and firewall/antivirus activity.

For details on working around this issue, please read this dotTrace Community post.

Please sign in to leave a comment.

Have more questions?

Submit a request