System Overview crashes and a red banner is displayed

Products

• Data Loss Prevention
• Data Loss Prevention API Detection
• Data Loss Prevention API Detection for Developer Apps Virtual Appliance
• Data Loss Prevention Cloud Detection Service
• Data Loss Prevention Cloud Detection Service for Endpoint
• Data Loss Prevention Cloud Detection Service for ICAP
• Data Loss Prevention Cloud Detection Service for REST
• Data Loss Prevention Cloud Package
• Data Loss Prevention Cloud Prevent for Microsoft Office 365
• Data Loss Prevention Cloud Service for Discovery/Connector
• Data Loss Prevention Cloud Service for Email
• Data Loss Prevention Cloud Storage
• Data Loss Prevention Core Package
• Data Loss Prevention Data Access Governance
• Data Loss Prevention Discover Suite
• Data Loss Prevention Endpoint Discover
• Data Loss Prevention Endpoint Prevent
• Data Loss Prevention Enforce
• Data Loss Prevention Enterprise Suite
• Data Loss Prevention for Mobile
• Data Loss Prevention Form Recognition
• Data Loss Prevention Network Discover
• Data Loss Prevention Network Monitor
• Data Loss Prevention Network Monitor and Prevent for Email
• Data Loss Prevention Network Monitor and Prevent for Email and Web
• Data Loss Prevention Network Monitor and Prevent for Web
• Data Loss Prevention Network Prevent for Email
• Data Loss Prevention Network Prevent for Email Virtual Appliance
• Data Loss Prevention Network Prevent for Web Virtual Appliance
• Data Loss Prevention Network Protect
• Data Loss Prevention Oracle Standard Edition 2
• Data Loss Prevention Plus Suite
• Data Loss Prevention Sensitive Image Recognition

Issue/Introduction

System Overview page crashes when a Detection Server is started. This occurred after upgrading from DLP 15.8 MP3 to DLP 16.1 MP1.
- No Detection Servers Running, the System Overview page displays normally
- Email Prevent Servers Running, the System Overview page displays normally
- WebPrevent Servers Running, this causes the System Overview page to crash
- Stopping the WebPrevent Servers will allow the System Overview page to display normally again.

 

Error Message:

Level: SEVERE

Source: com.vontu.manager

Message: [/SystemOverview] 

Cause:

org.springframework.dao.IncorrectResultSizeDataAccessException: query did not return a unique result: 2; nested exception is javax.persistence.NonUniqueResultException: query did not return a unique result: 2org.springframework.dao.IncorrectResultSizeDataAccessException: query did not return a unique result: 2; nested exception is javax.persistence.NonUniqueResultException: query did not return a unique result: 2

at org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:385)

at org.springframework.orm.jpa.vendor.HibernateJpaDialect.translateExceptionIfPossible(HibernateJpaDialect.java:235)

at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.translateExceptionIfPossible(AbstractEntityManagerFactoryBean.java:551)

at org.springframework.dao.support.ChainedPersistenceExceptionTranslator.translateExceptionIfPossible(ChainedPersistenceExceptionTranslator.java:61)

at org.springframework.dao.support.DataAccessUtils.translateIfNecessary(DataAccessUtils.java:243)

at org.springframework.dao.support.PersistenceExceptionTranslationInterceptor.invoke(PersistenceExceptionTranslationInterceptor.java:152)

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)

at org.springframework.data.jpa.repository.support.CrudMethodMetadataPostProcessor$CrudMethodMetadataPopulatingMethodInterceptor.invoke(CrudMethodMetadataPostProcessor.java:145)

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)

at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:241)

at com.sun.proxy.$Proxy344.getLastDetectorHeartbeat(Unknown Source)

at com.vontu.monitor.controller.servercontrol.ServerCommunicatorUDS.getStatus(ServerCommunicatorUDS.java:99)

at com.vontu.monitor.controller.servercontrol.DataFlowServerController.getStatuses(DataFlowServerController.java:72)

at com.vontu.monitor.controller.servercontrol.RemotableWrapper.getStatuses(RemotableWrapper.java:65)

 

 

 

Environment

n/a

Cause

This is caused by duplicate data in the database. In DLP 15.8 MP3 the duplicate data was simply ignored. But after upgrading to the UDS Detection Servers in DLP 16.1, these servers do not allow for the duplicate data.

Resolution

To confirm if this is an issue for you, you will need to run the two attached sql queries and submit them to support for review while referencing this KB article.

- Get_Duplicate_Statuses.sql
- Get_Duplicate_Heartbeat.sql

These will run a query against the corresponding table to look for any duplicate entries.
- If any data shows up, then you have this problem.
- If no data shows up, then there were no duplicate entries and this is not applicable to you.

For the fixes you will need to submit a ticket as this requires database modification which will require engineering approval. Submit the case normally and simply reference this KB article.