eDiscovery fails to start due to missing datastore folders

book

Article ID: 100047797

calendar_today

Updated On:

Description

Error Message

Client Browser:  

Clearwell is Currently Unavailable for Use

or

HTTP Status 500 - [#71000] Admin Services Error: service not initialized - clustermanager.clustermanager

Server.yyy-mm-dd.log:  

If the property esa.cluster.externalBaseDir is not set:

Unable to open data directory D:\CW\V91\data\esadb\dataStore_cluster_1_########
[#156060] Unable to access database locator {eDP-App1.eDP.lab, localhost, esadb_lds_cluster_1} with state INVALID:[MISSING DATA DIRECTORY]

If the property esa.cluster.externalBaseDir is set to a network share:

Unable to open external data directory \\Unable to open external data directory \\eDP_Server.domain.local\extdata\esadb\dataStore_cluster_1_########
Unable to access database locator {eDP_Server.domain.local, localhost, esadb_lds_cluster_1} with state INVALID:[MISSING EXTERNALIZABLE DATA DIRECTORY]

Cause

eDiscovery shell processes fail to load after a services restart due to master case template datastore folder(s) missing in the ExtData location.

The reasons the folder(s) could be missing is due to:

  • Antivirus does not have the proper exclusions for eDiscovery and it has removed / quarantined some of the folders
  • This may occur after a node has been removed from a clustered environment.
  • If the disk drive that the folders reside on is failing, the folder could be corrupt or lost

The following five datastore folders are required in the ExtData location.  These folders do not contain data, but are the master case template folders used for case creation.

The ClusterUpdateService checks for them in the following order:

dataStore_cluster_1_########
dataStore_appliance_2_########
dataStore_case_3_########
dataStore_case_group_4_########
dataStore_case_appliance_5_########

Resolution

  1. Navigate to the ExtData\esadb\ location mentioned in the server log error above and verify which datastore folder(s) are missing.
    • These folders need to be recreated and can only be done once the expected name is identified in the server log.
    • The ######## is an internal numeric identifier and is required in the folder name.
  2. Create a folder in ExtData\esadb\ location with the name exactly as indicated in the server log error, including the numeric identifier.
  3. Restart services.
  4. Check the server log for the above error and note the name of the next missing datastore folder.
  5. Repeat steps 2 and 3 until all the missing master case template folders have been recreated and this error is no longer seen in the server log.

 

Issue/Introduction

The eDiscovery application is unavailable after a services restart.