Flexera Community

Mar 07, 2008

We have discovered that the following message is thrown when a signed jar file is used as a dependency on a Custom Code Action:Installer User Interface Mode Not SupportedGoogling for this error reveals that the error is the result of a JVM incompatib...

Oct 23, 2007

I am attempting to migrate an install from Win32 to Linux(Fedora Core 6). The install is set up for a Windows target only w/a VM version of 1.6.0_00. On the Windows version of InstallAnywhere Enterprise 8.0, the script builds fine. However, on the Li...

Jun 30, 2008

Has anyone been able to reproduce this issue on Linux? I am at a stopping point as I really need to include JRE 1.6.0_06 in a build and am unable to do so. Any help is appreciated.

Jun 12, 2008

Tony,Yes, this error happens every time I attempt an update through the UI.What I mean by java version is the java executable being used to start InstallAnywhere is a JDK 1.6.0_06 version. This is also set in my $JAVA_HOME env variable.The version of...

Jun 11, 2008

Has this fix ever been applied? also, when I try to apply updates through the InstallAnywhere 2008 update process in the application, I get the following error:java.util.zip.ZipException: Wrong Central Directory SignatureSounds like a bug in Zip in J...

Oct 25, 2007

I solved the problem. Apparently in InstallAnywhere 2008, Custom Code Actions will not execute(at least I couldn't get them to) when compiled from JDK 1.6. My solution was to change the target value in my Maven pom file from 1.6 to 1.5, and this solv...

Flexera Community

User Statistics

User Activity

Signed Jar File causes erroneous GUI mode error

Custom Code Action in Linux Client

Re: Installanywhere and Java 1.6.0_04

Re: Installanywhere and Java 1.6.0_04

Re: Installanywhere and Java 1.6.0_04

Re: Custom Code Action in Linux Client