How to identify and resolve conflicts between other APM products and the APM Insight .NET agent?
If you are experiencing any of the issues mentioned below and you suspect that another APM product is interfering with the Applications Manager .NET agent, you can follow the steps given in this article to troubleshoot and fix the issues:
1. The .NET monitor is not getting created even after the .NET agent installation is complete.
2. The .NET monitor is not receiving data from the application.
Note: Before you proceed to troubleshoot, ensure that the APM Insight .NET agent has been installed.
Follow the steps given below to identify and resolve the conflict between the other APM product and the APM Insight.NET agent:
Profilers that commonly conflict with Applications Manager's .NET agent
Environment variable of Applications Manager's .NET agent:
{989D151B-3F31-482E-926F-2E95D274BD36}
Other APM profilers | Profiler CLSID |
AppDynamics | AppDynamics.AgentProfiler |
New Relic | {71DA0A04-7777-4EC6-9643-7D28B46A8A41} |
Dynatrace | {DA7CFC47-3E35-4c-4e-B495-534F93B28683} {B7038F67-52FC-4DA2-AB02-969B3C1EDA03} |
IntelliTrace | {2AA1AA98-2CAA-4FCF-86CE-EFA007737E83} |
Microsoft Application Insights | {324F817A-7420-4E6D-B3C1-143FBED6D855} |
SCOM APM | {AD5651A8-B5C8-46ca-A11B-E82AEC2B8E78} |
JetBrains dotCover | {9AA5D52F-37E2-487D-AAEC-727478B8BDB5} |
Identify the conflicting APM product using Event Viewer
- Open Event Viewer and navigate to Windows Logs > Application.
- Click the event with the source .NET Runtime to check the Profiler CLSID of the conflicting APM product.
The Event Viewer will be installed on your Windows machine by default.
Identify the conflicting APM product using Process Explorer
- Install and open the Process Explorer.
- Select w3wp.exe, go to the Environment tab, and look for the COR_PROFILER variable to identify the conflicting APM product.
Note: Please find the link to download and install the Process Explorer in your system.
Resolve the conflict
- You must uninstall the other APM product because Microsoft restricts using multiple profilers on the same machine.
- Perform IIS reset.
- Now, you can restart your application and make some transactions.
- Once the application is up and receiving requests, you can view the monitor under APM > Your APM Insight Application/Instance in the AppManager
- If you click the application name, you can also view the metrics and the corresponding graphs.
New to ADSelfService Plus?
Related Articles
Uninstrumented Block of Code - APM Insight
In the traces tab --> Slowest Method Calls and Count we show if you find Un-instrumented block of code the reason is as follows: Basically, What is un-instrumented block of code in APM Insight? By default, APM Insight agent monitors known frameworks ...Self monitor Applications Manager using APM Insight Java Agent
Applications Manager is built with Java, hence we can monitor it using APM Insight Java Agent to measure it's performance continuously, which can be very much useful. Setting up APM Insight Java Agent Follow the below steps to download and set up the ...Troubleshooting steps to identify and resolve the `System.AccessViolationException` crashing issue while monitoring the .NET applications
Understanding Our .NET agent instrumentation may encounter issues with specific versions of framework methods in your .NET applications, resulting in disruptions to the application monitoring process. If you encounter the exception ...How to rename an existing APM - Java agent application's monitor?
In Applications Manager's APM(Application Performance Monitoring) doesn't support renaming applications/monitors from the web client. However, the application name of an existing application instance can be renamed in the `apminsight.conf` file and ...APM Insight agent log paths
Folder path to view .NET agent logs .NET agent logs can be found only in the common application folder in Windows (usually under C:\ProgramData\ from Vista onwards, which is a hidden folder). Check the following folder paths: For agents v2.5.4 and ...