Download File Action can be used to download file using FTP, HTTP or SFTP.  InstallAnywhere IDE->Sequence->Install->Add Action->DownloadFileAction. Execute Command action can be used to run executable files as you would from the target system’s command line. InstallAnywhere IDE->Sequence->Install->Add Action->General->Execute Command. And check platform rule can be applied to restrict an action to run on a particular OS. After adding the action, rule can be applied to the action as follows: Select the action. Rules tab->Add Rule->Check Platform->Add. In the customizer, "Perform On" list can be configured. Once this rule is applied,  Execute Command action will execute only in the configured platforms. Can add multiple Execute command actions and apply rule. ... View more

Project source file should  be .iap_xml file and it is in the format required for InstallAnywhere.  This format has not been changed.  An issue was noticed wherein the Order of <object class="com.zerog.ia.installer.util.LAXPropertyData"> project XML tag  was changing with every save of project making source control merges of projects difficult. Further there has been an issue with ObjectIDs of VMWareCredentialInformationImp & few other xml tags changing on every project save/load. These merge issues has been fixed in InstallAnywhere 2020SP2. When you do merge of the project file you are noticing similar issue? Can you provide info on the random xml tags that are getting created? Can you please do a diff & share the screen shot of the unknown tags created on open/save of project file? ... View more

Hi emalloy, In case you are using Speed Folder, it has known issue when configured to install archive file with size more than 4GB. But in such scenario it throws an exception whereas no exception is seen in the details mentioned. One scenario where installer continuously asks for a new location, even when adequate space is available, is when a payload attached is corrupted. An installer with a corrupted payload launches, then repeatedly prompts the user for a new location in an endless loop.  Verify that the added files are not corrupted. After replacing the corrupted files if the issue still persist raise a support ticket. ... View more

Hi emalloy, Can you let us know which version of InstallAnywhere you are using? Please also share the screenshot of the message displayed. ... View more

Hi @jakobsachs, The issue seen is due to the use of 32 Bit  java for Windows 64 Bit installer. Have to use 64 Bit java. Please  verify that the java used/bundled is 64 Bit. Try using LAX_VM parameter to override the JRE that the installer uses as follows: <InstallerName>  LAX_VM <full_path_to_64Bit_java_executable> Eg: install.exe   LAX_VM   "C:\Program Files\Java\jdk-9\bin\java.exe" And Windows OS should be 64 bit. Windows Pure 64 Bit installers cannot be run on 32-bit Windows-based systems. ... View more

This seems to be due to the uninstaller's inability to delete HKEY_CLASSES_ROOT keys when its default(Default) value is set. If default registry value is not set, the HKEY_ROOT keys added are getting deleted on uninstall, when Uninstall Options in the "Set Windows Registry - Multiple Entries" action is set to "Force removal even if values has changed". The keys with default value set are not deleted but seems false positive is seen in log. Since file association keys require setting default value, The workaround will be to : set Uninstall options to "Do not Uninstall" and add a script to delete the keys in Sequence->Uninstall phase. or set Uninstall options to "Force removal even if values has changed" and add a script in Uninstall phase to delete only default values of the keys and let the uninstaller to remove the keys. Sequence->Uninstall->Add Action->General->Execute Script/Batch file. To get Uninstall log, enable logging as belows: In InstallAnywhere designer->Project-> General Setting-> Enable Logging -> select yes Select install checkbox & uninstall checkbox The log file will be found in the <InstallDir>/Logs folder after install/uninstall. ... View more

Yes, it will also require user action. In Console mode, all panels in pre/post-install sequence require user action to proceed. Important Note & Display message panels will also require user action. This is as per design in console mode installation. ... View more

In  Console mode installation, panels in post-install phase are designed to accept user action , whether to continue or exit. As a workaround  : If it is a simple installer with only Install complete panels in the post-install phase, To disable the status message & the "PRESS <ENTER> TO EXIT THE INSTALLER:" message in Console installer mode & let it finish automatically, Remove the Install Complete Panel found in Post-install sequence. InstallAnywhere Designer->Sequence->Post-Install->Action Group: Console actions-> Select panel "Console : Install Complete : Installation Complete" -> Remove ... View more

