Symantec DLP Detection Server Controller Service starts and then stops after upgrading Enforce.

Products

• Data Loss Prevention Network Discover

Issue/Introduction

After upgrading DLP Enforce from 15.8 to 16.0; the Symantec DLP Detection Server Controller Service will start and then stop after about a minute.

 

Cause

You may see the following errors in the Monitor Controller log:

SEVERE: Error starting monitor controller
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'monitorController' defined in URL [jar:file:/<Install_Drive>:/Program%20Files/Symantec/DataLossPrevention/EnforceServer/16.0.00000/Protect/lib/jar/monitorcontroller.jar!/com/vontu/monitor/controller/MonitorController.class]: Unsatisfied dependency expressed through constructor parameter 6; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'subsystemControllerManager'

Caused by: ERROR XSLAE: Control file at <Install_Drive>\ProgramData\Symantec\DataLossPrevention\EnforceServer\16.0.00000\scan\incremental_index\MONITOR_CONTROLLER\INCREMENTAL_INFO\log\log.ctrl cannot be written or updated."

 

You may see the following errors in the Symantec DLP Detection Server Controller log"

 Error creating bean with name 'subsystemControllerManager' defined in URL [jar:file:/<Install_Drive>:/Program%20Files/Symantec/DataLossPrevention/EnforceServer/16.0.00000/Protect/lib/jar/monitorcontroller.jar!

Resolution

This can occur if the service account for the DLP services is changed during the upgrade process and the DLP services are left running under the old service account.

Perform the following to resolve the issue:

1. Stop all of the DLP services.
2. Change the logon for the DLP services to the correct account and save.
3. After the logon account for the all the DLP services has been updated; restart the DLP services per: Restart DLP Enforce services in the correct order.