After the Enforce installation, the Incident persister and Monitor Controller services can't start up

book

Article ID: 160539

calendar_today

Updated On:

Products

Data Loss Prevention Enforce

Issue/Introduction

After the Enforce installation, the Incident persister and Monitor Controller services don't start with the following error in the logs:

VontuIncidentPersister.log and VontuMonitorController.log:

STATUS | wrapper  | 2011/02/02 16:15:23 | Launching a JVM...
INFO   | jvm 1    | 2011/02/02 16:15:23 | WrapperManager: Initializing...
INFO   | jvm 1    | 2011/02/02 16:15:24 | [org.apache.ojb.broker.metadata.RepositoryXmlHandler] ERROR: Exception while read metadata
INFO   | jvm 1    | 2011/02/02 16:15:24 | Can't assign the specified jdbc field-type 'BIGINT' for field:
INFO   | jvm 1    | 2011/02/02 16:15:24 |       <field-descriptor
INFO   | jvm 1    | 2011/02/02 16:15:24 |         name="maxKey"
INFO   | jvm 1    | 2011/02/02 16:15:24 |         column="MAX_KEY"
INFO   | jvm 1    | 2011/02/02 16:15:24 |         jdbc-type="BIGINT"

MonitorController0.log:

INFO: Connected to lock server at 127.0.0.1:37328.
02.?ub.2011 16:15:20 com.vontu.model.Model createInstance
SEVERE: model.startup.error
com.vontu.model.DataAccessRuntimeException: org.apache.ojb.broker.metadata.MetadataException: Can't read repository file 'com/vontu/model/data/ojb/repository.xml'
 at com.vontu.model.ojb.OJBSystem.checkConnectionStatus(OJBSystem.java:1032)
 at com.vontu.model.ojb.OJBSystem.start(OJBSystem.java:157)
 at com.vontu.model.ModelProxy.start(ModelProxy.java:202)

Resolution

The problem is related to the Operating System "Regional and Language Options". Follow these steps if you have Windows 2008 R2 64 bits:

1. Open the Control Panel -> Regional and Language Options

2. Click on Administrative TAB

3. Click on Copy Settings button

4. Verify that the "New User Accounts" would have English (US) listed in all fields

If the settings is different, you have to unistall the Enforce, change the "New User Accounts" settings as above, reboot the server and perform a new Enforce installation.

The E-track 1805050 is related to this issue.