Filereader fails to start with error "Unable to open JDBC Connection for DDL execution"

Products

• Data Loss Prevention Network Prevent for Email
• Data Loss Prevention

Issue/Introduction

The FileReader fails to start with the following errors and warnings:

Class: org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator
Method: initiateService
Level: WARN
Message:  HHH000342: Could not obtain connection to query metadata : Cannot create PoolableConnectionFactory (java.net.ConnectException : Error connecting to server localhost on port 1,527 with message Connection timed out (Connection timed out).)

Class: org.hibernate.engine.jdbc.spi.SqlExceptionHelper
Method: logExceptions
Level: WARN
Message:  SQL Error: 0, SQLState: null

Class: org.hibernate.engine.jdbc.spi.SqlExceptionHelper
Method: logExceptions
Level: ERROR
Message:  Cannot create PoolableConnectionFactory (java.net.ConnectException : Error connecting to server localhost on port 1,527 with message Connection timed out (Connection timed out).)

Class: org.springframework.context.annotation.AnnotationConfigApplicationContext
Method: refresh
Level: WARNING
Message:  Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in com.vontu.config.jpapersistence.JpaPersistenceSpringConfiguration: Invocation of init method failed; nested exception is javax.persistence.PersistenceException: [PersistenceUnit: default] Unable to build Hibernate SessionFactory; nested exception is org.hibernate.exception.GenericJDBCException: Unable to open JDBC Connection for DDL execution

Class: com.vontu.messaging.FileReaderSetup
Method: initialize
Level: SEVERE
Message:  (DETECTION.3) Failed to initialize Detection
java.lang.ExceptionInInitializerError
    at com.vontu.discover.remediation.detection.DiscoverServerRemediationDetectionConfiguration.getCatalogEntryService(DiscoverServerRemediationDetectionConfiguration.java:106)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in com.vontu.config.jpapersistence.JpaPersistenceSpringConfiguration: Invocation of init method failed; nested exception is javax.persistence.PersistenceException: [PersistenceUnit: default] Unable to build Hibernate SessionFactory; nested exception is org.hibernate.exception.GenericJDBCException: Unable to open JDBC Connection for DDL execution
Caused by: ERROR 08001: java.net.ConnectException : Error connecting to server localhost on port 1,527 with message Connection timed out (Connection timed out).

Class: com.vontu.logging.LocalLogWriter
Method: write
Level: SEVERE
Message:  File Reader failed to start. Error starting File Reader. java.lang.ExceptionInInitializerError. No incidents will be detected.

Resolution

Try adding the following path to the system PATH environment variable.  Please verify the below path and make sure its valid before adding it to the PATH variable.

C:\Program Files\Symantec\DataLossPrevention\ServerPlatformCommon\<ver>\Protect\lib\native

Make sure to update the drive letter to where DLP is installed.

 After this please restart DLP services and see if the issue persists.  If the issue still happens please continue below.

If this server is not a discover server, then you can disable remediation on this server to see if this helps.  Though it would be better to follow the last step and reinstall the software.

For this, modify the protect.properties file.

# Flag to turn on/off the Remediation Detection Subsystem on Discover

com.vontu.discover.detectionserver.remediation.detection.enabled = true (change true to false)

 

Failing the above, please uninstall and reinstall the detection server.  You do not need to remove it from enforce, just uninstall and reinstall the detection server.  Please always make sure to take a backup of the server before doing so.

Additional Information

In another case, simply restarting the Network Protect server itself, not just the services, restored the internal communications.
After which, the server started running again.