How to Use Diagnostics & Create a Support Package

The Support section of ADReports lets you load and inspect application and service log files, search and filter log entries by date, severity, and keyword, and create a compressed support package that you can send to technical support.

New in 7.5.4: support packages can be sent to us with one click and now explain what they found; a Support Packages list lets you send, e-mail or delete them later; the Support page shows which Windows account the application runs as; and a Log level setting turns Debug logging on and off without a restart.
1

Opening the Diagnostics Screen

  1. Launch ADReports.
  2. In the left-hand navigation bar, locate and click Support.
  3. The Diagnostics screen loads automatically inside the main panel.

AD Reports Support navigation item highlighted in the left navigation bar

2

Understanding the Screen Layout

The Diagnostics screen is divided into four areas:

Area Description
Filter bar (top) Controls for date range, severity, source, keyword, and action buttons.
Log Entries grid (middle) Tabular list of all loaded log entries, sortable and searchable.
Entry Details panel (bottom) Full text of the currently selected log entry, including stack traces.
Status bar (very bottom) Shows the current state — Ready, loading progress messages, or a result summary.
3

Setting the Date Range

The From and To date pickers at the left of the filter bar control which log files are read.

  1. Click the From date field and select the start date from the calendar popup.
  2. Click the To date field and select the end date.

Both fields default to today's date when you first open the screen. You can also type a date directly into either field.

The date range is inclusive — log entries from both the start and end dates are included.

AD Reports Diagnostics filter bar with From and To date fields highlighted

4

Choosing Severity Levels

Three severity checkboxes appear in the Severity group:

Checkbox Includes
Error Error and Fatal entries
Warning Warning entries
Info Informational entries
Debug New in 7.5.4 Debug entries — only written while the Log level is set to Debug (see step 14)

Error, Warning and Info are checked by default; Debug is unchecked so verbose entries stay out of the way. Uncheck one or more to narrow the results — for example, uncheck Info and Warning to see only errors — and check Debug after reproducing a problem with Debug logging on, then uncheck it again afterwards.

Changing a severity checkbox while logs are already loaded instantly re-runs the load with the new filter — you do not need to click Load Logs again.

AD Reports Diagnostics severity checkboxes with Error only checked

5

Choosing Log Sources

The Source group has two checkboxes:

Checkbox Log files read
Application Logs produced by the ADReports desktop application.
Service Logs produced by the ADReports background scheduler service.

Both are checked by default. You must leave at least one source checked — if you uncheck both, the load will not start.

If you are troubleshooting a scheduled report that failed overnight, select Service only to focus on the scheduler logs.

AD Reports Diagnostics source checkboxes with only Service checked

6

Searching by Keyword

The Search field (labeled keyword...) filters entries by text content.

  1. Click the Search field to the right of the Source checkboxes.
  2. Type a keyword, error code, username, or any text fragment.
  3. Press Enter (or click Load Logs). Only entries whose message text contains the keyword will be loaded.

Leave the field blank to load all entries matching the other filters. The search is case-insensitive.

Improved in 7.5.4: the Search box is bigger, states that it applies when you refresh, and Enter refreshes for you. Because it filters the log as it is read, a support package created afterwards contains only the matching entries — a handy way to send us just the relevant part of a busy log.

AD Reports Diagnostics search field with an example keyword entered

7

Loading Log Entries

Once your filters are set:

  1. Click the Load Logs button at the right of the filter bar.
  2. The status bar at the bottom of the screen shows progress as each log file is read.
  3. When loading is complete, the status bar displays a summary such as:
    Showing 342 entries (15 errors, 27 warnings, 300 info)
Severity and source checkboxes automatically trigger a reload if logs have already been loaded at least once. You only need to click Load Logs manually for the first load or after changing the date range or keyword.

AD Reports Diagnostics status bar showing a result summary after a successful load

8

Reading the Log Grid

Loaded entries appear in the grid with the following columns:

Column Description
Timestamp Date and time of the entry (yyyy-MM-dd HH:mm:ss.fff). Sorted newest-first by default.
Level Severity: Information, Warning, Error, or Fatal.
Source Which component wrote the entry: Application or Service.
Message First line of the log message.
File Name of the originating log file (e.g., ADReports20250207.log).

Color coding: Error and Fatal entries appear in red, Warning entries in dark orange, and Informational entries in normal text.

Click any column header to sort by that column. Use the auto-filter row (the blank row directly below the column headers) to type a quick filter on any column without reloading. Use the Find panel to search across all columns simultaneously, and the navigator bar at the bottom of the grid to page through results.

AD Reports Diagnostics log grid with color-coded rows and the auto-filter row highlighted

9

Viewing Entry Details

Clicking any row in the grid displays the full entry text in the Entry Details panel below the grid. This panel shows the full-precision timestamp, severity level, source, originating log file name, and the complete log message — including multi-line stack traces and exception details.

The details panel supports both horizontal and vertical scrolling. If a stack trace is truncated in the Message column, the full text is always available here.

AD Reports Diagnostics Entry Details panel showing a multi-line exception stack trace

10

Cancelling a Load in Progress

