Reason | Cause | Solution |
Agent service not running | Can be contributed to various factors like antivirus software stopping the service or user stopping the service. | Start the APM Insight .NET agent service (this recycles the app pools), and perform some transactions. |
Could not connect to host | Server is behind proxy or uses outdated TLS version (versions below 1.2) for communication. | Edit the proxy settings in the APM Insight .NET Agent configuration
window and verify the connection to Appmanager server on a
browser. For outdated TLS versions, update to the latest .NET agent
version. |
Profiling environment variables not set | A competing profiler has been installed. | Navigate to the Tools tab, and click Repair Installation. Uninstall any competing profilers and restart the APM Insight .NET Agent service (this will reset IIS). |
No. of apps included for monitoring -0 | Applications to be monitored are not configured in APM Insight .NET
Agent configuration window or new applications were added after
configuration. | Open the APM Insight .NET agent configuration window and navigate to the Applications tab. Select the applications to be monitored, and click Save. This recycles the respective app pools. |
[IIS Applications tab] Monitor in "Deleted" or "Marked for deletion" state | Trying to add a monitor after deleting it in the Appmanager server | Delete the apminsight.net.info file of the respective application in the %ProgramData%\DotnetAgent\<APPLICATION_NAME> folder, and restart the APM Insight .NET Agent service (this will recycle the app pools). |