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 more

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. Version and Edition of InstallAnywhere Include the version and edition of InstallAnywhere used to design and build the installer.  Going to Help > About InstallAnywhere in the IDE is one of the easiest ways to verify this information. IDE or Standalone Build Specify whether you are using InstallAnywhere as a standalone product with its IDE or using the Standalone Build to build a project. InstallAnywhere Project File Provide your InstallAnywhere project file. This file has a .iap_xml file extension. The project file allows the Support Engineer to review your project settings, try to reproduce the issue, and so forth. When the Error Occurs Most errors can be classified as either a “Design-/Build-Time Error” or an “Install-Time/Runtime Error” depending on whether the issue occurs in the process of creating your installer or when running your installer. A Full Java Stack Trace, If Applicable If there is an error and/or a Java stack trace, it is critical to provide the full error message and/or full Java stack trace. This information is useful in tracing the origin and possible cause of the issue. Expected Versus Actual Results Describe in as much detail as possible what you expect the behavior to be and what the actual behavior observed is. Screenshots When applicable, including screenshots often provides valuable information that supplements the written description of the issue.  Screenshots comparing expected to unexpected or desired to actual appearance/behavior can be incredibly helpful. Reproducibility The best way to ensure a timely resolution to your issue is to provide a list of steps the Support Engineer can use to reproduce the issue you’re reporting.  Steps to reproduce that start with creating a new project in InstallAnywhere are the best, though not always possible.  Detailed steps to reproduce the issue allow the Support Engineer to understand the exact scenario and submit the issue to Engineering if necessary. Verbose Log File Attaching a verbose log file from when the issue was reproduced is always a good idea.  See the following Knowledge Base articles for more information regarding generating a log file: Logging an Installation with InstallAnywhere Verbosely Log a Command-Line Build on Windows and Linux Verbosely Log a Command Line Build on Mac Additional Pertinent Details Providing any additional details you believe are integral to the issue being reported is most often helpful.  It’s often better to provide more details than necessary rather than providing too few. ... View more

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 InstallShield case to Flexera Technical Support. Version and Edition of InstallShield Include the version and edition of InstallShield used to design and build the installer.  Going to Help > About InstallShield in the IDE is one of the easiest ways to verify this information. IDE, Stand Alone Build, Integration with Visual Studio Specify whether you are using InstallShield as a stand-alone product with its IDE, using the Stand Alone Build to build a project, or using InstallShield integrated with Visual Studio. Project Type There are several project types available in InstallShield.  Including the project type being used will clear up any ambiguity and allow the Support engineer to dive right in to troubleshooting.  With the project open in the IDE, the project type will be listed alongside the project name on the title bar of the IDE.  Otherwise, attaching a copy of the project file to your case will allow the Support engineer to quickly determine the project type. When the Error Occurs Most errors can be classified as either a “Design/Build Time Error” or a “Runtime Error” depending on whether the issue occurs in the process of creating your installer or when running your installer. Expected Versus Actual Results Describe in as much detail as possible what you expect the behavior to be and what the actual behavior observed is. Screenshots When applicable, including screenshots often provides valuable information that supplements the written description of the issue.  Screenshots comparing expected to unexpected or desired to actual appearance can be incredibly helpful. Reproducibility The best way to ensure a timely resolution to your issue is to provide a list of steps the Support engineer can use to reproduce the issue you are reporting.  Steps to reproduce that start with creating a new project in InstallShield are the best, though not always possible.  Detailed steps to reproduce the issue allow the Support engineer to understand the exact scenario and submit to Engineering if necessary. Verbose Log File Attaching a verbose log file from when the issue was reproduced is always a good idea.  See the following Knowledge Base articles for more information regarding generating a log file: Logging an MSI Installation Logging an InstallScript Project Logging an InstallScript MSI Project Logging an Express Installation Verbosely Log a Command Line Build Additional Pertinent Details Providing any additional details you believe are integral to the issue being reported is most often helpful.  It’s often better to provide more details than necessary rather than providing too few. ... View more

