Kofax Ascen 7.0 Release Script - Manual (Page 26)

Ascent® 7.0 Release Script for IBM Content Manager for iSeries 5.1-5.3 Release Notes
22 Kofax, Inc.
Known Problems
This section contains information about known problems with the Ascent 7.0 Release Script for
IBM Content Manager for iSeries.
Problems When Installing on Windows XP
If you are installing the Ascent 7.0 Release Script for IBM Content Manager for iSeries on a
Windows XP Professional workstation and you specify a mapped drive, you will receive the
following error message. (SPR 31250)
Error 1904. Module <mapped drive> failed to register. HRESULT -2147467259. Contact
your support personnel.
Workaround: The error message is incorrect and can simply be ignored. Click the Ignore button
and the release script will successfully install and register the release script.
If you click the Abort button, the installation will end. If you click the Retry button, you will
receive the above error message again.
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 that the Cancel button is clicked, the release script may be un-registered.
In such a case, once you attempt to login to the release script, login will fail. (SPR 31221)
Workaround: If this problem occurs, run Repair. Refer to Repairing the Release Script on page 11
for more information. Alternatively, you can re-register the release script in the Release Script
Manager.
Releasing Date Fields
When releasing Date fields for text constants, you must make certain that you specify the date
format as YY/MM/DD, where YY is the year, MM is the month, and DD is the day of the month. If
you enter a different format, the release setup will not notice that you entered an invalid format
for a text constant and will allow you to save your settings. The Content Manager release script is
not able to validate the Date fields at release when an invalid format is used. The documents will
release successfully.
Workaround: You can write a custom validation script that checks the date format when batches
are processed with the Validation module, and adjust the format as necessary.
Index Values With Apostrophes
If you use an Ascent Capture Index value that contains an apostrophe (') for a folder, you will
receive the following error message at release. (SPR 17622)
DGL0394A: Error in ::SimLibSearch [FRN=6297, ExtRC=0] (STATE) : 0]
Workaround: Edit the Index value to remove the apostrophe.