After following https://knowledge.broadcom.com/external/article?articleId=196171 Enforce console is not loading and showing HTTP 404 error.
Verified DB connection using DB client. DB report also shows no issue with DB. Listener status is fine as well. All enforce services are running.
Tomcat logs show below errors -
24 Mar 2023 13:53:32,472- Thread: 17 SEVERE [org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/ProtectManager]] Exception sending context initialized event to listener instance of class [com.vontu.manager.spring.ManagerContextLoaderListener]
Cause:
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'incidentActionRequestFetcher' defined in URL [jar:file:/C:/Program%20Files/Symantec/DataLossPrevention/EnforceServer/<version>/Protect/tomcat/webapps/ProtectManager/WEB-INF/lib/manager.jar!/com/vontu/manager/enduserremediation/communication/incidentaction/requestfetcher/IncidentActionRequestFetcher.class]: Unsatisfied dependency expressed through constructor parameter 2; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'incidentActionRequestProcessor' defined in URL [jar:file:/C:/Program%20Files/Symantec/DataLossPrevention/EnforceServer/<version>/Protect/tomcat/webapps/ProtectManager/WEB-INF/lib/manager.jar!/com/vontu/manager/enduserremediation/communication/incidentaction/requestprocessor/IncidentActionRequestProcessor.class]: Unsatisfied dependency expressed through constructor parameter 1; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.vontu.manager.enduserremediation.communication.incidentaction.requestprocessor.IncidentRemediationRequestProcessor]: Constructor threw exception; nested exception is 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: 2
DLP ProtectUsers table has 2 "Administrator" users in it, due to AD sync and we need to remove that newly added "Administrator" user.
This is resolved in DLP 16.1, if upgrading is not possible and the issue is occurring on a supported release, please contact support.