Encountering error connecting to notifier when attempting to import solution pack in Windows

book

Article ID: 159885

calendar_today

Updated On:

Products

Data Loss Prevention Enforce

Issue/Introduction

After a fresh installation of Symantec DLP in Windows, while attempting to import a solution pack, the import fails with the following messages:

INFO: Created listener proxy: bind address = 127.0.0.1, timeout = DEFAULT, server object host = 127.0.0.1

Jan 11, 2010 6:55:54 PM com.vontu.model.notification.rmi.RMINotificationModel connectToNotifier

WARNING: Error connecting to notifier at: 127.0.0.1:37328

Jan 11, 2010 6:55:54 PM com.vontu.model.Model createInstance

INFO: Created Model instance using: com.vontu.model.ojb.OjbAuthorizingModel

---------- Testing System Integrity ------------

--------------------- OK -----------------------

Jan 11, 2010 6:55:57 PM com.vontu.model.ojb.LockServerConnector logRemoteException

WARNING: Error performing registry lookup for lock server at 127.0.0.1:37328.

[org.apache.ojb.odmg.TransactionImpl] ERROR: Error while commit objects, do abort tx [email protected],

Error performing registry lookup for lock server at 127.0.0.1:37328.

Error performing registry lookup for lock server at 127.0.0.1:37328.

org.apache.ojb.broker.PersistenceBrokerException: Error performing registry look

Resolution

The error indicates that although per the import instructions Symantec DLP services were brought down, but there is an exception and that is the Notifier service.  The error calls out the lack of this service.

In Windows Services, stop all Symantec Data Loss Prevention services except

for the Notifier service. The Notifier service must remain running.

Stop the following services:

¦ Vontu Update

¦ Vontu Incident Persister

¦ Vontu Manager

¦ Vontu Monitor (if a single-tier installation)

¦ Vontu Monitor Controller

(unwritten, but ought to be there)

¦ Make SURE that Vontu Notifier is STARTED!