Resolved issues

This topic lists previously reported issues that are resolved in Kofax FraudOne 4.6.0. Each Kofax FraudOne product release is cumulative and includes the resolved issues from earlier releases.

Database issue after password change

1846333: If an administrator changed the password for a user who did not belong to a group, a database issue occurred.

Active Directory user search issue

1844206: The user ID field in the Active Directory search dialog box was not updated when the user selection was changed.

Issue with SBDebTab

1843920: The MSSQL specific database script failed to reset the object IDs in the RULES table due to a keyword conflict.

Error after wrong password was entered

1841182: When trying to log in with a wrong password, the client displayed the "Authentication failed" message, but on the Server Manager the following error was posted:

E 2022-08-22 06:48:53.5 Q SB-Server: VBS2268 [Zu90S] ODBC: Error in incrementPasswordRetryCount:incrementPasswordRetryCount Execute -1 SQL_ERROR

E 2022-08-22 06:48:53.5 Q SB-Server: VBS2269 [Zu90S] ODBC: State:22005, Native Error:-99999, Message: [IBM][CLI Driver] CLI0112E Error in assignment. SQLSTATE=22005

Unable to crop grayscale signature from account image

1840667: From the account image pane (or SignInfo view) if users masked a signature from a grayscale image and created a new signatory, the image in the signatory list appeared as a black rectangle.

Saving consecutive changes in the Java Client was not possible

1840485: The Java Client compared the dates incorrectly when saving the customer/account. Last changed and query dates were incorrectly compared (comparing by object reference instead of equals).

Java Client problem with empty result messages

1838496: The Java Client was running in an error situation when a result message without content was received.

Unable to search for Not Verified Customer

1836858: When using the Java Client to search for a customer, the following message appeared:

"You are not allowed to inquire the customer because the customer isn't verified yet"

Issue with User Management Module with Oracle DB

1833321: When FraudOne was used with an Oracle database, an error occurred if users were not able to log in, or if they were not able to perform a search.

E 2022-07-30 00:52:52.6 Q SB-Server-1: VBS2268 [Zu90S] ODBC: Error in checkUserAuthentication:checkUserAuthentication ReadCredentials Fetch -1 SQL_ERROR

E 2022-07-30 00:52:52.6 Q SB-Server-1: VBS2269 [Zu90S] ODBC: State:HY000, Native Error:1406, Message: [Oracle][ODBC][Ora]ORA-01406: fetched column value was truncated

Signature Reference Filter is missing a deprecated library

1827770: The Signature Reference Filter reported an error when started due to the missing of the deprecated library SicProperBridge.dll.

Administration Client database error

1811908: If you navigated to Administration Client > User Administration > Reports > Audit and then selected Display, the following error appeared:

The database has a problem.

Authentication Failed error in Administration Client

1808038: When the password was changed in the Administration Client, the client received RC 35 ("The database has reported a problem"), and in the database the following error message was found:

E 2022-04-20 05:51:46.8 Q SB-Server-1: VBS2269 [Zu90S] ODBC: State:HY000, Native Error:0, Message: [Microsoft][SQL Server Native Client 11.0]Connection is busy with results for another command

Incorrect calculation of inherited user rights

1799992: The "user administration" menu was disabled when the user inherited rights from the group to access the SB_Administrator right and logged in with the userid.

User with null adminclass not able to see all groups

1797376: If the groups had a non-null value in adminclass, a user with the super administrator userid (adminclass is null) was not be able to see these groups. A super administrator now sees all, including the userid and groups that belong to adminclass.

Currency.properties were not read from the database

1796729: Currency.properties were not read from the database, but from the file system.

Signature card display issue

1786015: There were sporadic error messages when displaying signature cards. The error message was:

"Account search: Wrong message type received."

Monitor log error

1785651: After restarting the FraudOne server after a network connection issue, the Monitor log included the following message:

E 2022-03-06 23:05:53.4 C SB-Data-4: OC20048 OC20048 [Zu90H] Customer hook version later than installed server version, execution continues but hooked functions may be missing

Different display between Java Client and Thin Client

1780798: The Signatory list of a SignBase Customer couldn’t be displayed in the Java Client, but the Thin Client displayed the list correctly.

Server Interface: Unable to read/write SerialNumberRange

1759798: When adding a SerialNumberRange to StockImage, the following exception occurred:

de.softpro.signplus.serverinterface.MessageException: Stock Image does not contain serial number ranges

SPFreeImage.dll was not included in SignPlus.war

1716118: The FraudOne Thin Client was not displaying dynamic signatures in an account. This happened because SPFreeImage was not included in WEB-INF\lib\bin.

Long validation time for the Active Directory users

1714376: Because the server took a lot of time for the verification of the Active Directory users and their groups, it took a long time to open the user administration window in the Administration Client.

Attman5.exe became unresponsive

1697987: After an upgrade to FraudOne 4.5.0 on Windows Server 2019, Attman5.exe was unresponsive.

Check loading slowdown

1697686: A significant slowdown occurred when loading an account with a high number of signatories.

SignBase Server reported field error message

1696266: When trying to save the workspace in the Java Client, the field error message "cannot insert NULL into ("DEB"."CUSTOMER"."OPID_ENTRY")" appeared, stating that the database has detected a problem.

ServerInterface.jar incorrectly read transaction header

1693758: The transaction header sent from the server was not fully read because of a delay in tcp/ip.

List of checks displayed incorrectly after item was processed

1679712: After a decision was made for one check, the list of checks was not accurate when it was refreshed.

Missing message implementation in the Archive Interface Server

1677424: A message to received configuration information was not implemented in the new Archive Interface Server AIS2.

Java Client: Sort order reset after decision in the list of checks

1674949: The sort order was switched back to the default once the current item was decided and the current list was displayed again.

Java Client: Unable to delete account or customer records

1669971: During the deletion of the account, the Java Client created an additional serial range number (type 22). This serial range did not exist in the database. However, the Java Client sent a request to remove it and SignBase server returned error code 38.

Java Client: Account Search did not work in Visual Technical Verification Queue screen

1643601: The FraudOne Java Client was unable to display the signatory list when starting an account search out of the Visual Technical Verification queue.

Server Manager unresponsive after Database connection outage

1643600, 1461443: The Server Manager became unresponsive after losing a connection to the Oracle database server.

Validation didn't support Content Type 8 or 9

1542583: When trying to use the validation script, the following error message appeared:

EXTENSION6:1,1: Extension incorrect type (8)

Entries with Content Type = 8 or 9 were detected in the extension tables.

Database migration script generated inconsistent SPX_UR records

1523983: The FraudOne SignBase database migration script generated invalid records in the SPX_UR table when it added the new access rights for SB_EditSerial, SB_EditHighlight and SP_CoreProperties rights.

SAE Server failed to write a result when throughput license

1468746: When the GIA-SAE Automat/Server were processing documents and the throughput license limit had been reached, the GIA Server attempted to write a result for each document and failed with an error message such as:

2020-05-19 08:10:23.7 L GIA-Server-2: AUS0237 GIA Throughput license exceeded!