Logs

---

Assumptions

The EDM for Sage X3 solution is fully installed and implemented:

• For the purposes of this page, we will assume C:\V1 (change the path as appropriate to your installation)
• You have direct remote desktop access to the V1 Server

---

EDD

Master Log

The primary method by which documents are distributed is the 'EDD Outbound Management' Windows service.
This triggers periodically, or 'tick', and each time it does, it checks for and distributes any files found and generates a log:

C:\V1\logs\EDDOUTBOUNDMANAGEMENT.log

Which will contain detailed evidence of the last files processed since the last tick.

A copy of this log is also copied to the directory where the processed files are kept:

C:\V1\EDDOUTBOUNDMANAGEMENT\PROCESSED\ADMIN_190717152044_jobrpt_SBONFACAUTO_ADMIN_95571

Which will contain detailed evidence of the files in that directory that have been processed.

Emailing with DbMail

C:\V1\logs\DbMail.log

Contains detailed evidence of all files ever processed since installation.

NOTE: This file can be opened in the DbMail Admin Client giving a clearer indication of success / failure.

Emailing with SmartMail

C:\V1\SmartMail\logs

Which will contain 2 files for both system activity and an audit of mailing activity.

New files are generated per day and meaningfully named so as to make it easier to track emails that have been received / distributed.

C:\V1Home\SmartMail\logs\2021-01-13.system.log
C:\V1Home\SmartMail\logs\2021-01-13.AUDIT.log

Faxing

C:\V1\DbFax\spool

Which will contain 1 file per fax generated, a L- followed by the FAXID.

L-12345.log

Printing

The primary method by which documents are distributed is the 'EDM Print Management' Windows service.
This triggers periodically, or 'tick', and each time it does, it checks for and prints any files found and generates a log:

C:\V1\logs\Print_Pickup.log

Which will contain detailed evidence of the last files printed since the last tick.

---

EDM

EDM generates many log files, getting to know where they are can help diagnose issues and help debug enhancements.

NOTE: All the EDD log files will be present for EDM, in addition:

DbArchive

DbArchive is generic term given to the core software component of EDM (and associated SQL Database) housing the images archived.

If using SmartDeposit, DbScanner or from a distributed document using EDD where EDM has also been purchased, the following logs are updated:

C:\V1\DbArchive\dbarchive.31417.lg
Containing all evidence of activity between the server and request for adding a document.

C:\V1\DbArchive\dbarchive.31418.lg
Containing all evidence of activity between the server and request for querying a document.

C:\V1\DbArchive\V1X3_V1BIC.31417.log
Containing all evidence of activity in the DbForm definition file of the same name (*.def) handling the validation and export of images.

NOTE: The text in red indicates the Sage object that has been archived, a unique log is generated per object.

EDMImport

When using the '[EDM] Archive Transaction / Attachment' links in Sage X3, the 'EDM Import' Windows service is used to manage moving the file to V1 so it can be archived.
This triggers periodically, or 'tick', and each time it does, it generates a log:

C:\V1\logs\EDMImport.log

---

PIA with DbCapture

PIA with DbCapture generates many log files, getting to know where they are can help diagnose issues and help debug enhancements.

NOTE: All the EDD and EDM log files will be present for PIA with DbCapture, in addition:

C:\V1\DbCapture\Queue\45\45val.log
Containing all evidence debugged from the DbForm definition file handling the validation of a document.

C:\V1\DbCapture\Queue\45\45exp.log
Containing all evidence debugged from the DbForm definition file handling the export of a document.

C:\V1\DbCapture\Queue\45\45rej.log
Containing all evidence debugged from the DbForm definition file handling when a document is put on hold.

NOTE: The text in red indicates the Document ID, a unique log is generated for each one.

---

SmartConnect

API

When used in conjunction with SmartExtract, the SmartConnect API layer handles the communication between them during day to day processing of documents, such as validation and export.

C:\V1\SmartConnect\SmartConnectAPI\logs\SmartconnectAPI_2021_01_13.log
A log is generated per day with evidence of all communication.

EXE

When used in conjunction with SmartExtract or translations in PIA with DbCapture, the SmartConnect EXE is triggered to interrogate the relevant area of the system.

C:\V1\logs\Smartconnect_01-12-2021.log
A log is generated per day with evidence of all communication.