The .NET Common Language Runtime (CLR) only allows one profiler to access the profiling API of a process at any given time. If another profiler is installed on the system, the New Relic profiler will not instrument any applications.
To avoid a profiler conflict, fully remove the other profiler from the environment, then ensure the IIS registry keys or system environment variables have been restored.
Exception: For conflicts with Microsoft's System Center Operations Manager (SCOM), follow the troubleshooting procedures specifically for SCOM.
Here are some commonly reported profiler conflicts. This is not an exhaustive list of .NET profilers, as any program that uses the .NET profiling API may cause conflicts with the New Relic .NET profiler.
Diagnostic Policy Service
Microsoft App Insights
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.