cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Not a customer? Start a free trial

Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.

AppDynamics customers and established members should click the sign in button to authenticate.

Knowledge Base

How can I determine the root cause of CLR crashes?

Updated on 7/30/18

 

Question

We see CLR crashes happening a few times a day. How can I use AppDynamics to determine the root cause of the crashes?

 

Answer

One issue usually causes multiple CLR crashes. Here are some places to look to help you find the root cause:

 

1. When a CLR crashes, the .NET Machine Agent raises an event in the Controller. Start by looking at the details captured in the CLR crash event by clicking on the Server Crashes link in the Application Dashboard. You will see information about the crash event, like the process ID and windows event log id. Double-click on the CLR Crash Type to view additional information that can help you troubleshoot the root cause of the crash. For additional instructions on reviewing the crash event, see: Analyze and Respond to CLR Crashes
 
2. Look at any errors/exceptions happening around the same time as the crash that could be related to it. Transaction Analysis is a great place to get a combined view (see below). If the crash occurred before we could report the captured exception, you may not see anything there.

transaction_analysis.png

 

3. Look at Machine snapshots from that time on the machine where the crash occurred. This will rule out any physical resource pressures.
 
Version history
Last update:
‎07-30-2018 10:41 AM
Updated by:
Labels (2)
Tags (2)
By replying you agree to the Terms and Conditions of the AppDynamics Community.
0 Kudos