Hi Geeks,
Need your valuable inputs to resolve management console issue. This is a fresh install of 14.6 and im facing the below issue.
https://localhost/ProtectManager/GlobalDialog?type=NOT_FOUND
The URL is always get struck here when looked at log files i could see few more errors but unable to resolve the issue.
NOTE:
1) We are able to connect to remote protect DB without a problem
2) Check the acounts whether locked or expired found to be clean.
3) MS Patches have been installed KB2919355 and KB2919442
In the installation logs i could find this error message
Jan 17, 2017 12:15:43 PM com.vontu.util.config.SystemProperties load
SEVERE: Unable to load SystemProperties, property 'com.vontu.properties' is not defined
but when i look into tomcat config logs "localhost" i could see many more.
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'formRecognitionIndexTaskManager' defined in URL [jar:file:/C:/SymantecDLP/Protect/tomcat/webapps/ProtectManager/WEB-INF/lib/manager.jar!/com/vontu/manager/admin/formrecognitionprofiles/task/FormRecognitionIndexTaskManager.class]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.vontu.manager.admin.formrecognitionprofiles.task.FormRecognitionIndexTaskManager]: Constructor threw exception; nested exception is java.lang.UnsatisfiedLinkError: C:\SymantecDLP\Protect\lib\native\PDFiumInterface.dll: Can't find dependent libraries
Caused by: org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.vontu.manager.admin.formrecognitionprofiles.task.FormRecognitionIndexTaskManager]: Constructor threw exception; nested exception is java.lang.UnsatisfiedLinkError: C:\SymantecDLP\Protect\lib\native\PDFiumInterface.dll: Can't find dependent libraries
Caused by: java.lang.UnsatisfiedLinkError: C:\SymantecDLP\Protect\lib\native\PDFiumInterface.dll: Can't find dependent libraries
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'formRecognitionIndexTaskManager' defined in URL [jar:file:/C:/SymantecDLP/Protect/tomcat/webapps/ProtectManager/WEB-INF/lib/manager.jar!/com/vontu/manager/admin/formrecognitionprofiles/task/FormRecognitionIndexTaskManager.class]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.vontu.manager.admin.formrecognitionprofiles.task.FormRecognitionIndexTaskManager]: Constructor threw exception; nested exception is java.lang.UnsatisfiedLinkError: C:\SymantecDLP\Protect\lib\native\PDFiumInterface.dll: Can't find dependent libraries
Caused by: org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.vontu.manager.admin.formrecognitionprofiles.task.FormRecognitionIndexTaskManager]: Constructor threw exception; nested exception is java.lang.UnsatisfiedLinkError: C:\SymantecDLP\Protect\lib\native\PDFiumInterface.dll: Can't find dependent libraries
17 Jan 2017 15:27:46,948- Context [/ProtectManager] startup failed due to previous errors
17 Jan 2017 15:27:42,652- Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'formRecognitionIndexTaskManager' defined in URL [jar:file:/C:/SymantecDLP/Protect/tomcat/webapps/ProtectManager/WEB-INF/lib/manager.jar!/com/vontu/manager/admin/formrecognitionprofiles/task/FormRecognitionIndexTaskManager.class]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.vontu.manager.admin.formrecognitionprofiles.task.FormRecognitionIndexTaskManager]: Constructor threw exception; nested exception is java.lang.UnsatisfiedLinkError: C:\SymantecDLP\Protect\lib\native\PDFiumInterface.dll: Can't find dependent libraries
17 Jan 2017 15:27:46,648- Thread: 19 WARNING [com.sun.xml.ws.wsdl.PayloadQNameBasedOperationFinder] Non unique body parts! In a port, as per BP 1.1 R2710 operations must have unique operation signature on the wire for successful dispatch. Methods [listCustomAttributes, listIncidentStatus] have the same request body block . Method dispatching may fail, runtime will try to dispatch using SOAPAction. Another option is to enable AddressingFeature to enabled runtime to uniquely identify WSDL operation using wsa:Action header.
17 Jan 2017 15:27:46,947- One or more listeners failed to start. Full details will be found in the appropriate container log file
17 Jan 2017 15:27:46,980- The web application [/ProtectManager] appears to have started a thread named [FileObservable] but has failed to stop it. This is very likely to create a memory leak.
17 Jan 2017 15:27:46,981- The web application [/ProtectManager] appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely to create a memory leak.
Followed below articles but without much help
https://support.symantec.com/en_US/article.TECH236804.html
https://support.symantec.com/en_US/article.TECH228141.html
All the Vontu services are up and running
Thanks,
-Syed Hussain