Latest News: MIDAS v4.25 Now Available | COVID-19 Support

MIDAS Knowledge BaseMIDAS Knowledge Base

How to enable debug logging

Note: This article applies to self-hosted editions of MIDAS only

If when using your MIDAS scheduling system you see a "MIDAS encountered an unexpected error" or "Unable to save settings" error message in your browser, then to help identify the specific cause of the error you may need to enable debug logging.

For security reasons, debug logging in MIDAS is disabled by default, and therefore in the unlikely event that your MIDAS encounters an error, very limited information will be shown to end-users.

If you're running MIDAS v4.16 (or later), then you can enable/disable debug logging via MIDAS Admin Options → Manage MIDAS → Miscellaneous → Enable Debug Logging.

To enable debug logging if you're running an earlier version of MIDAS (pre v4.16), you will need access to the server where your MIDAS resides, and you'll need to do the following:

  1. Locate the "midasglobal.dat" file and open this in a standard text editor
  2. On line 3 of this file (after the <midas> tag on the previous line), add the following:
  3. Save changes to the midasglobal.dat back to the server

Once debug logging has been enabled, try and recreate the conditions which led to the "MIDAS encountered an unexpected error" or "Unable to save settings" message in your browser, and additional diagnostic information may be shown on screen along with the generic error message.

In addition, a "debug.dat" file may also be created on your server (at the location where your MIDAS is installed), which will contain further specifics on the error.

Important: We recommend only enabling debug logging to troubleshoot a specific issue, or when requested to by MIDAS support. Once your issue has been resolved, you should disable debug logging again and remove any created "debug.dat" file from your server

To disable debug logging in self-hosted editions of MIDAS prior to v4.16, follow the steps for enabling debug logging above, but set <debug>3</debug> (or remove the <debug>...</debug> line from the midasdglobal.dat file completely)

You might also be interested in...

MIDAS » KB » Support » Article 00146

← Return to Knowledge Base