"Forcepoint DLP could not be launched" error on accessing Data Tab in Forcepoint Security Manager
- Article Number: 000016033
- Products: Forcepoint DLP, TRITON AP-DATA
- Version: 8.7, 8.6, 8.5, 8.4, 8.3
- Last Published Date: October 13, 2020
Notes & Warnings
If the issue happens with a specific DLP administrator rather than for all Administrators in the Forcepoint Security Manager, see Specific DLP Administrator User Unable to Access the Forcepoint DLP Management UI. |
Problem Description
When accessing the DATA tab in the Forcepoint Security Manager, the following error is displayed:
"Forcepoint DLP could not be launched" |
Resolution
In order to resolve the issue, consider the options below. Option 1 Restart the DLP Server if possible, and wait for all the Forcepoint services to start correctly. Alternatively, restart all of the Data Security services. If the above option does not resolve the situation, proceed to the next steps below. Option 2 Important Log into the server with the same account used to run the Websense Services. Performing these steps with the wrong user can break the environment.
Note In v8.5 and later, the work folder will be labeled wbsnWork. In versions prior to v8.5, rename the work folder as mentioned above.
Note In v8.5 and later, the work folder will be wbsnWork. In versions prior to v8.5, rename the work folder as mentioned above. In some instances, users have reported there being no work folder in this location. If you do not see any work folder listed to begin with, then create one.
Note In v8.5 and later, once you have renamed the wbsnWork folder to wbsnWork.old, then create a new wbsnWork folder. In versions prior to v8.5, rename the work folder as mentioned above.
Check to see if there has been a recent change to the SQL credentials used by the DLP system. This can be confirmed by running a Modify setup (Not Repair) of the Forcepoint installer. See below for the steps to follow. Running the Modify setup will confirm the current SQL configuration and throw an error if anything is incorrect. Important Log into the server with the same account used to run the Websense Services. Performing these steps with the wrong user can break the environment.
If the Data tab is not able to load, stays in the Processing state indefinitely, or is generally sluggish when performing a deployment, please refer to the following article for more information. The steps to follow are also listed below:
Note No other XML files, including backups of dlp.xml, must be present within the localhost directory
Additionally, clear the Tomcat cache in addition to recreating the DLP folder within webapps for any changes to dlp.xml:
Review dlp-all.log from %DSS_HOME%tomcat\logs\dlp\ on the Windows Management Server. If you see many error messages similar to the following, please check the size of the wbsn-data-security from the SQL server also check whether enough space is available on the SQL Server: The transaction log for database 'wbsn-data-security' is full due to 'LOG_BACKUP'. Option 6 Review dlp-all.log for error messages similar to the following pertaining to ActiveMQ, active-mq, and bean property: ERROR org.apache.activemq.broker.BrokerService - Failed to start ActiveMQ JMS Message Broker. Reason: org.apache.activemq.kaha.RuntimeStoreException: java.io.EOFException Perform the following steps:
Option 7
Ensure that the following folders do not contain non-default backup files (even if they are renamed):
Option 8 If you have followed all the above steps and are still unable to access the DLP tab in the Forcepoint Security Manager, then please open a case with Technical Support and provide the following logs from the DLP Server:
Keywords: DLP Console; Forcepoint DLP could not be launched; Data Module; DSS Console issue; DLP Not launched; |
Article Feedback
Want 24/7 Tech Support?
Learn more