Logs & Diagnostics
What the Label Print App records, how it reaches DPD support, and what to do when support asks you to turn on extra detail.
The Label Print App writes log files on your computer and can send them to DPD automatically. Online Label Print runs in your browser and has no local log files — for problems there, contact support directly.
Where the log files are
The application writes its log to the logs folder of its data directory, typically:
C:\ProgramData\DPD\LabelPrintClient\logs
A new file is started each day, named client-application.<date>_FILE-<n>.log, and files are kept for 30 days. The file for the current day stays open while the application is running.
The exact folder depends on how the application was installed. It is shown as LOG_DIR under Settings → Version information.
Sending logs to DPD
The application uploads completed daily log files to DPD on its own, so support can look at a problem without asking you to find and e-mail anything.
Uploads happen about ten minutes after the application starts and again every night at 05:30, in both service and application installation modes. Only files for days that have finished are sent, each file is sent once, and the file for the current day is never sent while it is still being written.
You can switch this off under Settings → Global settings → Send logs to DPD. It is on by default.
Because the current day's file is only uploaded after midnight, support may ask you to send it manually. Copy it out of the logs folder above and attach it to your ticket — copying the file while the application is running is safe.
Debug logging
Normally the application records the important steps only. Debug logging adds a much more detailed record, which is often what support needs to explain behaviour that only happens on your machine.
Turn it on under Settings → Global settings → Debug logging.
You do not need to restart the application. The extra detail starts being recorded as soon as you save the setting, and the setting is remembered the next time the application starts.
Turn it off again once support has what they need. Debug logging makes the files considerably larger — they roll over sooner, so they cover fewer days, and more data is uploaded.
A useful sequence when support asks for it:
- Turn Debug logging on.
- Reproduce the problem.
- Note the time you reproduced it and tell support — it helps them find the right lines.
- Turn Debug logging off.
Earlier versions always recorded the detailed level. From 3.5.0 the detailed level is off unless you switch it on, which keeps the log files smaller. Your version is shown under Settings → Version information.
The switches are greyed out
Both settings are administrator settings. If you cannot change them, sign in with an account that has administrator rights, or ask a colleague who has one.