Summary 11-July-2014 ? On 8-July-2014, Microsoft released KB2962872 (MS14-037), a security update for Internet Explorer versions 6, 7, 8, 9, 10 and 11. Please be advised that applying Microsoft security update KB2962872 (MS14-037) may cause the InstallShield or InstallShield for AdminStudio application to crash upon launch. NOTE: The issue affects only InstallShield development tools and does not affect InstallShield Standalone Build or any installers built with InstallShield. Synopsis UPDATE: On 12-August-2014, Microsoft released KB2976627 (MS14-051), a security update for Internet Explorer. This update replaces KB2962872 (MS14-037), an earlier Microsoft security update that led to crashes in InstallShield and InstallShield for AdminStudio. Security update KB2976627 (MS14-051) has been found to resolve those crashes. Therefore, it is recommended that users who are affected by that issue install security update KB2976627 (MS14-051) on their machines. Once this security update has been applied, InstallShield patch IOJ-1662902 can be uninstalled. 17-July-2014 ? While Microsoft continues to develop a fix through Windows Update to address this issue, Flexera has created an interim solution. This patch resolves the crashes caused by KB2962872 (MS14-037) for all affected versions of InstallShield and InstallShield for AdminStudio. ORIGINAL NOTICE: 11-July-2014 ? On 8-July-2014, Microsoft released KB2962872 (MS14-037), a security update for Internet Explorer versions 6, 7, 8, 9, 10 and 11. Please be advised that applying Microsoft security update KB2962872 (MS14-037) may cause the InstallShield or InstallShield for AdminStudio application to crash upon launch. NOTE: The issue affects only InstallShield development tools and does not affect InstallShield Standalone Build or any installers built with InstallShield. Discussion Products Affected InstallShield 2008 through 2014 InstallShield for AdminStudio Edition 8.6 through v.12 (2013) Products Not Affected InstallShield versions prior to InstallShield 2008 InstallShield Limited Edition for Visual Studio Get the InstallShield Patch (IOJ-1662902) UPDATE 12-August-2014: With the release of Microsoft Update KB2976627 (MS14-051) the InstallShield Patch IOJ-1662902 is no longer needed. Once KB2976627 (MS14-051) has been installed, the InstallShield Patch can be uninstalled. The InstallShield patch can be obtained through two different methods and resolves the InstallShield crash issues caused by Windows Update KB2962872 (MS14-037). This patch works for all affected versions of InstallShield and InstallShield for AdminStudio. This patch will disable the ability to build projects using InstallShield?s Trialware features: Try and Die, and Try and Buy. Installable Patch: Download and Run InstallShieldIOJ1662902Update.exe This patch can be uninstalled to restore the InstallShield Trialware capabilities. Uninstall of the patch is not advised until after Microsoft releases a Windows Update fix. We will update this page at that time. Manual Installation files: Download IOJ-1662902.zip Make a backup of \<ProgramFiles>\InstallShield\<version>\System\ClientPliApi.dll \<ProgramFiles>\InstallShield\<version>\System\ProtectionProcessor.dll Extract IOJ-1662902.zip to \<ProgramFiles>\InstallShield\<version>\System\ Additional Information Who to Contact for Questions If you have logged a ticket with our technical support team regarding this issue, please do not submit an additional ticket. Your request has been logged. Please contact our Technical Support team at support@flexera.com if you have additional questions not addressed here. ... View more

