Not able to load the Enforce UI due to the Manager service failing to start
search cancel

Not able to load the Enforce UI due to the Manager service failing to start

book

Article ID: 159663

calendar_today

Updated On:

Products

Data Loss Prevention Enforce

Issue/Introduction

After an upgrade, the Data Loss Prevention (DLP) Enforce UI does not load, and you cannot log in.

The DLP Manager service fails to start, with error "1067: The process terminated unexpectedly."

When starting the DLP Manager service, you see the error:

Could not start the Manager service on Local Computer.
1067: The process terminated unexpectedly.

The SymantecDLPManager.log repeatedly shows the following error:

ERROR  | wrapper  | 2010/09/21 10:40:03 | JVM exited while loading the application.
STATUS | wrapper  | 2010/09/21 10:40:07 | Launching a JVM...
INFO   | jvm 4    | 2010/09/21 10:40:07 | Error occurred during initialization of VM
INFO   | jvm 4    | 2010/09/21 10:40:07 | Could not reserve enough space for object heap
INFO   | jvm 4    | 2010/09/21 10:40:07 | Could not create the Java virtual machine.
ERROR  | wrapper  | 2010/09/21 10:40:08 | JVM exited while loading the application.

Cause

The computer is trying to use more RAM for the Java Virtual Machine (JVM) than what is allowed by the operating system.

 

Resolution

Change the following defaults in \Symantec\DataLossPrevention\EnforceServer\Services\SymantecDLPManager.conf:
# Initial Java Heap Size (in MB)
wrapper.java.initmemory = 1378

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory = 2048

To change the default settings:

  1. In a text editor, open SymantecDLPManager.config.
  2. Locate the lines referenced above.
  3. Set both the initmemory to "2048" and maxmemory values to "4096".
  4. Save the changes to SymantecDLPManager.config
  5. Restart the SymantecDLPManager service

*Note: You may need to increase the maxmemory setting more depending on the the available RAM on the system and the size of the DLP environment.