40.26 Error Report via Email
40.26.1 Overview ¶
In the Error Report via Email area you configure the automatic dispatch of the error report by email (as of version 4.7.0). Following a defined schedule, the program generates the complete error report - the same file that can be created manually via the submenu More → Generate Error Report… (see Chapter 2.6.1) - and sends it as an attachment to one or more email addresses.
This is particularly useful when one person is responsible for keeping an eye on several installations without having to generate and check error logs on each computer regularly.
Related: The processing report (Excel) has its own schedule, see Chapter 40.16 (Excel Report).
40.26.2 Activation ¶
| Field |
Description |
| Send error report by email |
Enables the automatic dispatch. As long as this option is disabled, all further inputs in this area are locked |
40.26.3 Schedule ¶
| Field |
Description |
| Interval |
Daily, weekly, or monthly |
| Weekday |
Only for the weekly interval: Monday to Sunday |
| Day of month |
Only for the monthly interval: 1 to 28 (higher days are avoided because they do not exist in every month) |
| Time |
Time of day at which the report is sent (format HH:MM) |
Note: If the program is not running at the set time (application mode, PC off), the due dispatch is caught up on the next program run - but at most one report is sent per interval.
40.26.4 Only send if there are new entries ¶
| Field |
Description |
| Only send if new error log entries have been added since the last send |
Enabled by default. At the due time, the program checks whether new error log entries have been created since the last dispatch - if not, the dispatch is skipped for this interval |
Tip: With this option, an incoming report email automatically means “something new happened” - if the mailbox stays empty, the installation was unremarkable. Disable the option if you deliberately want to receive the report in every interval (e.g. as a sign of life of the installation).
40.26.5 Recipients and email account ¶
| Field |
Description |
| Email addresses |
One or more recipient addresses, separated by semicolons (e.g. it-support@company.com; admin@company.com) |
| Email account |
Selection from the accounts configured under Email Accounts. The account must support sending |
Note: If the selected account is removed later, a phantom entry “(account no longer exists)” appears in the dropdown - the selection is retained until you actively change it.
40.26.6 Error report via command line ¶
For scripts and the central monitoring of many installations, the error report can also be generated and sent via the command line - e.g. via the Windows Task Scheduler:
| Parameter |
Short form |
Description |
--errorreport [target] |
-e [target] |
Generates the error report and exits. Target: file or folder; without a target, the file is placed on the desktop |
--send [recipients] |
|
Only with --errorreport: sends the report by email. Without recipients, the recipients and sending account from this options area apply |
--onlynew |
|
Only with --send: only sends if new error log entries have been added since the last command-line dispatch |
--inboxcounts |
|
Only with --errorreport: additionally queries the inbox counts of all accounts (connects to all accounts, takes correspondingly longer) |
Examples:
AEPProcessor.exe --errorreport
AEPProcessor.exe --errorreport "\\Server\Share\AEP-Reports"
AEPProcessor.exe --errorreport --send
AEPProcessor.exe --errorreport --send it-support@company.com --onlynew
If a folder is specified as the target, the file name automatically includes the computer name - this way, many installations can write to the same central network folder without overwriting each other. The command line also works in parallel with a running processing service.
Note: The command-line dispatch and the scheduled dispatch from this options area work independently of each other - each keeps its own record of “since the last send”. A morning script dispatch therefore does not prevent the later scheduled dispatch to the supervisor address.
The complete parameter overview of the processor (including exit codes for scripts) can be found in Chapter 60.3 (Service Mode).
40.26.7 Use case ¶
Central monitoring of several installations
A system house supports ten installations at a customer site. The schedule is active on each computer: weekly, Monday 07:00, with the option “Only send if there are new entries”, recipient aep-monitoring@systemhouse.com. On Monday mornings, the monitoring mailbox shows at a glance which installations logged errors in the previous week - no email arrives from the unremarkable ones. In addition, a scheduled task (--errorreport "\\Server\AEP-Reports") collects the complete reports in a central share every day.