Troubleshooting Profiler error | APM Insight .NET agent

Unable to see application after adding APM Insight .NET agent and getting "Failed to Load Profiler" error

The following are few reasons that might pose an interference with the APM Insight .NET agent profiling: 
1. User Permission settings
2. Competing profilers/monitoring services

If the installation is not done with administrative privileges, the following error might be printed on event logs,
"Loading profiler failed.  The profiler COM object was instantiated, but the profiler failed during its initialization callback.  Profiler CLSID: '{989D151B-3F31-482E-926F-2E95D274BD36}'.  HRESULT: 0x80004005."
In such cases, Health monitor tool will show the message, 
Profiler loaded for 0 out of -- process. 
If you have installed other monitoring services, stop/uninstall them and perform the following steps:
1. Uninstall the current version of .NET agent from the server
2. Download the latest .NET agent from your Site24x7 account  
3. Launch command prompt in administrative mode  on the server and install the msi from this command prompt by using the following command : 
- msiexec /i apminsight-dotnetagent.msi (or the respective msi)
4. When prompted, enter your license key and make sure all required applications are selected from App filter tab of the configuration dialog. 
5. Once the installation is complete and the service is started, you can start performing the desired transactions. 


Customers also searched this KB for the below problem statements:

  1. I'm not able to see some data collected by APM Insight .NET agent for my website.
  2. We are trying to implement APM into our website (.Net application), but the system is unable to detect it.
  3. The APM agent was installed, however the monitor was not added to the site24x7 console.

Top Phrases/Keywords used: Loading profiler failed, Failed to Load Profiler.


    • Related Articles

    • How to add APM Insight Java agent without application restart?

      In general, after installing the APM Insight Java agent, you have to restart your application for the agent to capture monitoring data. But in case of critical issues in the app, like sudden application slowness, where you haven't installed APM ...

    • How to identify and resolve conflicts between other APM products and the APM Insight .NET agent

      Problem statement: You are experiencing either of the below issues and suspect that another APM product is interfering with the Site24x7 .NET agent. 1. The .NET monitor is not created under APM > APM Insight > Applications, even after the .NET agent ...

    • APM Insight monitor not getting added to my account

      The most probable reason will be a wrong license key used while adding the agent. Check if you have added the agent in the application with the correct license key. If you have used the correct license key and still the monitor is not getting added, ...

    • DC migration steps for APM Insight Python agent

      Obtain the new device key. Update the license.key value in the apminsight_info.json file located at the <application root directory>. Log in to the server and delete the existing instance information file located at the <application root ...

    • DC migration steps for APM Insight Node.js agent

      Obtain the new device key. Update the licenseKey value in the apminsighnode.json file located at the <application root directory>. Log in to the server and delete the existing instance information file apminsight.json located at <application root ...