Cannot not load the DLP Enforce console - receiving 404 Errors
search cancel

Cannot not load the DLP Enforce console - receiving 404 Errors


Article ID: 186978


Updated On:


Data Loss Prevention Endpoint Prevent


You are unable to access the Enforce console. A 404 error is being received repeatedly.

  • Restarting the DLP and Oracle service does not resolve the issue
  • Rebooting the server does not resolve the issue
  • You are able to connect to the DB via sqlplus

Page cannot redirect and keeps looping at “https://<yourcompany>/ProtectManager/GlobalDialog?type=NOT_FOUND”


Release : 14.x, 15.x


You may see this kind of entry in the localhost log:

20 Mar 2020 17:31:47,414- Thread: 28 SEVERE [com.vontu.util.jdbc.JDBCLogger] Failed to initialize JDBC Logging
java.nio.file.NoSuchFileException: C:\Vontu\Protect\logs\debug\manager_jdbc_0.log.lck
java.nio.file.NoSuchFileException: C:\Vontu\Protect\logs\debug\manager_jdbc_0.log.lck
 at sun.nio.fs.WindowsException.translateToIOException(

Note that it may not always be the jdbc_0.log.lck but some .lck file has become corrupted.
This may be due to a file system corruption, a server crash, or a backup such as P2V having been made without first stopping the DLP services


  1. Stop the DLP services see this article for the correct order of DLP service starts
  2. Move all of the log files out of the log folders to a backup location, leaving only the log folder and its tomcat, and debug child folders intact
  3. Restart the services in the correct order
  4. Allow a few minutes for the services to get up and running, then load the console