knowledge Base

PaperVision® Capture

PaperVision Capture brings an unprecedented level of efficiency and power to information capture. Work with everything, implement any custom process you want and track any statistic you need.

 Menu

80 articles found
After upgrading to PaperVision Capture R73, and when attempting to edit a custom code step, the new Custom Code Wizard does not display.

The database table that stores batch statistics can grow considerably large in a short amount of time. If this table grows too large, an error may be thrown executing the stored procedure used to retrieve these statistics.

Within PaperVision Capture, regular expressions can be used to validate batch names and index fields populated by a user or an OCR process. Below are a few regular expressions that validate some common date formats:

When using the custom code export feature of PaperVision Capture, and designing specific output, can one use the characters of double quotation marks as field qualifiers for images?

If operators notice a long delay when taking/opening batches and before the first page displays in the Operator Console, administrators can enable the Pre-Caching property in any manual step.

When moving the batch files up to the Master Batch Repository, the PaperVision Data Transfer Agent may encounter an invalid lease error. When the Operator Console submits a batch, it acquires a "lease" from the server that expires after a certain amount of time.

When configuring Match and Merge to connect to a Named SQL Server Instance or using a non-standard port, a user receives one of the following errors: [DBNETLIB][ConnectionOpen (Invalid Instance()).]Invalid Connection or [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.


The customization and filtering capabilities of Microsoft Excel can easily augment the functionality available in PaperVision Capture. This article demonstrates a simple way to import batch statistics into Microsoft Excel 2007.

A user logs into the Operator Console and attempts to take and open a batch, and receives the following error: Unknown error code = {0}.

This error may occur because the Master Batch Path to where this batch resides has been changed in the Admin Console, but the batch has not been moved to the updated Master Batch Path. Essentially, the Operator Console is looking for the batch in the new location, but it doesn’t exist.


The Custom Code step is running the LaserFiche.xml export template, which is not modified from its default. The root path for the export folder does exist, however no files are populated. In the Batch Management Window, the job is showing “Not Owned”, but still in the Custom Code step.

80 articles found