Oxygen XML Forum

Posted: **Fri Apr 21, 2017 7:20 pm**

Hello together,

Right now i am unable to run Oxygen XML ver 17.1 in my computer, my operating system is Windows 10 and i am using jdk1.8.0_65 as java version in JAVA_HOME environment variable in my computer(don't know if this info necessary)

Lastly i've checked that my windows user has write access to %TEMP% folder so i don't think that this part is not working.

Here is the stacktrace, can someone kindly support me ?

Code: Select all

Cannot start <oXygen/> XML Editor.

Due to:java.lang.reflect.InvocationTargetException

java.lang.reflect.InvocationTargetException

	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

	at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

	at java.lang.reflect.Constructor.newInstance(Unknown Source)

	at ro.sync.ui.application.ApplicationLauncher.d(Unknown Source)

	at ro.sync.ui.application.ApplicationLauncher.launch(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 ro.sync.exml.Oxygen.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.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.NullPointerException

	at ro.sync.exml.editor.cb.b.m.f(Unknown Source)

	at ro.sync.exml.editor.cb.b.m.b(Unknown Source)

	at ro.sync.exml.editor.cb.b.e.e(Unknown Source)

	at ro.sync.exml.xc.<init>(Unknown Source)

	at ro.sync.exml.editor.cb.b.e.<init>(Unknown Source)

	at ro.sync.exml.editor.cb.b.e.<init>(Unknown Source)

	at ro.sync.exml.editor.cb.b.c$1.<init>(Unknown Source)

	at ro.sync.exml.editor.cb.b.c.<init>(Unknown Source)

	at ro.sync.exml.editor.cb.g$1.<init>(Unknown Source)

	at ro.sync.exml.editor.cb.g.<init>(Unknown Source)

	at ro.sync.exml.editor.cb.b.<init>(Unknown Source)

	at ro.sync.exml.editor.nd$5.<init>(Unknown Source)

	at ro.sync.exml.editor.nd.<init>(Unknown Source)

	at ro.sync.exml.editor.pb.<init>(Unknown Source)

	at ro.sync.exml.MainFrame.<init>(Unknown Source)

	at ro.sync.exml.MainFrame.<init>(Unknown Source)

	... 18 more

Posted: **Mon Apr 24, 2017 12:43 pm**

Hello,

This problem has been resolved in the latest maintenance build of oXygen 17.1, 2015102718:

Linux/Windows XP (unsupported OS)/Startup: Fixed a NullPointerException error that prevented the application from starting due to an unavailable system font.

The list of all bug-fixes for v17.1 maintenance builds can be found here:
https://www.oxygenxml.com/build_history ... 2016032212

You can download the latest maintenance build of oXygen XML Editor v17.1 from our software archive:
https://www.oxygenxml.com/xml_editor/so ... .html#17.1

To upgrade for Windows you can install the new build in the same folder as the previous installation, it will automatically upgrade it.
Before you upgrade, if you have added files or made changes to any of the files from the oXygen installation folder(especially the frameworks folder), you may want to create a backup of them because they will be overwritten during the upgrade procedure. Custom frameworks will be preserved but we recommend backing them up anyway, just to be safe.

The oXygen preferences will be preserved since they are located elsewhere (user home folder).

Regards,
Ionela

Posted: **Sat Sep 09, 2017 3:28 pm**

We are having the same issue. Writer is installing on a Windows VM machine. Running <oXygen/> XML Author 17.1, build 2016032212. I believe this is the latest version of oXygen Author 17.1. How can this be resolved if we are running latest 17.1 version? Thanks.

Posted: **Mon Sep 11, 2017 11:39 am**

Hi Rhonda,

Please note that this error message, "Cannot start <oXygen/> / Invocation target exception", is very generic and appears for most startup issues. The actual cause of the error is seen in the "Caused by" section of the stack trace. In your case (as seen in your private report) the startup issue is caused by a broken third party plugin, so it's actually unrelated to this problem. This was a NullPointerException that appeared because Oxygen was trying to use an unavailable font (does not apply in your case).

Regards,
Adrian

Oxygen XML Forum

FATAL ERROR - Cannot start <oXygen/> XML Editor.

FATAL ERROR - Cannot start <oXygen/> XML Editor.

Re: FATAL ERROR - Cannot start <oXygen/> XML Editor.

Re: FATAL ERROR - Cannot start <oXygen/> XML Editor.

Re: FATAL ERROR - Cannot start <oXygen/> XML Editor.