Periodically, I receive emails describing various errors related to Kofax batches. The errors indicate that certain batches have failed during emailing, scanning, transformation, validation and/or export. Often, the error is so inaccurate that we need to perform additional investigation to determine the exact source of the problem. Investigating such errors is somewhat complicated, especially in cases where other products in the Kofax portfolio report the error, such as KCNS, KCIC/KIC, e-Transaction or Kofax Transformation Module (KTM).
Recently, I encountered an error stating the following: “batches failed during the ‘KTM Server’ queue, as there was no disk space available”. This problem caused the files to be unrecoverable and therefore had to be re-imported into the system.
Interestingly, the error message had nothing to do with the actual problem.
Taking the above into consideration, and for everyone's convenience, I have made a summary of all the necessary folders that require cleaning as part of the regular maintenance of your Kofax system. This will certainly prevent such error messages from occurring in your organization.
Kofax records
- C:\programdata\Kofax Product>Local Logs. For example, C:\programdata\Kofax\Capture\Local\Logs.
- \CaptureSV Logs
Kofax Database
You can identify the database configuration by running the Kofax DBUtil utility from the ‘Database’ tab.
If the Kofax database configuration is set to ‘Standard’, then the option to free up disk space is not necessary. But, in case it is set to SQL Server, Oracle or DB2, If the database is not backed up, then a schedule for standard database backup and regular maintenance is required to truncate the records.
The most important task is to set up a weekly full backup that truncates logins. An administrator can configure others, such as incremental backup, but the goal is to truncate logs that can go to GB at any time (depending on usage).
External application and/or service related to a lot or project type
Many Kofax projects require database lookups, along with search queries that are configured either directly from the schema of other systems (such as ERP, accounting systems, payroll systems) or from intermediate ASCII files placed in a folder that are selected by a custom service and appended to the application database. In many cases, I have observed that maintenance is not performed on these folders and, over time, these ASCII files accumulate on disk and consume storage. A regular maintenance regimen is necessary to identify those folders, which should be backed up and/or cleaned up, to ensure that disk storage remains intact.
These simple practices will ensure that your Kofax validation runs smoothly and are useful and can be applied to most systems within your organization.
Spanish 
English 
German