Log file path entry is appearing as log is enabled for the installation. Can hide this by either setting logging to off General Settings->Enable Logging->No or Keeping logging ON & setting InstallAnywhere Designer->Project->General Settings-> Log Settings->Include Debug output(stderr & stdout) ->Yes The log entry  along with other standard messages will now be written to the log file  and   it wont be shown in the console. ... View more

Silent installation does not accept any User Input. In silent installation this can be achieved by setting an Installer Rule & passing values as command line arguments. 1. Add an Installer Rule InstallAnywhere Designer->Project->Installer Rules-> Add Rule->Compare InstallAnywhere Variables set Operand 1- $PASSWORD_1$ select "equals" Operand 2- $PASSWORD_2$ 2. Run Silent installation as follows: <installerName> -i silent -DVariable1=value1 -DVariable2=value2 Eg: install.exe -i silent -DPASSWORD_1=password1 -DPASSWORD_2=password2 Result: Only if values passed to $PASSWORD_1$ and $PASSWORD_2$ are same installation happens. ... View more

This can be achieved using "Add Jump Label" & "Jump to Target" actions found in Install & Post Install Sequence. Add a Jump Label Action just before Panel3. Name it, for Example, "JumpPanel3". Add a "Jump to Target" action after Panel 1 & Set the Next Jump action as JumpPanel3 & add a rule to this action checking the selection status of the Checkbox. Below are the  steps for the sample , where I am using Get User Input- simple panel (Panel 1) to capture the user input of the checkbox. 1.    Add a Get User Input - Simple Panel (Panel 1) from        InstallAnywhere Designer->Sequence->Pre-Install->Add Action->Panels 2.    In Get User Input Panel change Input Method to "CheckBoxes" 3.    Set Results Variable as $USER_INPUT_1$ 4.    Select Configure Button and Select "Add" 5.    Give Label: CheckBox_1         Default Value: Not Selected 6.    Add Panel 2 7.    Add Panel 3 8.     Add a "Add Jump Label" Action (NOTE : Add this just ABOVE Panel 3)         from InstallAnywhere Designer->Sequence->Pre-Install->Add Action->         General->Add Jump Label 9.    Enter Label as "JumpToPanel3" and add a description 10.    Add "Jump To Target" Action           (Note : Add this Just AFTER Get User Input Panel or Panel 1)           from InstallAnywhere Designer->Sequence->Pre-Install           ->Add Action->General->Jump to Target 11.    In the action, For Next Jump Action choose Jump Label "JumpToPanel3". 12.    In the same action, Select Rules tab -> Add Rule           --> Compare InstallAnywhere Variables          Enter Operand1 - $USER_INPUT_1$          Select "equals" from the Drop down          Enter Operand2 - "CheckBox_1" (not to miss double quotes) Result will be : If Checkbox is Selected will move to Panel 3 directly from Panel 1 If Checkbox is not Selected will move to Panel 2 Hope this example helps. ... View more

Hi Bhuvana, Will it be possible to share the log file? To generate the log file: In InstallAnywhere designer->Project-> General Setting-> Enable Logging -> select yes Select install checkbox Select uninstall checkbox Include Debug output(stderr & stdout) - select yes In Project->JVM Settings-> Installer Settings -> Additional Argument -> enter -Dlax.debug.level=4 -Dlax.debug.all=true Share the log file generated in Logs folder after the silent installation.   ... View more

Hi Bhuvana, Your installer is running in GUI mode. The popups can be avoided with silent mode installation. What error you are getting when you try setup.exe -i silent?  Can you please share the screenshot of the error displayed? You were able to enable silent mode in   InstallAnywhere designer->Installer UI ->Look & Feel Settings-> General UI Settings->Allowable UI Modes?   ... View more