Using error logging to diagnose problems

Home » Tips » Using error logging to diagnose problems
Tips No Comments

Osmose endeavors to test O-Calc Pro on as many different systems and configurations as possible but occasionally there are installations that do not operate correctly due to unanticipated system setting, other installed security software, or non-standard drivers. When this happens O-Calc Pro provides tools to help diagnose and address these problems.

One of the most powerful of these tools is the advanced logging tool. The following steps may be followed to enable the logging function:

  1. Step 1: Enable error logging
    1. Open registry editor
    2. Open folder HKEY_CURRENT_USER / Software / PPL / Exceptions
    3. Set LogAssertions to “True”
    4. Set ExceptionLoggingLevel to a number between 1 and 4 as described below
  2. Stop and re-start O-Calc Pro and repeat the steps that cause the unexpected behavior
  3. In your “Documents” folder locate the file “OCalcExceptions.log
  4. Review the log to determine the source of the error

The various logging levels are as follows:
Level 1: Record name of calling Source where error occurred
Level 2: Additionally record Target
Level 3: Record the entire call stack (may be large)
Level 4: Record all inner exceptions (may be extremely large)

The log becomes much larger and more cryptic as the logging level goes up.  Levels 3 and 4 should be used to gather information to be sent to Osmose for review.  Levels 1 and 2 are best for local diagnosis as the error messages are more easily understood.

Make sure to set LogAssertions registry values back the “False” at a minimum, and set ExceptionLogging to 0 or 1. This will prevent unintended log growth.

Facebooktwitterlinkedinmail