Kofax Ascen 7.0 Release Script - Manual (Page 32)

Ascent® 7.0 Release Script for XML Release Notes
28 Kofax, Inc.
Known Problems
This section contains information about known problems with the Ascent 7.0 Release Script for
XML.
Problems When Uninstalling the Release Script
If you click the Cancel button while you are uninstalling the release script, all the release script
original files will remain properly installed on the system. However, depending on the point
during the uninstallation the Cancel button is clicked, the release script may be un-registered. In
such a case, once you attempt to log on to the release script, login will fail. (SPR 31221)
Workaround: If this problem occurs, run Repair.
Refer to Repairing the Release Script on page 18 for more information. Alternatively, you can re-
register the release script in the Release Script Manager.
Possible Memory Leak When Releasing Documents
When releasing documents continuously for twelve to fifteen hours, you may experience a
possible memory leak. In this case, you will notice that the workstation will be unresponsive and
the Ascent Capture Release module will close. (SPR 00019918)
Workaround: We suggest that you change the registry settings for the Ascent Capture server.
Registry keys that define the Release module are created in the following path:
HKEY_LOCAL_MACHINE\Software\Kofax Image Products\Ascent Capture\3.0
The suggested registry key values are listed in the following table:
Document Storage Directories
Document storage directories, such as the directories for releasing XML/DTD, image, Image files,
and/or OCR full text files, cannot be the same as subdirectories of the Release working directory.
This is because the files stored in the Release working directory are temporary, and are deleted
after the batch is successfully released from Ascent Capture.
If you inadvertently specify the same path in the same format for a document storage directory
and the Release working directory (for example, the same path in UNC format for both
directories), an error will be generated when you attempt to save your release setup settings.
However, if the paths are referenced differently (for example, the Release working directory is
specified as a UNC path and a document storage directory is the same path that uses a drive
letter), no error will be generated when you save your settings.
Table 2. Registry Settings
Name Data
LowMemoryLimit 20
RespawnDelay 240