(-3) General (unknown) error" Encountered During Forcepoint DLP Secondary Server Registration

(-3) General (unknown) error" Encountered During Forcepoint DLP Secondary Server Registration

Summary
Restart the Websense Data Security Fingerprinting Database to resolve the issue.
Problem
When attempting to complete a Modify of the Forcepoint DLP installer on a Secondary Windows Server to register the machine to a DLP Management Server, an popup containing "(-3) General (unknown) error" appears during "Registering management server Components" and the process fails. When the Cancel button is pressed, a generic 1720 error is returned. 



The Modify-Data-Security.log under %TEMP% shows an entry similar to the following:

Internal Error 2835. ErrorIcon, ErrorDialog
MSI (s) (E8:04) [03:33:22:302]: Product: Data Security -- Error 1720. There is a problem with this Windows Installer package. A script required for this install to complete could not be run. Contact your support personnel or package vendor. Custom action RegisterComponents script error -3, : Line 180, Column 5,

%DSS_HOME%tomcat\Logs\dlp\dlp-all.log on the DLP Manager Server:

com.sun.xml.internal.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: WebMethodPerformer: Exception thrown: Query <END TRANSACTION;> failed ! Error: <database is locked> Please see the server log to find more detail regarding exact cause of the failure.

%DSS_HOME%Logs\FPR.log on the DLP Manager Server:

FATAL root - WebMethodPerformer: Exception thrown: Error in function CppSQLite3DB::execQuery. query <SELECT FILE_COLLECTION_ID,FPNE_REVISION FROM TB_FILE_COLLECTION WHERE FPNE_REVISION>=0 ORDER BY FILE_COLLECTION_ID;>, error <database is locked>, nRet <5>
ERROR Exception - Query <END TRANSACTION;> failed ! Error: <database is locked>
FATAL root - WebMethodPerformer: Exception thrown: Query <END TRANSACTION;> failed ! Error: <database is locked>

 

Solution

If above errors are present, restart the Websense Data Fingerprint Database service on the DLP Manager and repeat the registration process again. The procedure should now be successful.

If the issue persists, then access the Forcepoint Management Server as the DLP service account and complete a modify of both the Forcepoint Management Infrastructure and Forcepoint DLP installers and confirm that all of the DLP services are running before pressing the Retry button again on the Secondary Server.

    • Related Articles

    • DLP module User Interface Error

      Observation During the session, it was observed that the Forcepoint DLP module encountered a UI error (Forcepoint DLP could not be launched). This issue was caused by corrupted files in the following directories: - `%DSS_HOME%tomcat\wbsnData\` - ...
    • Forcepoint DLP backup

      How do I back up and restore Forcepoint DLP? Backup and Restore | Forcepoint DLP | 29-Apr-2022 Back up your Forcepoint DLP system periodically to safeguard your policies, forensics, configuration data, fingerprints, encryption keys, and more. ...
    • How to Create and Install a New Server Certificate for the Forcepoint Management Infrastructure

      Summary Steps provided to utilize a 3rd party signed certificate. Notes and Warnings The following information describes editing the registry. Before proceeding, backup the registry, and be sure you understand how to restore the registry if a problem ...
    • HTTP Status 404" Error Occurs within the Forcepoint Security Manager

      Problem When logging on to the Forcepoint Manager web UI, why do I see the following error message? "HTTP status 404 The requested resource (/mng/) is not available." OR "HTTP status 404 - /manager/lgon/pages/login.page.jsf Type: Status Report ...
    • Determining the SQL Database Location for Forcepoint Components

      Summary Describes options for finding the SQL server connection details from the Forcepoint Management Server. Problem While troubleshooting an issue, Technical Support may request to investigate the SQL database of a Forcepoint product. If the ...