Error "2920: Failed to load database profile" when indexing an Exact Data Match profile
Last Updated January 05, 2019
You see the following error in your Data Loss Prevention (DLP) Enforce console on the System > Servers > Overview page when indexing an Exact Data Match (EDM) profile upon save or at a scheduled time.
Summary Failed to load database profile
Detail Failed to load RAM index from \Vontu\Protect\index\DataSource.nnn.nnnn.rdx.
No incidents will be detected against database profile "[Database_Profile_Name] (SADB.EMPLT)" version nnnn.
Attempting to index the EDM from a remote machine without using a remote indexer.
Copy the EDM source file locally on the Enforce server and retry the index.
Log into the Enforce console.
Go to Manage > Data Profiles > Exact Data.
Click on Add Exact Data Profile.
Enter a desired name.
For Data Source, select the "Upload Data Source to Server Now" radio button.
Browse the local copy of your source file on the Enforce server.
Imported Document ID: TECH218929
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe