Sage 200 Evolution – Using the Eureka Log to Trap and Trace errors

2 minute read time.

This blog article discusses how to use the Eureka Log to trap and trace errors. Remove the following: The Eureka Log in Sage 200 Evolution can trap and trace exception- and memory leak related issues and errors.

Once the errors have been trapped, a detailed log of the call stack with unit, class, method, and line number information is generated. These detailed logs are referred to as Exception Logs.

What are the basic steps in the process of using the Eureka Log and analysing its outputs?

  1. Confirm if the Sage 200 Evolution users can replicate or regularly observe the issue.
  2. If the answer the above is Yes, activate the Eureka Log – This is done to generate an error log in the form of *.DAT or _el files
  3. These DAT files are then sent to Sage 200 Evolution Support who then escalate to Development.
  4. Development will then further analyse the DAT files to find the cause which may lead to finding the solution. 

Activating the Eureka Log

1. Login to your Sage 200 Evolution Company as the Administrator

2. Navigate to Administration | System Configuration | System Wizard | Service 

3. Select the option Enable Detailed Exception Logging and then Finish

4. Exit and Log Off

5. Right click on the Evolution executable shortcut and edit the Properties as below:

   On the Target field: enter the /el phrase after the current value, e.g. "C:\Program Files (x86)\Sage Evo\Evolution.exe /el”

6. Apply and save the above changes

7. Notice that when the errors occur, they are automatically logged as new DAT files created in the C:\Users\ {USERNAME}\AppData\Roaming\ExceptionLogs folder 

Else, you can check under the Exceptions log folder, within the Sage Evolution Program Files Install Directory

8. Several log files may be generated as seen below, which should be sent to Sage 200 Evolution Support. Sage 200 Evolution Support will then escalate accordingly to the Development team for further                     investigation on this matter and map a way forward for a fix.

            

9. These three file types may be generated and should all be sent to Sage 200 Evolution Support.

  • *._el file/s
  • *.Dat file/s
  • *.bmp file/s  
  • The captured screen shots of the error/s when they are observed.

10. In addition:

The above files are required along with:

  • The relevant Evolution Administration | System Tools | Message Log Viewer | Application log files - Select file and Save
  • Relevant Windows Event Viewer log files as obtained by the client’s local IT technician
Anonymous