Summary If you find that it will be necessary to move your license to a new machine, the license must first be returned or deactivated from the previous machine before it can be activated on the new machine. Synopsis InstallShield node-locked licenses are single-machine, single-user licenses according to the End-User License Agreement (EULA). This means that they can be activated on one machine and accessed by one user. If moving a license to a new machine is required, the license must be returned or deactivated from the machine on which it is currently activated, before attempting to activate the license on a new machine. Please note that there is a return limit for each type of licence: Node Locked Licence If your licence is a node locked licence, then you are allowed to return/deactivate/transfer your licence up to a maximum of four times per year. Concurrent Licence If your licence is a concurrent licence and you would like to return/transfer it from the current licence server to a new/another licence server, then please note that there is a return/transfer limit of 2 returns/transfers per year. Discussion This section included steps for both online and offline activation methods of deactivation. Online Deactivation: 1) Reinstall the software on the previous machine (if it has been uninstalled). 2) From the command-line change directories to the appropriate default path: InstallShield Default Path InstallShield 2008 Express C:\Program Files\Macrovision\IS 2008 Express\System InstallShield 2008 Pro/Premier C:\Program Files\Macrovision\IS2008\System InstallShield 2009 Express C:\Program Files\InstallShield\2009 Express\System InstallShield 2009 Pro/Premier C:\Program Files\InstallShield\2009\System InstallShield 2010 Express/Pro/Premier C:\Program Files\InstallShield\2010\System InstallShield 2011 Express/Pro/Premier C:\Program Files\InstallShield\2011\System InstallShield 2012 Express/Pro/Premier C:\Program Files\InstallShield\2012\System InstallShield 2012 Spring Express/Pro/Premier C:\Program Files\InstallShield\2012Spring\System InstallShield 2013 Express/Pro/Premier C:\Program Files\InstallShield\2013\System InstallShield 2014 Express/Pro/Premier C:\Program Files\InstallShield\2014\System InstallShield 2015 Express/Pro/Premier C:\Program Files\InstallShield\2015\System InstallShield 2016 Express/Pro/Premier C:\Program Files\InstallShield\2016\System InstallShield 2018 Express/Pro/Premier C:\Program Files\InstallShield\2018\System Note: For 64 bit machines, the default location will be under the (x86) Directory. For example: InstallShield 2011 on a 64-bit machine will be located at C:\Program Files (x86)\InstallShield\2011\System 3) For InstallShield, execute the following Command: TSconfig /return Activation Server URL: activationservice.installshield.comNote: We suggest allowing incoming and outgoing traffic to and from *.flexerasoftware.com and *.installshield.com as well as making sure that ports 80, 443 & 8443 are open. Offline Deactivation: 1) Reinstall the software on the previous machine (if it has been uninstalled) 2) Open up a Command Prompt and CD to the appropriate default path. 3) Execute the following command for InstallShield which will generate a request code: TSconfig /return /no_internet 4) For InstallShield 2014 and later, process the request code at our Product and License Center self-service web page. . Additional Information If you have InstallShield 2010 or newer, you can also return the license by going to Help->About InstallShield and selecting the return button. If you have successfully deactivated your license, but are unable to activate InstallShield on a new machine: 1) See the links below for additional information and troubleshooting steps regarding activation. 2) If further assistance is required, contact Support . ... View more

