Support Center

How can I increase the debugging level in the log file of Liquid Notes?

Last Updated: Nov 06, 2016 04:35PM CET
This article provides information on how to to increase the output from notifications, etc. collected in the log file of Liquid Notes.

Quick answer: Follow the steps below for enabling of more detailed tracing.

Note: Only do this if asked to do so by Customer Support, as the additional output slows down Liquid Notes and may cause other applications to be slow/non-responsive, or even crash, on your machine.

Enabling advanced debugging in Liquid Notes

As is typical with other software, Liquid Notes provides an option for more detailed debugging. This option needs to be enabled manually by the user, and should only be done so in case of a need for more detailed analysis by Re-Compose. 

Please follow these steps to enable advanced debugging:
  1. Make sure that Liquid Notes is not running!
  2. Go to the log file folder of Liquid Notes. Find the steps here how to locate it -
  3. Rename the file "logLevels.cfg" into "logLevels_old.cfg".
  4. Download the configuration file with settings for advanced debugging, and place it into the log file folder -

    (Note: If the file opens in your web browser, please right-click with your mouse and select "Save page as ..". Make sure the file is named "logLevels.cfg" when saving it to your hard disk.)
  5. Launch Liquid Notes and wait for the application to start up or quit

    (Note: Depending on your error scenario you may have to execute a few more steps until running into the error which requires debugging.)
  6. Copy the file "logFile.txt" and send it to Re-Compose Customer Support
  7. Delete the file "logLevels.cfg"
  8. Rename the file "logLevels_old.cfg" to "logLevels.cfg"

After having completed the entire sequence the debugging level is back to default again. This is to make sure Liquid Notes, and your system, behaves normally.

In case you feel there is abnormal behavior after debugging, let us know asap.

Need Help?

Should you require assistance, get in touch with us at!
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found