How to produce clean log files

The best way to troubleshoot problems, is to send a 'clean debug log' to support. This is a log file that contains, as far as possible, only information related to the problem at hand. Note that from version 8.0, the server diagnostics file is preferred, as it contains the configuration file as well as logging.
The summary steps for producing a 'clean debug log' are as follows:

  1. Set the logging level to Debug (or All, for even more detail)
  2. Stop the CompleteFTP service
  3. Delete the existing log file
  4. Start the CompleteFTP service again
  5. Reproduce the error
  6. Send support the (zipped-up) log file

This, of course, assumes that the service can be stopped without impacting users. If the service cannot be stopped, perform steps 1, 5 and 6 only.

The detailed steps:

  1. Set the logging level to Debug:
    1. Open CompleteFTP Manager and connect.
    2. Select the Monitoring tab and then select Log Files.
    3. Set the Logging level to 'Debug' and click 'Apply Changes'.
    4. Close the CompleteFTP Manager.
  2. Stop the CompleteFTP service:
    1. Open the Services item in the Windows Control Panel.
    2. Select CompleteFTP and hit the stop button.
  3. Delete the existing log file:
    1. Select 'Log Files' from the CompleteFTP menu group in the Windows start menu.
    2. Find 'Diagnostics.log' and delete (or rename) it.
  4. Start the CompleteFTP service again:
    1. Open the Services item in the Windows Control Panel.
    2. Select CompleteFTP and hit the start button.
  5. Reproduce the error:
    1. Do whatever it was that caused the error: E.g. connecting with an SFTP client and getting an error.
  6. Send the (zipped) log file to EDT support:
    1. Select 'Log Files' from the CompleteFTP start menu (in Windows).
    2. Zip up the Diagnostics.log file and e-mail it to support