TN 1433 Capturing AVEVA Application Crash Using DebugDiag

Description

This article from InSource shows how to configure DebugDiag to capture AVEVA application crash events. 

• Author: Mario Meza
• Published: 03/30/24
• Applies to: AVEVA Products

Details

DebugDiag is a powerful tool used to create detailed dump files. These dump files help in diagnosing and resolving crashes, memory leaks, and other unexpected software behaviors

Download and Install DebugDiag2

1. Download DebugDiag2.
   1. Choose 64 bit for 64 bit machines or 32 bit for 32 bit machines.
      1. The bit type of the system can be confirmed in the System control panel or in Settings>System>About.
   2. Download link:
      1. https://www.microsoft.com/en-us/download/details.aspx?id=58210
2. Install DebugDiag2.
   1. Only Dump Collection is required to be installed.
      

Create a Crash Rule in DebugDiag2

1. Open the Start menu, click Debug Diagnostics Tools 2, click DebugDiag 2 Collection.
2. Click Add Rule if the wizard does not pop up
3. Choose Crash and click Next.
   
4. Choose A specific process and click Next.
5. Select or type the name of the process you wish to monitor, in this case we will use Studio Manager.exe or Viewer.exe and click Next.
   
   For the focus of this article we will use IWS however this could be any AVEVA product .exe that is manifesting unexpected software behaviors.
   
   
   1. The InduSoft Web Studio runtime needs to be running in order to see Studio Manager.exe or Viewer.exe in the process list. It can simply be typed in however.
      
6. For Action type for unconfigured first chance exceptions choose Full Userdump.
   1. Set Action limit for unconfigured first chance exceptions to 5.
   2. Set Maximum number of userdumps created by this rule to 25.
      
   3. Click Exceptions, click Add Exception.
   4. Choose Access Violation.
   5. Set Action Type to Full Userdump and Action Limit to 10.
      
   6.  Click OK.
   7. Repeat steps d through g but this time choose Stack Overflow.
      
   8. Once configured the First Chance Exception Configuration should look like this:
       
   9. Click Save & Close
   10. Click Next. Click Yes to any popups
7. Under Rule Output Location, click Browse, and choose a folder to store the DebugDiag dumps.
   1. Going to the C drive and creating a folder called DebugDiagDumps is recommended.
8. Keep Activate the rule now checked and click Finish.
   1. If it asks about setting the symbol path, click Yes. aveva.com
9. You should now see the rule just created in DebugDiag.
   
10. Repeat steps 5-9 and create a Crash Rule for more processes as required.
11. DebugDiag is now setup to create full userdumps when exceptions or crashes occur