File Type Analyzer Utility Fails to Launch in Symantec DLP 16.0 RU2
search cancel

File Type Analyzer Utility Fails to Launch in Symantec DLP 16.0 RU2

book

Article ID: 376487

calendar_today

Updated On:

Products

Data Loss Prevention

Issue/Introduction

When attempting to launch the File Type Analyzer utility (analyzer_gui.exe), the following error message is displayed:

java.lang.NoClassDefFoundError: org/apache/log4j/PropertyConfigurator
at com.vontu.tools.filegenie.FileGenie.main(FileGenie.java:25)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)
at com.exe4j.runtime.WinLauncher.main(Unknown Source)
at com.install4j.runtime.launcher.WinLauncher.main(Unknown Source)
Caused by: java.lang.ClassNotFoundException: org.apache.log4j.PropertyConfigurator
at java.net.URLClassLoader$1.run(URLClassLoader.java:372)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:360)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 8 more

Environment

DLP Release: 16.0 RU2

Cause

This issue is a known defect in DLP 16.0 RU2 and will be addressed in a future release.

Resolution

A simple workaround is available:

1. Navigate to the following directory: DRIVE:\Program Files\File Analyzer\lib
2. Rename the file log4j-1.2.17.jar to log4j-1.2.14.jar.
3. Relaunch the File Type Analyzer utility (analyzer_gui.exe).

Additional Information