InstallAnywhere Knowledge Base

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  This page provides links to download InstallAnywhere files and utilities including custom code, merge modules, JRE VM packs, and VM templates.
View full article
InstallAnywhere StandAlone Build with Docker Build your own Docker Image with InstallAnywhere SAB  On an machine where Docker is installed, create Folder (eg: IADockerBuild). Copy InstallAnywhere installer (eg: InstallAnywhere2020.bin for Ubuntu docker) to the above created folder (i.e IADockerBuild) and ensure the file has execute permissions. Create a file called DockerFile (no extension) inside the above created folder (i.e IADockerBuild) with the following content [Dockerfile] # Base Ubuntu Image FROM ubuntu:latest # Change to Root Dir WORKDIR / # Copy InstallAnywhere installer to root ADD InstallAnywhere2020.bin / # InstallAnywhere installation RUN ./InstallAnywhere2020.bin -i silent Launch Terminal and navigate to the above created folder (i.e IADockerBuild) Run the following command as 'sudo' or root user to build the Docker image with InstallAnywhere installed: docker build -t installanywhere2020 --no-cache=true . Wait for the build to complete. Once the build is complete run the following command to list the newly created image docker images   License InstallAnywhere SAB  Activate a Node Locked License For activating SAB using a node locked license, you need to manually copy the license file (license.lic) to InstallAnywhere [INSTALLDIR] location. It is also mandatory to create the container with --mac-address option, else the MAC/Physical address will be dynamic each time you create a new container. Open the license file that you want to use for activating InstallAnywhere SAB and copy the MAC address.           Use the same/copied MAC/Physical address to create the container using --mac-address docker run --mac-address <MAC-ADDRESS> -it <IMAGE> (Optional) In case if you want to create container, mount folder and assign MAC address at the same time run the following command: docker run --mac-address <MAC-ADDRESS> -v "<HOST-DIR>:<CONTAINER-DIR>" -it <IMAGE> Where: MAC-ADDRESS : is separated by colon( : ), eg: 00:16:7F:51:03:7D HOST-DIR : folder present in Physical machine/VM CONTAINER-DIR : folder inside the container;  if the folder does not exist it will automatically create it. The license file need to be copied to the installation folder. The container should be in Exited state in order to copy files to a container. Run the following command to Stop the container: docker stop <CONTAINER-ID/CONTAINER-NAME>         4. After the container is stopped, run the following command to copy the license file (i.e license.lic) to docker container. "docker cp license.lic <CONTAINER-ID/CONTAINER-NAME>:root         5. After the license file copy is done, run the following command to Restart the container: docker start <CONTAINER-ID/CONTAINER-NAME>          6. Navigate to the install directory cd /root/InstallAnywhere\ 2020          7. Register the Nodelocked license to the SAB build using the following command ./build -registerNodeLocked [path_of_license_file] Activate a Concurrent License Run the command as sudo or root user docker run -it <IMAGE>        2. Navigate to the InstallAnywhere location cd /root/InstallAnywhere\ 2020        3. Register the SAB build with concurrent License Server    ./build ls <License Server Port>@<License Server IP Address>   Note:  Please refer the following for addition details on the commands used: docker build: https://docs.docker.com/engine/reference/commandline/build/ docker images: https://docs.docker.com/engine/reference/commandline/images/ docker start : https://docs.docker.com/engine/reference/commandline/start/ docker stop : https://docs.docker.com/engine/reference/commandline/stop/ docker cp: https://docs.docker.com/engine/reference/commandline/cp/ docker run: https://docs.docker.com/engine/reference/run/
View full article
This article provides a Hotfix for InstallAnywhere 2018 SP1.
View full article
Description Command line builds fail intermittently with a JRE Fatal Error.  Often the failure is accompanied by a JRE crash and dump.  Fatal Errors encountered may be similar to the following: build failed A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x71f46fbc, pid=27912, tid=0x00007c98 # # JRE version: Java(TM) SE Runtime Environment (8.0_162-b12) (build 1.8.0_162-b12) # Java VM: Java HotSpot(TM) Client VM (25.162-b12 mixed mode windows-x86 ) # Problematic frame: # V [jvm.dll+0x76fbc] # # Core dump written. Default location: C:\Program Files (x86)\InstallAnywhere 2018\hs_err_pid27912.mdmp # # An error report file with more information is saved as: # C:\Program Files (x86)\InstallAnywhere 2018\hs_err_pid27912.log # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # //... - file(s) not opened on this client. # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x7778342f, pid=9192, tid=0x00002140 # # JRE version: Java(TM) SE Runtime Environment (8.0_162-b12) (build 1.8.0_162-b12) # Java VM: Java HotSpot(TM) Client VM (25.162-b12 mixed mode windows-x86 ) # Problematic frame: # C [ntdll.dll+0x4342f] # # Core dump written. Default location: C:\Program Files (x86)\InstallAnywhere 2018\hs_err_pid9192.mdmp # # An error report file with more information is saved as: # C:\Program Files (x86)\InstallAnywhere 2018\hs_err_pid9192.log # # Compiler replay data is saved as: # C:\Program Files (x86)\InstallAnywhere 2018\replay_pid9192.log # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # [Fatal Error] %7BA4FF8391-1F32-11B2-BC6B-C34F3EE71742%7D.pf.xml:1:1: Premature end of file. Workaround In order to resolve the issue, please do the following: Open the .lax file that corresponds to the launcher you are using (e.g. build.lax) in a text editor. Find the property, lax.command.line.args, and prepend the following to whatever value it currently has, followed by a space: -nupd Open %USERPROFILE%\.InstallAnywhere\190\Premier\preferences\com.zerog.ia.Designer.properties in a text editor and make sure the following property is set to false like: designer.update.ceipoptin=false Resolution This issue has been resolved in InstallAnywhere 2020.
View full article
To help our customers expedite their license activation, we've set up a Flexera Support Chat feature in the case management portal. To initiate a chat and get assistance with your license activation: Sign into the community Navigate to Get Support -> Open New Case  (Don't see this option? Read   Linking your Community Account to your Organization ) Select the InstallAnywhere product from the Product drop-down Click the Chat with an Expert option when it appears  NOTE:  This feature is only for license activation assistance. If you require product assistance, please open a support case.
View full article
Symptoms: InstallAnywhere digital signing feature uses a timestamp URL from Symantec which is being decommissioned (more details here) and migrated to Digicert. Signing with new Digicert URL causes a breakage in Digital Signing Diagnosis: When signing an installer with SHA-256 digest, using the new Digicert server (http://timestamp.digicert.com), the resulting installer is signed by SHA-256 digest, but the counter signatures are signed with SHA1 due to an incorrect order in which InstallAnywhere calls the signing APIs Affected InstallAnywhere Versions InstallAnywhere 2015 InstallAnywhere 2017 InstallAnywhere 2018 InstallAnywhere 2020 All minor releases of the above releases included Resolution The issue is resolved in a hotfix that can be downloaded from here. Please note that the hotfix is applicable on the latest service packs of above affected versions. Download and extract the contents of the file. Copy x86/IAWinDigiSign.exe to <IA_Install_Location>/resource/nativetools/windows Copy x64/IAWinDigiSign.exe to <IA_Install_Location>/resource/nativetools/windows64 After replacing the above files, in your InstallAnywhere project, navigate to Project à Platforms à Windows à Digital Signing and update the Timestamp server field to http://timestamp.digicert.com Additional Information If there are any additional issues, please contact our  Technical Support team  
View full article
Summary When attempting to uninstall or install the InstallAnywhere product, a message displays that says, "This is an incomplete installation of InstallAnywhere [EditionNumber] Evaluation." Synopsis When attempting to uninstall or install the InstallAnywhere product, a message displays that says, "This is an incomplete installation of InstallAnywhere [InstallAnywhereVersion] Evaluation." Ex: "This is an incomplete installation of InstallAnywhere 2014 SP1 Evaluation" Ex: "This is an incomplete installation of InstallAnywhere 2017 Evaluation." Note: This same error message may also appear when building a project from the command-line.   Discussion To resolve the issue please view the following steps:   On a Windows machine, follow these steps: 1. In Windows Explorer, navigate to the following path: %USERPROFILE%\InstallAnywhere Note: The InstallAnywhere directory is a hidden directory. Make sure to enable hidden folders.   2. Locate and delete the appropriate version number folder that corresponds with your installed copy of InstallAnywhere:   For InstallAnywhere 2020 Delete the 200 directory For InstallAnywhere 2018 Delete the 190 directory For InstallAnywhere 2017 Delete the 180 directory For InstallAnywhere 2015 Delete the 170 directory For InstallAnywhere 2014 SP1 Delete the 165 directory For InstallAnywhere 2014 Delete the 160 directory For InstallAnywhere 2013 Delete the 150 directory For InstallAnywhere 2012 Delete the 140 directory For InstallAnywhere 2011 SP3 Delete the 125 directory For InstallAnywhere 2011, 2011 SP1, 2011 SP2 Delete the 120 directory For InstallAnywhere 2010 Service Pack 1 (SP1) Delete the 115 directory For InstallAnywhere 2010 Delete the 110 directory For InstallAnywhere 2009, 2009 SP1, and 2009 SP2 Delete the 100 directory For InstallAnywhere 2008 Value Pack 1 (VP1) Delete the 95 directory For InstallAnywhere 2008 Delete the 90 directory For InstallAnywhere 8.0 Delete the 80 directory Note: The folder will be re-created when the product is launched again. 3. Re-launch the InstallAnywhere product and re-register the product.   ------------------------------------------------------------------------------------------------------------------------------------------------------ On macOS/OS X, Linux-based, or Unix-based machines follow these steps:     1. From the command-line, change directories to the hidden .InstallAnywhere directory in the user's home directory (for the user that registered InstallAnywhere).   Note: The InstallAnywhere directory is a hidden directory. Make sure to enable hidden folders.   2. Locate and delete the appropriate version number folder that corresponds with your installed copy of InstallAnywhere:   For InstallAnywhere 2020 Delete the 200 directory For InstallAnywhere 2018 Delete the 190 directory For InstallAnywhere 2017 Delete the 180 directory For InstallAnywhere 2015 Delete the 170 directory For InstallAnywhere 2014 SP1 Delete the 165 directory For InstallAnywhere 2014 Delete the 160 directory For InstallAnywhere 2013 Delete the 150 directory For InstallAnywhere 2012 Delete the 140 directory For InstallAnywhere 2011 SP3 Delete the 125 directory For InstallAnywhere 2011, 2011 SP1, 2011 SP2 Delete the 120 directory For InstallAnywhere 2010 Service Pack 1 (SP1) Delete the 115 directory For InstallAnywhere 2010 Delete the 110 directory For InstallAnywhere 2009, 2009 SP1, and 2009 SP2 Delete the 100 directory For InstallAnywhere 2008 Value Pack 1 (VP1) Delete the 95 directory For InstallAnywhere 2008 Delete the 90 directory For InstallAnywhere 8.0 Delete the 80 directory   Note: The folder will be re-created when the product is launched again.   3. Re-launch the InstallAnywhere product and re-register the product.   Additional Information For information on registering the InstallAnywhere product, please view the related knowledge base articles: Licensing Overview for InstallAnywhere 2011 and Later How to Register InstallAnywhere (Versions 8.0 - 2010) If further assistance is needed, please contact Flexera Software Technical Support .
View full article
Summary How To generate the InstallAnywhere Log for Install, Uninstall, and Build in InstallAnywhere 2011 and later. Synopsis This article discusses how to generate an install/uninstall/build log to capture what is occurring during an installation/uninstallation/build, primarily for troubleshooting purposes.   Discussion Generating an InstallAnywhere Standard Installation Log: Follow these steps in the InstallAnywhere IDE with your project open: Navigate to the Project > General Settings > Log Settings Section. For InstallAnywhere versions earlier than 2013, navigate to Project > Log Settings. Under Log Settings section, set Enable Logging to Yes. For InstallAnywhere versions earlier than 2013, check the Enable Logging checkbox Check the Install checkbox. Under Log Format, select the Plain text format option. Build the project. Run the installer. Note 1: Plain text format is selected by default, not XML format. Note 2: These steps will create an installation log in plain text or XML format. The installation log file is created in the installation directory, under a Logs subdirectory, with the default filename $PRODUCT_NAME$_InstallLog.log or $PRODUCT_NAME$_InstallLog.xml.   Generating an InstallAnywhere Standard Installation Log That Includes the Verbose Installation Debug Output: Follow these steps in the InstallAnywhere IDE with your project open: Navigate to the Project > JVM Settings > Installer Settings View > Optional Installer Arguments Section. Specify the following value in the Additional Arguments field: -Dlax.debug.level=4 -Dlax.debug.all=true Navigate to the Project > General Settings > Log Settings Section. For InstallAnywhere versions earlier than 2013, navigate to Project > Log Settings. Under Log Settings section, set Enable Logging to Yes. For InstallAnywhere versions earlier than 2013, check the Enable Logging checkbox. Check the Install checkbox. Under Log Format, select the Plain text format option. Set Include debug output (stderr and stdout) to Yes. For InstallAnywhere versions earlier than 2013, check the Include Debug Output (stderr and stdout) checkbox. Build the project. Run the installer. Note 1: Verbose debug output refers to more detailed debug output that can be generated by an installer. Note 2: Plain text format is selected by default, not XML format. Note 3: These steps will create an installation log in plain text or XML format. The installation log file is created in the installation directory, under a Logs subdirectory, with the default filename $PRODUCT_NAME$_InstallLog.log or $PRODUCT_NAME$_InstallLog.xml.   Generating an InstallAnywhere Standard Uninstallation Log: Follow these steps in the InstallAnywhere IDE with your project open: Navigate to the Project > General Settings > Log Settings Section. For InstallAnywhere versions earlier than 2013, navigate to Project > Log Settings. Under Log Settings section, set Enable Logging to Yes. For InstallAnywhere versions earlier than 2013, check the Enable Logging checkbox Check the Uninstall checkbox. Under Log Format, select the Plain text format option. Build the project. Run the installer. Run the uninstaller. Note 1: Plain text format is selected by default, not XML format. Note 2: These steps will create an uninstallation log in plain text or XML format. The uninstallation log file is created in the installation directory, under a Logs subdirectory, with the default filename $PRODUCT_NAME$_UninstallLog.log or $PRODUCT_NAME$_UninstallLog.xml.   Generating an InstallAnywhere Standard Uninstallation Log That Includes the Verbose Uninstallation Debug Output: Follow these steps in the InstallAnywhere IDE with your project open: Navigate to the Project > JVM Settings > Installer Settings View > Optional Installer Arguments Section. Specify the following value in the Additional Arguments field: -Dlax.debug.level=4 -Dlax.debug.all=true Navigate to the Project > General Settings > Log Settings Section. For InstallAnywhere versions earlier than 2013, navigate to Project > Log Settings. Under Log Settings section, set Enable Logging to Yes. For InstallAnywhere versions earlier than 2013, check the Enable Logging checkbox Check the Uninstall checkbox. Under Log Format, select the Plain text format option. Set Include debug output (stderr and stdout) to Yes. For InstallAnywhere versions earlier than 2013, check the Include Debug Output (stderr and stdout) checkbox. Build the project. Run the installer. Run the uninstaller. Note 1: Verbose debug output refers to more detailed debug output that can be generated by an uninstaller. Note 2: Plain text format is selected by default, not XML format. Note 3: These steps will create an uninstallation log in plain text or XML format. The uninstallation log file is created in the installation directory, under a Logs subdirectory, with the default filename $PRODUCT_NAME$_UninstallLog.log or $PRODUCT_NAME$_UninstallLog.xml.   Generating a Build Log: Command Line Build Log The build output when running a command line build can be redirected by setting the following two properties in the build.lax file. The build.lax file is found in the InstallAnywhere HOME where InstallAnywhere is installed. lax.stderr.redirect=\\tmp\\buildconsole.txt lax.stdout.redirect=\\tmp\\buildconsole.txt Setting the properties as shown above will generate a file named buildconsole.txt in the specified directory (C:\\tmp) in Windows. If only a filename is specified as shown below, then the file will be created in the same directory containing the build.lax file. lax.stderr.redirect=buildconsole.txt lax.stdout.redirect=buildconsole.txt GUI Build Log The build output when running a GUI build, through the InstallAnywhere Advance Designer, can similarly be redirected to a file by setting the lax.stdout.redirect and lax.stderr.redirect properties (mentioned above) in the InstallAnywhere.lax file. This file is found in the InstallAnywhere installation directory, where InstallAnywhere is installed. Note: You will need to restart the InstallAnywhere IDE after making the changes in the InstallAnywhere.lax file.
View full article
Summary Generating InstallAnywhere Build Log specifically for Windows and Linux. Synopsis This article outlines the steps necessary to generate a verbose build-time debug log, specifically for Windows and Linux.   Discussion An InstallAnywhere verbose build-time debug log can be generated through a number of ways: From the Advanced Designer: When running a GUI build through the InstallAnywhere Advanced Designer, the build output can be redirected to a text file by setting the following two properties in the InstallAnywhere.lax file. lax.stderr.redirect=buildconsole.txt lax.stdout.redirect=buildconsole.txt The InstallAnywhere.lax file is found in the location where InstallAnywhere is installed. Setting the above two properties to a text file will generate the text file in the same directory as the InstallAnywhere.lax file is located. A path can also be specified, so that the log will be created in that specific location. Write permissions to the directory where a file is being created are necessary. Note: You will need to restart the InstallAnywhere IDE after making the change in the InstallAnywhere.lax file. To generate a verbose GUI build-time debug log (in InstallAnywhere versions prior to 2011), add the following line to the top of the InstallAnywhere.lax file: lax.nl.java.option.additional=-Dlax.debug.all=true -Dlax.debug.level=4 In InstallAnywhere 2011 and later, this property is already included in the InstallAnywhere.lax file. Therefore, if the property already exists in the InstallAnywhere.lax file, append "-Dlax.debug.level=4 -Dlax.debug.all=true" (without quotes) at the end of the existing property (like shown below) lax.nl.java.option.additional=ExistingValue -Dlax.debug.level=4 -Dlax.debug.all=true where, ExistingValue is the value that is already present and assigned to the property. Note: Ensure that there is only one entry for the lax.nl.java.option.additional property, otherwise the build-time log with not be verbose. The Build Log tab in the Build section of the InstallAnywhere Advanced Designer displays a build log in XML format once a build is complete (only applicable to the Premier Edition). From the Command-Line: If you are building from the command line using the application launcher named "build.exe" then, use the following approach: build.exe "C:\MyProduct.iap_xml" You can use the build output displayed in the console window as a build-time log. To save the log information in a file, copy the output of the build from the console window to a text file. When running a command line build, the build output can also be redirected to a text file by setting the following two properties in the build.lax file located in IA HOME where InstallAnywhere is installed. lax.stderr.redirect=buildconsole.txt lax.stdout.redirect=buildconsole.txt Setting, the properties as shown above will generate a file named buildconsole.txt in IA HOME, in the same directory containing the build.lax file. You can also specify a path to a text file if you want to create the text file in another location. To generate a verbose command line build log (in InstallAnywhere versions prior to 2011), add the following line to the top of the build.lax file: lax.nl.java.option.additional=-Dlax.debug.all=true -Dlax.debug.level=4 Note: For InstallAnywhere 2011 and later, append "-Dlax.debug.level=4 -Dlax.debug.all=true" (without quotes) at the end of the existing property in the build.lax file as explained in the From the Advanced Designer section above. Note: Ensure that there is only one entry for the lax.nl.java.option.additional property, otherwise the build-time log with not be verbose.   Additional Information For instructions on generating an installation/uninstallation log with InstallAnywhere 2010 and previous InstallAnywhere versions: Generating InstallAnywhere Log for Install and Uninstall with InstallAnywhere For instructions on generating an installation/uninstallation log with InstallAnywhere 2011 and later InstallAnywhere versions: Generating a Log for Install, Uninstall, and Build in InstallAnywhere.
View full article
Providing the necessary information to allow a Support Engineer to begin troubleshooting your issue is one of the best ways to avoid delays.  This article discusses what type of information to include and how to gather it when submitting an InstallAnywhere case to Flexera Technical Support.
View full article
Summary この記事では、アカウント管理者が フレクセラ・ソフトウェア製品 & ライセンス センター のアカウントにメンバーを追加またはアクティブ化する手順を説明します。 Symptoms この記事では、アカウント管理者が フレクセラ・ソフトウェア製品 & ライセンス センター のアカウントにメンバーを追加またはアクティブ化する手順を説明します。 Resolution 〇メンバーの追加:   フレクセラ・ソフトウェア製品 & ライセンス センター  にログインします。(https://flexerasoftware.flexnetoperations.com) 日本語表示は、画面左上部の「日本語(Japanese)」をクリックします。 「管理」下の「アカウント メンバー」をクリックします。 「新しいメンバーの追加」ボタンをクリックします。 フォームに必要事項を記載します。 「保存」ボタンをクリックします。 〇既存のエンドユーザーのメンバー ID の有効化:   フレクセラ・ソフトウェア製品 & ライセンス センター  にログインします。(https://flexerasoftware.flexnetoperations.com) 日本語表示は、画面左上部の「日本語(Japanese)」をクリックします。 「管理」下の「アカウント メンバー」をクリックします。 「非アクティブなメンバーをリスト表示」ボタンをクリックします。 リストから該当するユーザー名を選択します。 「電子メールを送信」にチェックします。 「メンバーの再アクティベート」ボタンをクリックします。
View full article
Summary Information on capturing debug output for macOS or OS X-based installers. Synopsis This article provides information on how to capture debug output for macOS or OS X?based installers. Discussion InstallAnywhere-generated installers use the standard output layers on macOS or OS X target systems to display output. To gather debugging output from a macOS or OS X?based installer, launch Console.app (found in /Applications/Utilities). To retain this information, cut and paste information from the console window to a file. If you do not see debug output from an installer, check the Info.plist file inside the installer. To do this, press Control while clicking the installer (or right-click the installer) and then click Show Package Contents. Inside the Contents folder, you will see an XML file named Info.plist. You?ll need to change the contents of the file. Initially, it contains the following: <key>lax.stderr.redirect</key> <string></string> <key>lax.stdout.redirect</key> <string></string> Change the file to this: <key>lax.stderr.redirect</key> <string>console</string> <key>lax.stdout.redirect</key> <string>console</string> When you relaunch the installer, the installer output should be now listed in Console.app.
View full article
Summary This article discusses how to generate a verbose InstallAnywhere build log specifically on macOS or OS X. Synopsis This article outlines the steps necessary to generate a verbose build-time debug log, specifically on macOS or OS X. Discussion Here are the steps for generating a verbose build log when building from the InstallAnywhere IDE: Close the InstallAnywhere IDE. In Finder, open the InstallAnywhere installation directory, where InstallAnywhere was installed. Right-click the InstallAnywhere executable. Select the Show Package Contents option. Open the Contents directory. Right-click the Info.plist file. Select to open the Info.plist file in Xcode (This can also be modified with TextEdit which, is showcased in the command-line builder steps below). For InstallAnywhere 2012 and InstallAnywhere 2013, expand the Java node. For InstallAnywhere 2014 and later, expand the JavaOra node. Select the lax.stderr.redirect entry. Replace the value with /tmp/verboseIAbuildlog.txt or a similar filename and absolute directory path to a location where you have write permissions. Select the lax.out.redirect entry. Replace the value with /tmp/verboseIAbuildlog.txt or a similar filename and absolute directory path to a location where you have write permissions. Expand the VMOptions node. Select the last Item entry under the VMOptions node. Click the + button to add an Item. For the new Item, make sure that the Item is of Type String. For the new Item, specify the value as: -Dlax.debug.all=true Select the new Item entry. Click the + button to add another new Item. For the new Item, make sure that the Item is of Type String. For the new Item, specify the value as: -Dlax.debug.level=4 Save the Info.plist file. Open the InstallAnywhere IDE. Build the project with the InstallAnywhere IDE. The specified file (for example, the /tmp/verboseIAbuildlog.txt file) should now be created with verbose build-time debug output. Here are the steps for generating a verbose build log by building with the InstallAnywhere command-line builder: In Finder, open the InstallAnywhere installation directory, where InstallAnywhere was installed. Open the the build.command.lax file, in the same directory as the main InstallAnywhere executable with TextEdit (This can also be modified with Xcode, which is showcased in the IDE steps above). Specify the following property values for the following properties, append the value if necessary: lax.stderr.redirect=/tmp/verboseIACMDBLD.txt lax.out.redirect=/tmp/verboseIACMDBLD.txt lax.nl.java.option.additional=-Dlax.debug.all=true -Dlax.debug.level=4 Save the changes. Build the project with the InstallAnywhere command-line builder. The specified file (for example, the /tmp/verboseIACMDBLD.txt file) should now be created with verbose build-time debug output. Additional Information There are different steps to generate a verbose build log on Windows and Linux. For those steps please see the following article: Generating InstallAnywhere Build Log on Windows and Linux
View full article
Summary The following example illustrates a guide to creating patch installers using InstallAnywhere, complete with sample projects (see Attachment: GeneratingPatchesWithInstallAnywhere.zip). This example may be especially helpful for developers interested in FlexNet Connect. Synopsis The following example illustrates a guide to creating patch installers using InstallAnywhere, complete with sample projects (see Attachment: GeneratingPatchesWithInstallAnywhere.zip). This example may be especially helpful for developers interested in FlexNet Connect. Discussion In this example, a program called Text Editor 1.0 was first generated and installed. Then a Simple Text Editor 1.1 patch was created. It updated core files, added some additional files, and removed any deprecated files. The patch should be installed in the same folder as 1.0, and it should only be executed if 1.0 is already installed. If someone installs 1.0, then 1.1, and then uninstalls 1.1, all the files should be uninstalled no matter if they were installed by the 1.0 installer or the patch installer. 1. Create version 1.0 installer. Make note of "Common" Component UUID. It will be needed in the Patch installer. Note: The Advanced Designer view is different in InstallAnywhere 2012 and earlier versions, click here for the documentation for those specific versions. 2. Make a copy of the version 1.0 project. Rename it. This is a step of convenience. You can create patch project from scratch, but you would need to re-add all files and reconfigure your project. Using a copy of the original project gives you a nice base to start from. 3. Open the new Project. Feel free to make changes to the Installer Title and Product Name to reflect that this is a patch installer. 4. Update Product Version in Project > General Settings > Product Information. 5. Update the "Common" Component Version. 6. Remove any unnecessary Panels and Actions from the Pre-Install Sequence. The patch will be installed in the existing product directory so we don?t need to ask the user to install the patch. This means the Choose Install Folder panel needs to be removed. No shortcuts will be installed by the patch Choose Shortcut Destination Panel is also not necessary. 7. Add a Find Component in Registry Action. To detect if a previous version of Simple Text Editor is already installed, the InstallAnywhere Registry needs to be searched. The Common Component ID (from Step 1) must be entered here. 8. Add a Show Message Dialog. This Action will tell the user that a previous version of Simple Text Editor has not been found, and it is required for this patch installer to run. 9. Add a Compare InstallAnywhere Variable Rule to the Show Message Dialog. This Rule must be added so that the dialog only appears if the Component ID is not found. 10. Add a Set InstallAnywhere Variable Action. This Action sets the install folder of the patch to the install location of the previously installed instance of Simple Text Editor. 11. Remove unnecessary Actions in the Install Sequence. Certain Actions like the Actions to create shortcuts and launchers do not need to be executed in a patch so you should remove those Actions to streamline the patch. Leave the Uninstaller untouched. Do not remove it. 12. Add updated file contents. Make sure File overwrite behavior is set to Always overwrite. This will prevent the installer from asking whether or not the installer should overwrite an existing file. Since this is a patch installer you always want this to happen. 13. Add any other Actions that may be required. If you need to remove files that are no longer necessary used, take advantage of the Delete File and Delete Folder Actions. Additional Information For more information about the location of the InstallAnywhere Registry file, click here. The InstallAnywhere IDE GUI was revamped in InstallAnywhere 2013. To see this patch installer documentation for InstallAnywhere 2012 and prior versions, click here.
View full article
Summary This article talks about the changes to Authentication and Code Signing Support for OS X Based Installers in InstallAnywhere 2014 Hotfix A Synopsis InstallAnywhere 2014 Hotfix A brings updated authentication support for Mac OS X installers for OS X systems. This article talks about the new updated Mac OS X installer authentication support and its requirements. Please note that this article does not list the complete steps required to create the authenticated installer. For complete detailed information on the new updated authentication and code signing support, refer to this PDF file or the file linked at the end of this article. The PDF includes all the necessary information regarding the new authentication and code signing support with detailed steps to create a Mac OS X authenticated installer. Discussion In InstallAnywhere 2014, authentication support for a Mac OS X installer can be enabled at the Project>Platforms>Mac OS X>Authentication setting in the project. Set the ?Requires an Administrator Name or Password to Install? setting to ?Yes? to enable authentication support for a Mac OS X installer. Support for authenticated installers is included for OS X 10.8 and later systems. However, installers which do not have authentication enabled are supported on OS X 10.7 and later. The authenticated installer must be code signed. An unsigned Mac OS X installer cannot be launched in authenticated mode. If the setting ?Requires an Administrator Name and Password to Install? is enabled in the project in the Project>Platforms>Mac OS X>Authentication section, the built installer won?t launch unless the installer is also code signed. The authenticated Mac OS X installer can be code signed in two ways: 1. By providing the code signing information in the project, enabling IA to create a code signed installer at build time. In order to code sign a Mac OS X installer at build time, the signing information should be provided in the project in the Project>Platforms>Mac OS X>Code Signing section. A valid ?Developer ID Application? certificate (exported in .p12 file format) is required with its correct keystore password. In order for an authenticated installer to be code signed at build time, follow the step below: Check the box for Code Signing in the Project>Platforms>Mac OS X>Code Signing section and specify the .p12 file and its correct password 2. By creating an unsigned installer at build time and code signing the IA created installer post build. In order to code sign an authenticated Mac OS X installer after build-time, refer to the PDF linked in this article. Specifically, the installer developer is required to follow the steps from the section: ?To code sign the build output (install.zip file) on a separate code-signing machine?. Note: Installanywhere generates the uninstaller and bundles it into the installer at build time. Therefore, a limitation of this method is that it is not possible to code sign the uninstaller. Therefore, such uninstaller installed by the authenticated installer will not function if the installer is code signed after build. In addition to code signing the installer, other steps are required to be completed prior to build in order to create an authenticated installer. InstallAnywhere is shipped with the helper tool, which is the file that is used to launch the installer or uninstaller with elevated privileges. The helper tool must be code signed with the same ?Developer ID Application? certificate that will be used to sign the installer. The signing of the helper tool should be done before build time. Note that the same certificate should be used to sign both the helper tool and the authenticated installer. Also, the signing of the helper tool is only required if creating authenticated installers. When only creating code signed installers that do not have authentication enabled, the step to sign the helper tool can be skipped. For more detailed information on the complete steps to sign the helper tool in preparation of authenticated installer, please refer to the PDF. Additional Information Note: Any code signing must be performed on Mac OS X system 10.9 or later. The signing of the helper tool and the installer must be done on Mac OS X. This means that if the installer is configured to be code signed during build time, the InstallAnywhere IDE or SAB must be installed on a Mac OS X machine and the installer build must be performed on Mac OS X. After the authenticated installer is built and launched on the target OS X system, the installer prompts for elevation and then installs the helper tool to the target system. The helper tool is installed with root privilege, which is capable of launching the installer launcher with the elevated privileges. For the complete detailed information on the new updated authentication support, refer to this PDF document.
View full article
Summary The article talks about the 'JRE Source does not exist' error on Mac OS X. Symptoms The following error is seen in the installation log on Mac OS X: Install Directory: /Applications/2013/jre Status: SUCCESSFUL Install JRE: /Applications/2013/jre Status: ERROR Additional Notes: ERROR - JRE Source does not exist Install JRE: Status: SUCCESSFUL Install Directory: /Applications/2013/ Status: SUCCESSFUL Additional Notes: NOTE - Directory already existed Cause The above error is seen with a project that is bundled with a JVM and configured to install bundled JVM even when not installing a LaunchAnywhere. This setting is configured in the installer project, at Project>JVM Settings>Installer Settings>Bundled/Downloaded Virtual Machine. In this setting, if the checkbox ?Only when installing a LaunchAnywhere? is not checked (as shown below), the error is written to the installation log on Mac OS X. However, the JRE is installed successfully and there is not any issue with the actual installation of the product. Resolution This issue was resolved in InstallAnywhere 2017. Please upgrade to take advantage of this fix. The resolved Issue# IOA-000084658 is listed under the Resolved Issues section in the InstallAnywhere 2017 Release Notes. Workaround There are two workarounds (listed as A and B below) to this issue that an installer developer can use depending on the installer use case: A) If the project is configured to install a LaunchAnywhere 1) Enable the above ?Only when installing a LaunchAnywhere? checkbox to resolve the error in the log. B) If the project is not configured to install a LaunchAnywhere 1) Enable the above ?Only when installing a LaunchAnywhere? checkbox. 2) Add a dummy LaunchAnywhere launcher to the installation phase by clicking on the ?Add Launcher? button in the Install sequence of the project. 3) Immediately after the launcher action, include an action to remove it. 4) The result is that the jre is installed and the end-user does not see the created dummy LaunchAnywhere.
View full article
Summary This article shows the supported Java virtual machines for different versions of InstallAnywhere Synopsis The following is a listing of Java virtual machines that are supported by InstallAnywhere organized by each version. Note: InstallAnywhere-generated installers are not supported on beta versions or on early-access releases of Java. Discussion InstallAnywhere 2018 SP1 Manufacturer Supported JVM Versions Sun 1.7.x, 1.8.x, 9 IBM 1.7.x, 1.8.x, 9 HP 1.7.x, 1.8.x, 9 Oracle 1.7.x, 1.8.x, 9, 10, 11 OpenJDK 1.7.x, 1.8.x, 9, 11 InstallAnywhere 2018 Manufacturer Supported JVM Versions IBM 1.7.x, 1.8.x, 9 HP 1.7.x, 1.8.x, 9 Oracle 1.7.x, 1.8.x, 9, 10 OpenJDK 1.7.x, 1.8.x, 9 InstallAnywhere 2017 Manufacturer Supported JVM Versions Sun 1.6.x, 1.7.x IBM 1.6.x, 1.7.x, 1.8.x HP 1.6.x, 1.7.x Oracle 1.7.x, 1.8.x InstallAnywhere 2015 Manufacturer Supported JVM Versions Sun 1.6.x, 1.7.x IBM 1.6.x, 1.7.x, 1.8.x HP 1.6.x, 1.7.x Oracle 1.7.x, 1.8.x InstallAnywhere 2014 Manufacturer Supported JVM Versions Sun 1.6.x, 1.7.x IBM 1.6.x, 1.7.x HP 1.6.x Oracle 1.7.x, 1.8.x Note: InstallAnywhere 2014 now supports Oracle Java 8 on Apple OS X Mountain Lion (10.8) and OS X Mavericks (10.9) InstallAnywhere 2013 Manufacturer Supported JVM Versions Sun 1.5.x, 1.6.x, 1.7.x IBM 1.5.x, 1.6.x, 1.7.x Apple 1.5.x, 1.6.x HP 1.5.x, 1.6.x Oracle 1.7.x Note: Installers built with InstallAnywhere 2013 support running with Java 8 on all platforms except Mac OS X. InstallAnywhere 2013 also has support for building OS X?based installers that use Java 7 at run time, and has support for creating VM packs with Oracle JRE 7, as well as for bundling installers with Oracle JRE 7. InstallAnywhere 2012 Manufacturer Supported JVM Versions Sun 1.5.x, 1.6.x, 1.7.x IBM 1.5.x, 1.6.x, 1.7.x Apple 1.5.x, 1.6.x HP 1.5.x, 1.6.x Oracle 1.7.x InstallAnywhere 2011 Manufacturer Supported JVM Versions Sun 1.4.x, 1.5.x, 1.6.x IBM 1.4.x, 1.5.x, 1.6.x, 1.7.x Apple 1.4.x, 1.5.x, 1.6.x HP 1.4.x, 1.5.x, 1.6.x Oracle 1.7.x
View full article
Summary This is the InstallAnywhere HotFix for Windows Launchers Symptoms This HotFix addresses the following issues: IOJ-1737900 Without VM installer fails to launch using Java 8 Update 60 on Windows. The error displayed is ?Windows error 2 occurred while loading the Java VM?. IOJ-1739427 LaunchAnywhere launcher fails to launch target application using Java 8 Update 60 on Windows. IOJ-1741088 Hotfix for Windows Launchers causes built installer to generate Windows error on Windows XP and Windows Server 2003. Resolution The HotFix is provided through a common patch installer for the following versions of InstallAnywhere and can be obtained by checking for updates from the InstallAnywhere IDE. InstallAnywhere 2013 InstallAnywhere 2014 InstallAnywhere 2014 SP1 InstallAnywhere 2015 The patch installer for the HotFix will only patch one instance of InstallAnywhere at a time. That is, if user has multiple InstallAnywhere versions installed, for instance, InstallAnywhere 2014 and InstallAnywhere 2015 are both present in the system, the user can choose to patch only one version/instance at a time. So if the user chooses to patch IA 2014, the installer will install the patch for that chosen instance of IA 2014 and exit. To patch another version/instance of the product, the user should run the installer again. Below are the direct download links for the HotFix installers: Windows Apple OS X Solaris Sparc Linux (32-bit) Linux (64-bit) To obtain the HotFix for InstallAnywhere 2012 SP1, download the zip file listed below: launchanywh eres .zip To apply the downloaded HotFix on top of InstallAnywhere 2012 SP1, follow the steps below: Make sure InstallAnywhere 2012 SP1 is not running Go to the directory where you installed InstallAnywhere 2012 SP1 and backup the ?windows? directory present at resource\launchanywheres directory Extract the contents of the attached zip file making sure the extracted contents replace the files inside the resource\launchanywheres\windows directory To verify that the Hotfix was applied, navigate to the: <IA_HOME>/resource/launchanywheres/windows directory, where <IA_HOME> is where InstallAnywhere was installed. Right-click one of the executables in the: <IA_HOME>/resource/launchanywheres/windows directory. Under the Details Tab the File version should be: InstallAnywhere Version File Version InstallAnywhere 2015 17.0.2.0 InstallAnywhere 2014 SP1 16.5.2.0 InstallAnywhere 2014 16.0.2.0 InstallAnywhere 2013 15.0.2.0 InstallAnywhere 2012 SP1 14.0.2.0 Additional Information The fix should be applied on top of latest HotFix available for the version of InstallAnywhere listed above. Below are the links to: HOTFIX: InstallAnywhere 2013 HotFix C HOTFIX: InstallAnywhere 2014 HotFix A HOTFIX: InstallAnywhere 2014 Service Pack 1 HotFix A For more information on the issue IOJ-1737900 , refer to the KB article The Without VM Installer Fails To Launch Using Java 8 Update 60 On Windows.
View full article
Summary Concurrent License Server Error EXITING DUE TO SIGNAL 37 Exit reason 5: Vendor daemon can't talk to lmgrd. Symptoms EXITING DUE TO SIGNAL 37 Exit reason 5: Vendor daemon can't talk to lmgrd Cause This error is known to occur on Linux due to a permissions issue if lmadmin was installed as root. Resolution Move the installation to a non-root user path and log in as a non-root user Restart the license server
View full article
Summary This article goes over why the Valid VM List will not work with a pure Java installer and provides a workaround for this limitation Synopsis You can specify a list of Java Virtual Machines for the installer to run with under the Project > JVM Settings > Installer Settings > Valid VM list setting. However, this setting will only affect the launcher for the installer. When selecting the Other Java-Enabled Platforms build target, a pure Java installer will get created, in which case a launcher will not be used. As a result, launcher-specific settings will not affect a pure java installer. To limit a pure Java installer to only run on certain JVMs, refer to the discussion below. Discussion The following example outlines how to set a "valid VM list" for an installer to run only on Java 7 and Java 8: In the project, go to Project > Rules and add a "Compare InstallAnywhere Variables" Rule Set the properties of the Rule as follows: Operand 1 = $prop.java.version$ contains Operand 2 = 1.7 Add another "Compare InstallAnywhere Variables" Rule Set the properties of the Rule as follows: Operand 1 = $prop.java.version$ contains Operand 2 = 1.8 Modify the Rule expression to 'OR' the Rule ID's. EX: CIAV111 || CIAV222 (Where CIAV# are the ID's designated for each rule added) What this rule expression will do is check that the Java System Property, java.version contains 1.7 or 1.8. If the System Property does not contain either string, the installer will display the message specified in the Message to Display if Installer Rules Fail field then exit the installation. Additional Information Installer Rules View Rules Reference Building Complex Rule Expressions
View full article