Summary InstallShield 2016 Known Issues Synopsis This article contains a list of hyperlinks to articles about known issues, workarounds, hotfixes, and related information for InstallShield 2016. The article will be updated as new information becomes available. Discussion InstallShield 2016 Known Issues Issue Number Description Fix (if available) IOJ-1812110 CMDLINE Variable used in InstallShield includes '-IS_temp -IS_OriginalLauncher:<Path_to_setup.exe>' Resolved in InstallShield 2016 SP1. IOJ-1774403 Error 7354 When Building MSI with MoveFile Table Entry InstallShield 2016 Hotfix available here: Error 7354 When Building MSI with MoveFile Table Entry Resolved in InstallShield 2016 SP1. IOJ-1774042 Install conditions for .Net Framework versions do not work when created using our Project Assistant Modify the condition in the Installation Designer and prefix the value with the pound sign (#) Resolved in InstallShield 2016 SP1. IOJ-1771076 InstallScript Setup Launcher Unicode has stopped working during setup initialization Resolved in InstallShield 2016 SP1. IOJ-1777822 InstallScript Setup Launcher Unicode error during shortcut creation Resolved in InstallShield 2016 SP1. IOJ-1815849 Multi-Language Installations No Longer Work When Using the /clone_wait Command Line Parameter InstallShield 2016 SP1 Hotfix available here: Multi-Language Installations No Longer Work When Using the /clone_wait Command Line Parameter Resolved in InstallShield 2016 SP2. Additional Information InstallShield 2016 SP1 and SP2 can be downloaded from the Product and License Center Related KB Articles Error 7354 When Building MSI with MoveFile Table Entry ... View more

Summary This article contains a list of hyperlinks to articles about known issues, workarounds, hotfixes, and related information for InstallShield 2015. The article will be updated as new information becomes available. Synopsis This article contains a list of hyperlinks to articles about known issues, workarounds, hotfixes, and related information for InstallShield 2015. The article will be updated as new information becomes available. Discussion InstallShield 2015 Known Issues Issue Number Description Fix (if available) IOJ-1733677 Visual Studio hangs / GUI becomes unresponsive at Files and Folders View Visual Studio Hangs / becomes Unresponsive after integration with InstallShield 2015 IOJ-1733016 Build error -7325, -6212, or -6213 occurs when building a project containing .NET assembly through Visual Studio or MSBuild ISDEV : fatal error -6213: Internal build error ISDEV : fatal error -6212: Internal build error Build error -7325: An unexpected error occurred validating the architecture (note same hotfix is valid for all three) IOJ-1735718 Windows Update KB3072630 causes Registry permission changes to HKCU to fail Windows Update KB3072630 causes Registry permission changes to HKCU to fail IOJ-1737342 Build error ?-7240? occurs when building a release associated with a release flag that excludes a feature HOTFIX: InstallShield 2015 Suite Build Error '-7240' IOJ-1752933 HOTFIX: Install Fails With Error 1001 HOTFIX: Install Fails With Error 1001 Related KB Articles ISDEV : fatal error -6213: Internal build error ISDEV : fatal error -6212: Internal build error Build error -7325: An unexpected error occurred validating the architecture Visual Studio Hangs / becomes Unresponsive after integration with InstallShield 2015 ISDEV : Windows Update KB3072630 causes Registry permission changes to HKCU to fail ... View more

Summary This article documents known issues for InstallShield 2014. Synopsis This article contains a list of hyperlinks to articles about known issues, workarounds, hotfixes, and related information for InstallShield 2014. The article will be updated as new information becomes available. Discussion InstallShield 2014 Known Issues Issue Number Description Fix (if available) IOJ-1660031 "Unspecified Error" displayed in Visual Studio Japanese accessing InstallScript view HOTFIX: "Unspecified Error" Displayed in InstallScript View When InstallShield Japanese is Integrated With Visual Studio IOJ-1661158 Distributing Releases to a Virtual Machine that InstallShield Provisions at Build Time or on Demand does not work - Error 28: Out of stack space IOJ-1663885 Patch update.exe is not signed when specified to do so As a workaround, find the appropriate ISPatchConfigurationProperty - SignaturePassword field in the direct editor and replace its value with the raw password. IOJ-1663062 Major upgrade of an InstallScript/MSI project terminates unexpectedly Run the major upgrade in compatibility mode. IOJ-1664081 InstallScript system variables FOLDER_APPLICATIONS64 and PROGRAMFILES64 do not resolve correctly during uninstallation IOJ-1665767 XML File Changes configured not to format target file leave target file formatted after uninstallation IOC-000061592 Setting a Component's .NET Precompile Assembly property to Yes uses .NET 1.1 command line values when project is configued to use later versions of the .NET framework As a workaround, use a custom action to call ngen.exe with command line values appropriate for the targeted version of the .NET framework. IOJ-1667248 CopyFile on locked file causes installation to hang HOTFIX: CopyFile on Locked File Results in Installation Hanging IOJ-1720774 Unable To Obtain New License From Trialware View HOTFIX: Unable To Obtain New License From Trialware View IOJ-1721225 InstallScript Project package fails during Suite installation HOTFIX: Suite Fails with an InstallScript Project (.ism) Package IOJ-1726120 The computer image on the left side of the InstallScript skinned dialog does not appear on the progress dialog HOTFIX: No Image on the Left Side of the STATUSEX Dialog IOJ-1727555 64 bit system variables resolve to their respective 32 bit paths on an upgrade install where the base was created with an older version of InstallShield HOTFIX: 64 bit System Variables Resolves to 32 bit Path During an Upgrade IOJ-1719756 Properties contained in ISHiddenProperties and passed as arguments to the Suite launcher or to any packages are logged in plain text HOTFIX: Properties contained in ISHiddenProperties and passed as arguments to the Suite launcher or to any packages are logged in plain text IOJ-1721173 When attempting to use the "Distribute to VM" feature using InstallShield 2014 SP1 and supplying an invalid path, InstallShield will become unresponsive HOTFIX: Distribute to VM with Invalid Path Results in InstallShield Becoming Unresponsive IOJ-1723088 The install log is not getting created when the installation log location is set to a UNC path Additional Information HOTFIX: "Unspecified Error" Displayed in Japanese Visual Studio InstallScript View HOTFIX: No Image on the Left Side of the STATUSEX Dialog HOTFIX: CopyFile on Locked File Results in Installation Hanging HOTFIX: Suite Fails with an InstallScript Project (.ism) Package HOTFIX: Properties contained in ISHiddenProperties and passed as arguments to the Suite launcher or to any packages are logged in plain text HOTFIX: Distribute to VM with Invalid Path Results in InstallShield Becoming Unresponsive ... View more

Summary This article contains a list of known issues, workarounds, hotfixes, and related information for InstallAnywhere 2014. The article will be updated as new information becomes available. Synopsis This article contains a list of known issues, workarounds, hotfixes, and related information for InstallAnywhere 2014 and InstallAnywhere 2014 SP1. The article will be updated as new information becomes available. Discussion InstallAnywhere 2014 Known Issues: Issue Description IOJ-1665770 Mac OS X authenticated launchers created with InstallAnywhere 2014 do not launch. IOJ-1663318 If authentication is enabled in two or more OS X-based installers and an end user tries running these installers simultaneously, the authentication prompts for administrator name and password may not be displayed. Thus, standard users may not have adequate privileges to complete either installer. IOJ-1663773 If authentication is enabled in an OS X-based installer, the files that were extracted to the $TMPDIR and /tmp locations are not deleted by the installer or the uninstaller. IOJ-1664183 The Execute Uninstaller action does not uninstall a product from OS X-based systems if authentication was enabled in the original installer. In addition, if an upgrade attempts to uninstall an earlier version of a product before installing the new version on an OS X-based system, and if authentication is enabled in the base version of the product, the upgrade cannot successfully uninstall the earlier version or install the latest version. IOJ-1664447 If authentication is enabled for OS X-based installers and launchers, the run-time panels do not respond to any keyboard events. As a result, end users must use the mouse to click and select controls such as buttons and radio buttons. VoiceOver, the built-in screen reader that is available on OS X-based systems, cannot read the text on the run-time panels. This appears to be a bug in Java rather than in InstallAnywhere, since the same issue occurs with a Swing-based Java application. The InstallAnywhere team has reported the bug to Oracle. To work around the issue and enable end users to enter text for run-time panels, whenever an end user clicks a text box, a native dialog box opens, enable the end user to enter the appropriate text. When the native dialog box is dismissed, the text that the end user entered is displayed in the text box that the end user had clicked on the run-time panel. To avoid displaying the native dialog box at run time, set the new variable $IA_BLOCK_OSX_USE_SECURE_POPUP_DIALOG_FOR_AUTHENTICATION$ to *yes* or *true*. IOJ-1664588 The strings for some of the controls on the Tomcat Runtime Deployment panel may be truncated on the Japanese version of this panel: ?Choose button--If the Local Tomcat server option is selected on this panel, the panel includes a Choose button next to the Local Tomcat server path setting. Part of the text on the Choose button is cut off on the Japanese version of this panel. ?Test Connection button--If the Remote Tomcat server option is selected on this panel, the panel includes a Test Connection button. Part of the text of the Test Connection button is cut off on the Japanese version of this panel. ?Save the WAR locally on the target system for later deployment option--If this option is included on this panel, part of the last character in the label for this option is cut off. IOJ-1664649 The Always Show GUI setting is available under the Authentication setting (Project Page > Platforms view > Mac OS X area). If you select Yes for this setting, InstallAnywhere's built-in Authentication panel is not displayed at run time. (InstallAnywhere's built-in Authentication panel has the text "You need an Administrator password to install the software" and a lock icon that end users need to click to display the standard OS X-based credentials prompt.) IOJ-1665180 The InstallAnywhere 2014 installer or any installer created using Installanywhere 2014 that is not located at least 3 folders deep fails to launch on a *nix platform when run as root. IOJ-1665716 If an uninstaller created with InstallAnywhere 2014 is run as root on a *nix machine, the uninstaller fails to launch. IOJ-1663251 Rules on Install Sets intermittently do not execute causing Install Sets to be available on the Choose Install Sets Panel which should not be. InstallAnywhere 2014 SP1 Known Issues: Issue Description IOA-000125033 Java applications that are launched using a Java 7 graphical LaunchAnywhere cannot write to relative paths on Apple OS X-based systems in some scenarios, such as when the application is launched by double-clicking it from within the Finder. As a workaround, the application can be launched from the executable stub within the .app structure, or you can offer a Console launcher. IOJ-1662464 Under certain conditions, a LaunchAnywhere launcher that is installed on an OS X-based system and using Java 7 cannot find and load a required native library that is installed to $USER_INSTALL_DIR$. IOJ-1664319 A graphical LaunchAnywhere launcher that is installed on an OS X-based system and using Java 7 cannot access a file that is in the same folder as the launcher and is referenced by a relative path. The problem does not exist for the console launcher, or if an absolute path is used to reference the file. IOJ-1699420 OS X-based, code-signed installers that include authentication support do not create uninstaller shortcuts. IOJ-1718753 If a CD-ROM installer that targets OS X-based target systems installs merge modules, the merge modules cannot be uninstalled from the $USER_INSTALL_DIR$ directory where the merge module is located. IOJ-1719020 Maintenance mode and instance management do not work as expected for CD-ROM installers that target OS X-based target systems. For example, an attempt to try to manage an existing installed instance and remove a feature leads to the installer to stop responding. IOJ-1699908 When an installer includes an imported merge module and Red Hat Package Management (RPM) registration is enabled in the merge module, it takes much more time to install and uninstall the merge module on Red Hat Enterprise Linux 7 systems then it does for earlier versions of Red Hat Enterprise Linux. IOJ-1700753 If you add authentication support to an OS X-based installer and an end user runs the installer on an Apple OS X 10.10 target system, the installer launches a second time and then exits; this occurs after the end user clicks Done for the initial run of the installer. IOJ-1700997 The About dialog box in InstallAnywhere on OS X-based versions shows version 1.0 of InstallAnywhere instead of 16.5 for InstallAnywhere 2014 SP1. IOJ-1720113 In certain scenarios, the default icon is used in the Finder instead of a custom icon for the uninstaller launcher on OS X-based target systems. This occurs if the custom icon file is for a merge module that includes authentication support. The custom icon is displayed in the Dock only when the uninstaller is running. ... View more

Summary When fulfilling an upgrade order for a concurrently licensed product, a license file will be generated which includes an UPGRADE line. In order to make use of this license file, there are a number of considerations to take into account. Synopsis When fulfilling an upgrade order for a concurrently licensed product, such as InstallShield or InstallAnywhere, a license file will be generated which includes an UPGRADE line. In order to make use of this license file, there are a number of considerations to take into account. This article discusses these considerations and describes how to make use of the license. Discussion Creating the license file The upgrade license file will not replace the existing license file. It will be used in addition to the existing file. When generating the file, the HostID must be identical to the HostID used to generate the original license file. Using the license file There are two options to put the upgrade license file in use: 1. Add the UPGRADE line from the upgrade license to the existing license file. For example, if the existing license file contains: SERVER HostName 00137238bb89 VENDOR mvsn USE_SERVER FEATURE IAEE mvsn 9.5 permanent 15 DUP_GROUP=UH SIGN="1B05 5F12 663D\ 83E6 8A00 889F FF81 3B50 4AC1 8BA1 BC09 1D41 87AA 102A A02D \ 0FAC 1C11 120C 16B3 458D 3740 97F4 5C40 0805 F269 E18D A732 \ 1E3D C3C4 D6EC" And the upgrade license contains: SERVER HostName 00137238bb89 VENDOR mvsn USE_SERVER UPGRADE IAEE mvsn 9.5 10.0 permanent 15 DUP_GROUP=UH TS_OK SIGN="032D \ FDFB 76D5 1B01 B6E7 BB88 2055 B433 1A59 9413 BA13 C4E3 CF40 \ 545E 06FA 0851 6BE9 453C 7CDC 22CA A137 6A8B 39BA 4972 5B20 \ DA35 5F24 288D 3CF2 857D" Combine the files by copying the UPGRADE line from the upgrade license and pasting it in the existing file: SERVER HostName 00137238bb89 VENDOR mvsn USE_SERVER FEATURE IAEE mvsn 9.5 permanent 15 DUP_GROUP=UH SIGN="1B05 5F12 663D\ 83E6 8A00 889F FF81 3B50 4AC1 8BA1 BC09 1D41 87AA 102A A02D \ 0FAC 1C11 120C 16B3 458D 3740 97F4 5C40 0805 F269 E18D A732 \ 1E3D C3C4 D6EC" UPGRADE IAEE mvsn 9.5 11.0 permanent 15 DUP_GROUP=UH TS_OK SIGN="032D \ FDFB 76D5 1B01 B6E7 BB88 2055 B433 1A59 9413 BA13 C4E3 CF40 \ 545E 06FA 0851 6BE9 453C 7CDC 22CA A137 6A8B 39BA 4972 5B20 \ DA35 5F24 288D 3CF2 857D" After modifying the license file, restart the License Server. 2. Configure the license server to read both the existing and upgrade license files. First, copy both the existing license file and the upgrade license file to the same directory. Then, launch the license server from the command line: Windows lmgrd.exe -c <FULL_PATH_TO_DIRECTORY> Non-Windows lmgrd -c <FULL_PATH_TO_DIRECTORY> Verifying the licenses have been upgraded After restarting the license server, check the debug log. If the upgrade has been successful, there should be an entry in the debug log file as the server starts up similar to: 10:39:53 (mvsn) FLEXnet Licensing version v11.4.0.0 build 31341 10:39:54 (mvsn) UPGRADING 15 "IAEE" from version 9.5 to version 11.0 After a successful upgrade, versions from that referenced in the existing file to that referenced in the upgrade file are able to check out and use licenses. Additional Information Additional Considerations It is not necessary that the existing license file contain a FEATURE or INCREMENT line which exactly matches the version referenced in the UPGRADE line. The license server will upgrade any INCREMENT or FEATURE line which references a version greater than or equal to the one referenced in the UPGRADE line. For example, the UPGRADE line: UPGRADE IAEE mvsn 9.5 11.0 permanent 15 DUP_GROUP=UH TS_OK SIGN="1AC1 \ 4E1F 3B2A 1FB9 31C8 E6BD 4FBF 7DB0 7D45 7B25 FC3E E442 00B5 \ AA4F E6E5 0A11 6551 947A 8CA5 9457 01D4 BF2E F7E0 B7F6 8BB5 \ 10BF E510 2D4B 58AB D226" will upgrade any IAEE INCREMENT or FEATURE line of version 9.5 or greater to version 11.0. An UPGRADE line does not provide additional licenses. It simply upgrades the licenses contained in an existing file to the version specified. When fulfilling an order for an upgrade license, it is not necessary to configure a new license server. The upgrade license file will be used with an existing license server. Therefore, the instructions in the order regarding downloading a license server may be ignored. In order to use InstallAnywhere 2008 Value Pack 1 with an upgraded license file, a HotFix must be applied to the client machine. The HotFix may be downloaded here: InstallAnywhere 2008 Concurrent License Update. The zip file contains a ReadMe.txt file which explains how to apply the HotFix. In order to use InstallShield 2008 and 2009 with an upgraded license file, a HotFix must be applied to the client machine. The HotFix may be downloaded here: InstallShield 2008 and InstallShield 2009 Concurrent License Update. In order to verify whether or not the HotFix has been previously installed, check the System folder under the InstallShield install location for the files: ISUIServices_libFNP.dll.bak ISUIServices.dll.bak If these files exist, the HotFix has been applied previously and InstallShield will be able to check out upgraded licenses. InstallAnywhere 2009 will not check out upgraded licenses. In order to use an upgraded license with InstallAnywhere 2009, InstallAnywhere must be upgraded to InstallAnywhere 2009 Service Pack 2. InstallShield Versions Product Version Version in License File InstallShield 2008 14.0 InstallShield 2009 15.0 InstallShield 2010 16.0 InstallShield 2011 17.0 InstallShield 2012 18.0 InstallShield 2012 Spring 19.0 InstallShield 2013 20.0 InstallShield 2014 21.0 InstallShield 2015 22.0 InstallShield 2016 23.0 InstallShield 2018 24.0 InstallAnywhere Versions Product Version Version in License File InstallAnywhere 2008 Value Pack 1 9.5 InstallAnywhere 2009 (All Service Packs) 10.0 InstallAnywhere 2010 11.0 InstallAnywhere 2010 Service Pack 1 11.5 InstallAnywhere 2011 12.0 InstallAnywhere 2012 14.0 InstallAnywhere 2013 15.0 InstallAnywhere 2014 16.0 InstallAnywhere 2015 17.0 InstallAnywhere 2017 18.0 InstallAnywhere 2018 19.0 ... View more