› Known issues

Known issues

This topic contains information about potential issues that you may encounter while using Kofax FraudOne. Workarounds are included, as applicable.

Wrong build number in module information

1859938: In the module information of binaries and in the module overview the build number is not set.

Error in checkForDuplicatePasswords:ReadOldPasswords

1857525: When trying to change a user's password at the client logon, an error message "Authentication Failed" appears.

Administration Client initialization error displayed incorrectly

1788587: The Administration Client displays the error "JCS0417 Sival.initialize ( ): Cannot load Module fsxtk fsxtkkrn" during startup. The initialization is not required and the error message can be ignored.

ClientVersion is incorrectly calculated

1731512: When editing a user in the Administration Client, the server inserts a protocol entry and calculates the client version incorrectly.

Oracle: Incorrect timestamps used after DST change

713838: When editing a user in the Administration Client, the server inserts a protocol entry and calculates the client version incorrectly. Customer records displayed as "Verify Pending" cannot be verified due to an incorrectly stored timestamp (TIME_STAMP_VERIFY).

Workaround: This Oracle ODBC driver issue can be partially resolved using a wording ODBC driver/DBMS combination.

SetupCfg fails when used with a new Active Directory user as authorization source

1536287: If the user ID supplied for example to SetupCfg -importworkspace is an Active Directory user that is not already present in the user table but has the required access rights through a group membership then SetupCfg fails during the import.

Workaround: The "superuser" configuration to use an Active Directory group as the superuser should not be used before the SetupCfg activities are completed. Once SetupCfg work is completed, the superuser can be changed to a group using SBDebTab -resetusermanagement.

ServerInterface connection pool cannot address the ArchiveInterfaceServer

1472408: The Java Client expects to use the server type "SIGNINFO" to address an AIS server (typical port 2015) and NOT the real "SIGNINFO" server, which is just a sub function of the SignBase server.