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 "System.AccessViolationException" while running the APM Insight .NET agent, follow these steps to identify and resolve the issue:
Identify this Crashing issue with Event Logs
1. Open Event Viewer logs from the agent installed machine
2. Look for exception entries like below example:
Here, instances of connectivity errors and performance degradation were observed, indicating a potential conflict with the ServiceChannelProxy framework.
Solution
Follow the below steps to resolve the exception:
1. Navigate to the `C:\ProgramData\DotNetAgent` directory
2. Open the `apminsight.conf` file using a text editor. Add the appropriate class method which cause `System.AccessViolationException` under .NET Runtime source as mentioned above screenshot at the end of the file(Ensure there is an extra empty line after adding the configuration):
<Appropriate-Access-Violation-Exception-Occured-Method>=false
For Example here:
System.ServiceModel.Channels.ServiceChannelProxy.InvokeService=false
Note: This change removes tracking for the specified method by the agent to prevent the access violation further.
3. After saving the changes, restart the `ManageEngine .NET agent service` to apply the new configuration settings.
Additional Notes
We have acknowledged this issue and have included it in our roadmap for future releases to provide a permanent fix. In the meantime, implementing the suggested configuration changes will mitigate the instrumentation issues caused by the incompatible framework methods.
If the issue persists, Kindly contact the support@manageengine.com along with the updated Agent diagnostics
New to ADSelfService Plus?
Related Articles
Troubleshooting steps to identify and resolve the crashing issue while monitoring applications in SharePoint/Multiple domain assembly environments
If you encounter the exception "Loading this assembly would produce a different grant set from other instances" while running the APM Insight .NET agent, follow these steps to identify and resolve the issue: Understanding the issue Our APM Insight ...Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check prerequisites to be done Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...Troubleshooting steps to identify and resolve the APM - Java agent monitor onboarding issue due to "IllegalArgumentException: URI path begins with multiple slashes"
If you encounter the exception "java.lang.IllegalArgumentException: URI path begins with multiple slashes" while pointing the APM Insight Java agent folder to your monitoring Java Application server, follow these steps to identify and resolve the ...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 ...Troubleshooting steps for Server Hardware Health Monitoring
1. SNMP Mode of monitoring: Monitoring Dell hardware status: Dell OpenManage Server Administrator and make sure SNMP agent is enabled Installation steps: http://www.dell.com/downloads/global/power/ps2q06-20050112-Lou-OE.pdf Monitoring HP hardware ...