Oxygen XML Forum

I just upgraded to <oXygen/> 13.2 from 13.1. However, executing oxygen13.2.exe has no effect. No windows appear, no splash screen appears, and nothing that looks oXygen related appears in my list of running tasks. I get the same effect if I double click on the oXygen icon or run the executable from the command prompt.

However using oxygen.bat appears to work fine.

Any ideas? I've never seen this before with previous upgrades.

Hello,

We have had one other report of a similar incident with v13.2.
In v13.2 a new version of install4j was used, so it's possible that the launchers generated with this new version may have a glitch. We will investigate.

What edition of Windows are you using(XP, Vista, 7)? Is it 32 or 64 bit?

Can you please check in the Event Viewer under Applications, are there any Error events related to the Oxygen launchers?

Regards,
Adrian

I'm using Windows 7, 64 bit. I checked the Event Viewer but I don't see anything there that looks related. I admit that I'm not sure what I'm looking at. Under "Applications and Service Logs" there are a number of subheadings, including one labeled "Microsoft" that contains a large number of further subheadings.

Another tidbit... I have a Java 7 JRE installed as my primary Java. I understand oXygen comes with its own Java but I thought I'd throw that information out there just in case it matters.

Sorry, I meant Application. In the Windows 7 Event Viewer that's under Windows Logs.

A better way to obtain a launcher log is to run the launcher with the argument: /create-i4j-log
Open a command prompt windows and cd to the Oxygen folder. Run there:
oxygen13.2.exe /create-i4j-log
You should get a dialog telling you where the log file will be created and asking you if you want to open an Explorer window there.
If it doesn't do that, look for the last file named i4j_nlog_X(X is a number) in the TEMP folder: C:\Users\<username>\AppData\Local\Temp
Please send us this log file to support@oxygenxml.com

Alternatively, since you are on Windows 7 64 bit, you could get Oxygen running by installing the 64-bit kit of Oxygen found here:
http://www.oxygenxml.com/download_oxyge ... 64bit.html
Note that this installs in a different location so it will not interfere with the 32 bit installation. It installs in C:\Program Files instead of C:\Program Files (x86)

I would like to ask you to please also keep the 32 bit installation of Oxygen, if you are willing to help us in investigating this issue.

Regards,
Adrian

Okay, I created the log file you described and I'll send it to the support address. Actually this time, when I asked to create the log, oXygen did start but it took a very long time (I'd estimate maybe a minute). In fact I was looking at the log file in a text editor when suddenly the main oXygen window appeared. Note that in the past oXygen never started... at least not after even 30 minutes or more.

I didn't realize there was a 64 bit version. That's great... I'll try that too.

Hi,

Please note that a new build of Oxygen 13.2(build 2012011617) is now available on our web site. This build fixes a number of problems that were caused by the .exe launchers.

Windows: Fixed some problems with the application launchers that caused various issues: application not starting, options being reset at each restart.

You can download this new build from our web site:
http://www.oxygenxml.com/download.html

The complete list of bug-fixes for this build can be found here:
http://www.oxygenxml.com/build_history.html#2012011617

Let us know if the problem persists with this new build.

Regards,
Adrian

I'll check out the new build. Strangely after preparing the log file you mentioned before, oXygen now seems to start normally. I tried it several times and it starts right up (this is the original version I was having trouble with before). As far as I can tell I didn't change anything. It seems hard to believe that running the /create-i4j-log option would have changed the behavior, but what do I know?

You can delete three out of four of my previous replies. I was receiving "Bad response from server" messages when I tried to post it. Apparently they were getting posted anyway.