Tutorial: Export the Configuration and Create a Debug Log#

Use this tutorial when you need EventReporter configuration data and a debug log for troubleshooting or for a support case.

Goal#

At the end of this procedure, you will have:

  • a text-based export of the EventReporter configuration

  • a debug log file that captures service behavior

Prerequisites#

  • Access to the EventReporter Configuration Client

  • Permission to restart the EventReporter service if needed

  • A writable location for the exported settings and debug log

Steps#

  1. Export the EventReporter configuration.

    • Open the EventReporter Configuration Client.

    • Go to Computer -> Export Settings to Registry File.

    • Export the settings as a text-based registry file.

  2. Save the export to a known location.

    • Use a descriptive file name such as eventreporter-config.reg.

    • Do not use the binary export format.

  3. Enable debug logging.

    • Open Debug under General.

    • Enable debug output into file.

    • Set a full path and file name for the debug log.

    • Start with Errors & Warnings and Minimum Debug Output unless support asks for a higher level.

  4. Restart the EventReporter service if required.

  5. Reproduce the problem or run the test scenario.

  6. Disable debug logging again after capture.

    • Debug logging increases system load and should not stay enabled during normal operation.

  7. Package the files for review or support.

    • Compress the exported registry file and the debug log file into one ZIP archive.

Verification#

  1. Confirm that the registry export file exists and is readable as text.

  2. Confirm that the debug log file exists and contains recent entries from the test period.

  3. If the debug log stays empty, verify that the service was restarted after enabling debug output.

Next step#

If you need to send the data to Adiscon, continue with: