Enforce Server must be configured before installing this hotfix
search cancel

Enforce Server must be configured before installing this hotfix

book

Article ID: 406862

calendar_today

Updated On:

Products

Data Loss Prevention

Issue/Introduction

Applying a hotfix to the DLP Linux Enforce Server and receive the following error:

"Enforce Server must be configured before installing this hotfix"

Environment

RHEL Linux OS

DLP 16.x

Cause

The following files are missing from the below path:

Path:

/etc/Symantec/DataLossPrevention/EnforceServer/<version>/Installation

drwxr-xr-x. 2 root root 4096 <date>  .
drwxr-xr-x. 3 root root   26 <date>  ..
-rw-r--r--. 1 root root    4 <date>  additionalLocaleOption
-rw-r--r--. 1 root root    0 <date>  bindHost
-rw-r--r--. 1 root root   22 <date>  configurationState
-rw-r--r--. 1 root root   32 <date>  dataDirectory
-rw-r--r--. 1 root root    7 <date>  detectionCommunicationDefaultCertificates
-rw-r--r--. 1 root root    9 <date>  discoverClusterRoleOption
-rw-r--r--. 1 root root    8 <date>  externalStorageOption
-rw-r--r--. 1 root root    8 <date>  fipsOption
-rw-r--r--. 1 root root   32 <date>  installationDirectory
-rw-r--r--. 1 root root   34 <date>  jreDirectory
-rw-r--r--. 1 root root   37 <date>  oracleHome
-rw-r--r--. 1 root root   14 <date>  oracleHost
-rw-r--r--. 1 root root    4 <date>  oraclePort
-rw-r--r--. 1 root root    7 <date>  oracleServiceName
-rw-r--r--. 1 root root    7 <date>  oracleUsername
-rw-r--r--. 1 root root   11 <date>  serviceUserUsername

Resolution

The Admin can re-run the EnforceServerConfigurationUtility as outlined in documentation here

The tool is located in the following path:

Path:
/opt/Symantec/DataLossPrevention/EnforceServer/<version>/Protect/install/EnforceServerConfigurationUtility

 

Or, as in this reported instance, the Enforce Server had a copy Disaster Recovery Linux Enforce Server. This server held a copy of the original files in the Installation directory.

The Admin copied the missing files to the Enforce Server and was able to re-run the hotfix without incident