Adhoc Analysis Not Launching



We are unable to use Ad-Hoc Analysis at all, keep getting the following error:

Java Web Start Using JRE version 1.8.0_60-b27 Java HotSpot(TM) 64-Bit Server VM User home directory = C:\Users\s525702 ---------------------------------------------------- c:   clear console window f:   finalize objects on finalization queue g:   garbage collect h:   display this help message m:   print memory usage o:   trigger logging p:   reload proxy configuration q:   hide console r:   reload policy configuration s:   dump system and deployment properties t:   dump thread list v:   dump thread stack 0-5: set trace level to <n> ---------------------------------------------------- access denied ("java.lang.RuntimePermission" "")     at Source)     at Source)     at java.lang.SecurityManager.checkPermission(Unknown Source)     at java.lang.SecurityManager.checkPackageAccess(Unknown Source)     at java.lang.ClassLoader$ Source)     at java.lang.ClassLoader$ Source)     at Method)     at java.lang.ClassLoader.checkPackageAccess(Unknown Source)     at java.lang.ClassLoader.defineClass1(Native Method)     at java.lang.ClassLoader.defineClass(Unknown Source)     at Source)     at Source)     at$100(Unknown Source)     at$ Source)     at$ Source)     at Method)     at Source)     at java.lang.ClassLoader.loadClass(Unknown Source)     at Source)     at java.lang.ClassLoader.loadClass(Unknown Source) discoverPath = Local Settings/Application Data/Adobe/Discover/ logFilePath = log/discover%d.log FileAppender.relPathTemplate: 'Local Settings/Application Data/Adobe/Discover/log/discover%d.log' [134 TRACE pool-2-thread-1 DiscoverDownloadService] loading extra jars [230 TRACE pool-2-thread-1 DiscoverDownloadService] extra jars cached: false [5113 INFO javawsApplicationMain Discover] Client build: 3.5.2226 2016/04/21 21:09 [5114 INFO javawsApplicationMain Discover] Java Version: 1.8.0_60-b27 [5114 INFO javawsApplicationMain Discover] Java VM Name: Java HotSpot(TM) 64-Bit Server VM [5114 INFO javawsApplicationMain Discover] Operating System: Windows 7 [5121 INFO Thread-9 Discover] Client build: 3.5.2226 2016/04/21 21:09 [5122 INFO Thread-9 Discover] Java Version: 1.8.0_60-b27 [5122 INFO Thread-9 Discover] Java VM Name: Java HotSpot(TM) 64-Bit Server VM [5122 INFO Thread-9 Discover] Operating System: Windows 7 [5124 ERROR Thread-9 Discover] Uncaught exception occurred on thread Thread[Thread-9,5,javawsApplicationThreadGroup]: java.lang.NullPointerException     at com.omniture.workbench.DiscoverClient$DiscoverInstanceListener.newActivation(Unknown Source)     at com.sun.jnlp.SingleInstanceServiceImpl$TransferListener.newActivation(Unknown Source)     at$SingleInstanceServer$ Source)     at Method)     at$ Source) [6251 INFO AWT-EventQueue-2 BusySet] [AsynchManagerLoader] Object added, count: 1 [6251 INFO AWT-EventQueue-2 BusySet] [AsynchManagerLoader] Object added, count: 1 [6251 INFO AWT-EventQueue-2 BusySet] [AsynchManagerLoader] Object added, count: 2 JNLPClassLoader: Finding library gluegen-rt.dll [6369 ERROR javawsApplicationMain ClientStartupHelper]  java.lang.reflect.InvocationTargetException     at java.awt.EventQueue.invokeAndWait(Unknown Source)     at java.awt.EventQueue.invokeAndWait(Unknown Source)     at com.omniture.workbench.ClientStartupHelper.loginOberon(Unknown Source)     at com.omniture.workbench.ClientStartupHelper.start(Unknown Source)     at com.omniture.workbench.DiscoverClient.main(Unknown Source)     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)     at java.lang.reflect.Method.invoke(Unknown Source)     at com.sun.javaws.Launcher.executeApplication(Unknown Source)     at com.sun.javaws.Launcher.executeMainClass(Unknown Source)     at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)     at Source)     at Source) Caused by: java.lang.UnsatisfiedLinkError: jogamp.common.jvm.JVMUtil.initialize(Ljava/nio/ByteBuffer;)Z     at jogamp.common.jvm.JVMUtil.initialize(Native Method)     at jogamp.common.jvm.JVMUtil.<clinit>(Unknown Source)     at com.jogamp.common.os.Platform$ Source)     at com.jogamp.common.os.Platform$ Source)     at Method)     at com.jogamp.common.os.Platform.<clinit>(Unknown Source)     at<clinit>(Unknown Source)     at com.omniture.om3d.OmGlCanvas.<clinit>(Unknown Source)     at com.omniture.workbench.LoginProgressDialog.initComponents(Unknown Source)     at com.omniture.workbench.LoginProgressDialog.<init>(Unknown Source)     at com.omniture.workbench.ClientStartupHelper$ Source)     at java.awt.event.InvocationEvent.dispatch(Unknown Source)     at java.awt.EventQueue.dispatchEventImpl(Unknown Source)     at java.awt.EventQueue.access$500(Unknown Source)     at java.awt.EventQueue$ Source)     at java.awt.EventQueue$ Source)     at Method)     at$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)     at java.awt.EventQueue.dispatchEvent(Unknown Source)     at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)     at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)     at Source) [6588 TRACE AWT-EventQueue-2 DiscoverDialog] Dialog display time: 156 Discover Startup Error

Is anyone able to help at all?

Accepted Solutions (1)

Accepted Solutions (1)



After the launch of new UI,it seems like Ad-Hoc needs to be downloaded again. I had the same issue - deleting the current adhoc tool, re-downloading it, fixed the problem. 

Answers (3)

Answers (3)


Community Manager


Hi Andrew, 

Have you been able to sort this issue out? If you have found a solution, it would be great if you can provide it here for the benefit of the community. If not, I would request you to reach out to ClientCare as it will require a deeper look into your system. Thanks!




This has been happening for months, always use the latest ad-hoc analysis tool from Adobe and delete the Java case so definitely a different issue.