If loading is taking a long time (e.g., a very wide date range):

  1. Click the Cancel button that replaces the Load Logs button during loading.
  2. The status bar shows Cancelling... briefly, then displays a partial-results summary:
    Showing 120 entries (3 errors, 8 warnings, 109 info) — partial results (loading was cancelled)
  3. The entries loaded so far remain in the grid and can still be used to create a support package.
11

Creating a Support Package

A Support Package is a ZIP archive that bundles the filtered log data with system information. You can send this file to technical support for faster diagnosis.

The Create Support Package button is only enabled after at least one log entry has been loaded.
  1. Load the logs using your desired filter settings (see steps 3–7 above).
  2. Click the Create Support Package button at the far right of the filter bar.
  3. A confirmation dialog appears showing a summary of the package contents: time range covered, total number of entries, sources included, any active keyword search, and estimated file size.

AD Reports Diagnostics support package confirmation dialog with package summary

  1. Click OK to proceed, or Cancel to go back.
  2. The package is created immediately — there is no Save As dialog any more 7.5.4. It is saved to a Support folder beside your log files, and its name includes the date and time, so a second package never overwrites the first.
  3. You are then asked whether to send the package to MaxPowerSoft. Click Yes and it uploads over HTTPS and shows a reference number to quote when you contact us. Click No and the package is simply kept on disk — you can send, e-mail or delete it later from Support Packages.

AD Reports prompt asking whether to send the support package to MaxPowerSoft, with the reference number shown after upload

Nothing is sent unless you say yes. The upload only happens when you answer Yes to the prompt, or choose Send Checked in the Support Packages list. If you prefer to send the ZIP yourself, e-mail it to info@maxpowersoft.comE-mail Checked in the same list is there for that.

What the package contains:

File Contents
filtered-logs.txt All displayed log entries. Sensitive data (passwords, tokens, etc.) is automatically masked before inclusion.
diagnostic-summary.txt Starts with a Findings section New in 7.5.4 listing known problems recognised in your log — what is wrong, how to fix it, and how often it happened — followed by the statistics and filter criteria used to produce the log set.
job-history.txt New in 7.5.4 Recent scheduled runs with their status and any error, plus a summary of how e-mail is configured. Passwords are never included.
system-info.txt OS version, .NET version, machine name, the Windows account the application runs as, and other environment details useful for support.
Sensitive data in log messages (such as credentials or personal identifiers) is masked automatically before the package is created. You do not need to manually review or redact the log file.
Logs are always captured (Improved in 7.5.1.2): if AD Reports can't write to its shared data folder, log files are saved to a per-user folder instead of silently not being written at all — so a support package always contains something useful. Packages now collect logs from every location and state which one was used.
12

Send, E-mail or Delete Packages Later New in 7.5.4

Click Support Packages on the Support ribbon to see every package on this machine. Check the ones you want and use the buttons above the list:

  • Send Checked — uploads the checked packages to MaxPowerSoft over HTTPS and shows the reference number for each. A package that failed to send earlier can simply be sent again — there is no need to rebuild it.
  • E-mail Checked — e-mail the checked packages yourself instead of uploading them.
  • Delete Checked — removes the checked packages from disk.

The list shows which packages were already sent and their reference number, and it can be sorted, searched and filtered like any other list in the application.

AD Reports Support Packages list with Send Checked, E-mail Checked and Delete Checked buttons

13

Check Which Windows Account Is Running AD Reports New in 7.5.4

The bottom of the Support page shows the Windows account the application is running as and the log folder it writes to. Support packages report both as well.

Why this matters: the most common reason the Scheduler Service cannot send e-mail is that it runs as a different account from the one that saved the e-mail password. If scheduled e-mails fail while the application sends them fine, compare the account shown here with the account the service runs as.
14

Choose How Much Detail Is Logged New in 7.5.4

Settings → General now has a Log level setting: Debug, Information, Warning or Error. It applies immediately to both the application and the Scheduler Service — no restart needed.

The typical support workflow:

  1. Set the Log level to Debug.
  2. Reproduce the problem.
  3. On the Support page, check the Debug severity, load the logs and create a support package.
  4. Set the Log level back to Information — Debug logging is verbose and makes the log files grow quickly.

AD Reports Settings, General page with the Log level drop-down

15

Tips & Troubleshooting

Situation What to do
No entries found Widen the date range, or ensure at least one severity and one source are checked.
"From date cannot be after To date" error Correct the date fields so that From is earlier than or equal to To.
"Please select at least one log source" error Check at least one of the Application or Service checkboxes.
Load is very slow Narrow the date range to a shorter period, or cancel and refine your filters.
Create Support Package button is greyed out You must successfully load at least one log entry before the button becomes active.
Entry details are empty Click a row in the grid to select it; the details panel updates automatically.
I need logs from multiple date ranges Load and export one range first, then change the dates and create a second package.
A package failed to send, or I chose No and want to send it now Open Support Packages, check the package and click Send Checked. Sent packages show their reference number.
Scheduled e-mails fail but the application sends fine Compare the account shown at the bottom of the Support page with the account the Scheduler Service runs as (see step 13).
Support asked for a Debug log Set Settings → General → Log level to Debug, reproduce the problem, create the package, then set it back (see step 14).
If you have any questions or need assistance, please don't hesitate to contact us.
Ready to Try AD Reports?

Download the free 14-day trial and start reporting on your Active Directory today.

Download Free Trial Browse Report Library