Troubleshoot: APM+ for .NET

This guide is intended to help users who are experiencing problems trying to configure their application to send APM data to Retrace.  If you haven’t already, check out our documentation on installing Retrace for your appropriate application framework.  This guide will provide you with a checklist of items that will help troubleshoot what is going on.  If you are still not successfully receiving APM data, please contact us at [email protected] and we will do some further investigation.

Restart IIS 

The first thing to always try if you’re not receiving APM+ data is to restart IIS. You can either restart the IIS service as normal, or toggle the “Enable/Disable APM+” button in the Server Settings panel of the server you’re having problems with. The Retrace profiler hooks into IIS when it initializes.

Update Stackify Agent

Ensure the Retrace agent is up to date. Either install the latest version for your operating system, or easily update the the agent from the Server Settings dialog. 

Examine Windows Event Logs

In the Windows Event Viewer look for Application events from the Retrace Profiler:

  1. profiler – A .NET CLR profiler is loaded. Verify the CLSID is Retrace’s {68130646-C19E-459E-8BF4-5137ED7B3FD7} (for APM 2.0) or {DE70E25C-02B5-4556-A837-8AA6FE502668} (for APM 3.0). A list of common profilers with their identifiers is below.
  2. CoCreate – Another CLR profiler is competing with the Retrace profiler. Uninstall or disable any other profiler.
  3. w3wp.exe – If the active profiler causes problems with the w3wp service, it can cause crashes among other apps too. See a great blog post about w3wp here: ‘What is w3wp.exe? Learn the Basics about IIS Worker Processes’
  4. Events with the words “fault” or “crash” may indicate Retrace application errors, so please report those to us at [email protected] to investigate.

List of Common CLR Profiler Conflicts

Profiler Name Profiler Identifier
App Dynamics AppDynamics.AgentProfiler
AppInsights 324F817A-7420-4E6D-B3C1-143FBED6D855
Dynatrace DA7CFC47-3E35-4c-4e-B495-534F93B28683
Diagnostic Policy Service 555908d1-a6d7-4695-8e1e-26931d2012f4
IntelliTrace 2AA1AA98-2CAA-4FCF-86CE-EFA007737E83
Microsoft App Insights COR_PROFILER_PATH

D:homeSiteExtensionsMicrosoft.ApplicationInsights.AzureWebSitesAgentMicrosoftInstrumentationEngine.dll

New Relic FF68FEB9-E58A-4B75-A2B8-90CE7D915A26

or

71DA0A04-7777-4EC6-9643-7D28B46A8A41

Ruxit B7038F67-52FC-4DA2-AB02-969B3C1EDA03
SCOM APM AD5651A8-B5C8-46ca-A11B-E82AEC2B8E78

Check Application Pool Settings

  1. Classic mode or Integrated mode – If you are running your app pool in Classic mode, you will need to make a few settings changes. Please read the following document: .NET Agent Installation: Enable Classic IIS App Pools.
  2. .NET Runtime version – Retrace supports both .NET 2.0 and .NET 4.0 runtime versions, but if you’re using .NET 2.0, some minor configuration changes are required. Please read the following: .NET Agent Installation: Advanced Topics.

Contact Stackify Support

If none of the troubleshooting steps listed above solve your issue, reach out to the Stackify support team: [email protected].