Logs

---

Assumptions

The V1 Server Components are fully installed and implemented.

General

• For the purposes of this page, we will assume C:\V1Home (change the path as appropriate to your installation)
• Where a DATE is inferred, a new log is created per day DD/MM/YYYY
• Where an .lg file, this will only grow to a maximum of 512KB

Manual Access

• You have direct remote desktop access to the V1 Server

Remote Access

Where direct access to the V1 Server is not permitted (such as in conjunction with a hosted environment), logs can be emailed to anyone who wants to see them by implementing the V1Logs2Email add-on.

---

Document Delivery

Emailing with DbMail (legacy)

C:\V1Home\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:\V1Home\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\DATE.system.log
C:\V1Home\SmartMail\logs\DATE.AUDIT.log

Faxing (legacy)

C:\V1Home\DbFax\spool

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

L-12345.log

---

Document Archiving

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

DbArchive

DbArchive is generic term given to the core software component of Document Archiving (and associated SQL / Oracle / PostGRE Database) housing the images archived.

If using SmartDeposit, DbScanner or any external source comitting to DbArchive, the following logs are updated:

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

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

C:\V1Home\DbArchive\PURCHASE_INVOICES.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 DbArchive table name that has been archived, a unique log is generated per object.

---

DbCapture

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

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

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

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

C:\V1Home\DbCapture\Queue\45\45del.log
Containing all evidence debugged from the DbForm definition file handling when a document is deleted.

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

---

ArchJson

The bridge between DbArchive and the SmartSuite.

C:\V1Home\SmartSuite\ArchJson\ArchJson.log

---

HTTPServer

The bridge between the legacy clients and the SmartSuite.

C:\V1Home\SmartSuite\HTTPServer\logs\DATE.httpserver.log
C:\V1Home\SmartSuite\HTTPServer\logs\DATE.system.log

---

Integration Server

The API which houses all the front end components, as well as the communication between DbCapture and ABBYY.

C:\V1Home\SmartSuite\IntegrationServer\api\logs\DATE.AUDIT.log
C:\V1Home\SmartSuite\IntegrationServer\api\logs\DATE.system.log
Generic system activity, such as communication with the database.

C:\V1Home\SmartSuite\IntegrationServer\api\logs\EngineLogs\DATE.log
High level communication log with the ABBYY FineReader Engine.

C:\V1Home\SmartSuite\IntegrationServer\api\logs\EngineLogs\SC\DATE.log
Fine details of the above log.

---

SmartConnect

API

When used in conjunction with an API.

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

EXE

When used in conjunction with an API, the SmartConnect EXE is triggered to interrogate the relevant area of the system.

C:\V1Home\logs\Smartconnect_DATE.log
A log is generated per day with evidence of all communication.

---

Addons

All Addons will create a log in the C:\V1Home\logs dir NAMEOFSERVICE.log with all evidence of their activity, e.g.

C:\V1Home\logs\NAMEOFSERVICE.log

and so on.
In an effort to keep filesize to a minmum, these are overwritten per 'tick' of the associated service, so ensure to open them at the point you wish to refer to their content.