APM .NET - Avicode conflicts with the .NET agent

Products

• DX Application Performance Management

Issue/Introduction

After a successful Application Performance Management .NET Agent install or manual deploy of .NET Agent No Installer files, the agent is failing to execute and show the expected application metrics.

Environment

DX APM .NET

Resolution

Below are steps taken to identify the .NET agent conflict:

1) Check environment variables: profiling is enabled and our GUID is specified:

2) Used ProcMon to find out which w3wp is running the app pool to be instrumented.

3)Right-Clicked that w3wp.exe in ProcMon to look at its environment and discovered that the COR_PROFILER GUID it is using is NOT the same as the APM .Net agent GUID:

4) Looked in a command prompt to verify what the COR_PROFILER GUID was set to, and see that in the environment variables it is set to our APM GUID:

5) Here’s a comparison of the two GUIDs:

6) Searched the registry for the unknown GUID to find out what it is:

7) More searching in the registry for this GUID revealed that it is defined in IISADMIN’s startup environment, thus overriding our configuration in the System environment:

 

Conclusion:

AVIcode .NET Application Monitoring is a subsidiary of Microsoft.  AVIcode technologies enable in-production, always-on root-cause monitoring and analysis of Microsoft .NET Framework-based applications.

The AVIcode suite of software is available exclusively in connection with the purchase of licenses for the following products:

System Center Server Management Suite Enterprise (SMSE)System Center Server Management Suite Datacenter (SMSD)Enrollment for Core Infrastructure Server Suite EnterpriseEnrollment for Core Infrastructure Server Suite Datacenter

You should contact MS for instructions about how to properly remove Avicode profiler.

Below instructions provided by one of our customer that was affected by this issue:

“Deleting the Environment Reg Key from the following places and performing and IIS reset has resolved the issue of the Wily CA .Net agent not reporting it’s .net Web application traffic to the MOM.

Hey_Local_Machine\System\ControlSet001\Services\IISADMIN

Hey_Local_Machine\System\ControlSet001\Services\W3SVC

Hey_Local_Machine\System\ControlSet001\Services\WAS

Hey_Local_Machine\System\ControlSet003\Services\IISADMIN

Hey_Local_Machine\System\ControlSet003\Services\W3SVC

Hey_Local_Machine\System\ControlSet003\Services\WAS

Hey_Local_Machine\System\CurrentControlSet\Services\IISADMIN

Hey_Local_Machine\System\ CurrentControlSet \Services\W3SVC

Hey_Local_Machine\System\ CurrentControlSet \Services\WAS

 

This resolved the cor_profiler conflict issue

Additional Information

https://knowledge.broadcom.com/external/article/111638/apm-introscope-net-agent-troubleshootin.html