Summary: This article shows how to Configure External resource Bundle for custom locale files.   Steps to configure Resource Bundle:   1. Create Custom locale file which you want to add it in the External resource bundle. Naming Conventions: <bundle>_<language_code>.properties File Format: InstallSet.installSetName=Custom InstallSet.description=Choose this option to customize the features to be installed. 2. Create New Project, 3. Click on Locales and External Resource Bundle Bundle Name : Test Bundle Resource Bundle path : The custom locale properties file which you want to include. 4. Build and run the Project. 5. If you want to display or print the value of the key which is in the custom locale properties file, then you can add it in any of the panel, Generally external resource bundle contains a properties file for each locale.   ... View more

Summary: This article shows how to find and kill the running process before Uninstall Steps : 1. Create New Project 2. Goto Sequence and click Pre-Uninstall 3. Add Execute script/Batch file custom action query process script/command to find the process, 4. To Make sure the process details add the show message dialog with this $EXECUTE_STDOUT$ 5. Add the Execute Script/Batch file custom action to kill the process with name/PID 6. Build and run the project. 7. Here is the successful outputs of Find and kill process,   ... View more

Summary: This article will helps you to understand configuration of Install Speedfolder Include and Exclude Folders/Files. Steps: 1. Create New Project. 2. Goto Install sequence and add Install Speedfolder action then add the folder which contains the folder/files which you want to exclude/include. 3. Include : In this example the folder/file name starts with New are Included, After Install : 4. Exclude: In this Example the Folder name starts with My are excluded, After Install: More Info: https://docs.revenera.com/installanywhere2021/Content/helplibrary/ia_ref_actions_installspeed.htm ... View more

Summary: This article shows How to launch executable/browser/URL. Steps to Configure launch Executable: 1. Create New Project. 2. In Install sequence click add file to add the exe which you want to launch. 3. In Post Install sequence Click Add Action to add launch default browser. 4. In Properties customizer, Installed File : Choose the exe which you added in the Install sequence. 5. Goto Build Target choose the OS and the VM which you want to. 6. Build and run the Installer. 7. After Install it will launch the link. Steps to Configure URL/Browser: 1. Create New Project. 2. In Post Install sequence Click Add Action to add launch default browser. 3. In Properties customizer, Other URL : add the URL which want to launch. 4. Goto Build Target choose the OS and the VM which you want to. 5. Build and run the Installer. 6. After Install it will launch the exe. ... View more

  Symptoms: When tried to start mvsn manually using the below command that is also giving error as "No such file or directory". But the file is present in the directory. FNPLicenseServerManager# ./lmgrd -c /opt/FNPLicenseServerManager/licenses/license.lic (lmgrd) (@lmgrd-SLOG@) === Network Info === (lmgrd) (@lmgrd-SLOG@) Listening port: 27000 (lmgrd) (@lmgrd-SLOG@) (lmgrd) (@lmgrd-SLOG@) === Startup Info === (lmgrd) (@lmgrd-SLOG@) Server Configuration: Single Server (lmgrd) (@lmgrd-SLOG@) Command-line options used at LS startup: -c /opt/FNPLicenseServerManager/licenses/license.lic (lmgrd) (@lmgrd-SLOG@) License file(s) used: /opt/FNPLicenseServerManager/licenses/license.lic (lmgrd) (@lmgrd-SLOG@) =============================================== (lmgrd) Starting vendor daemons ... (lmgrd) Started mvsn (internet tcp_port 59453 pid 21623) (lmgrd) license daemon: execute process failed: (./mvsn) -T cop 15.12 2 -c :/opt/FNPLicenseServerManager/licenses/license.lic: (lmgrd) license daemon: system error code: No such file or directory (lmgrd) mvsn exited with status 45 (Child cannot exec requested server) (lmgrd) Please correct problem and restart daemons Diagnosis: The version of lmgrd should match that of the mvsn vendor daemon. If you are running 64 bit lmgrd and 32 bit mvsn on 64 bit machine, it will throw no such file or directory. Solution: You need to run the same version of lmgrd and the mvsn vendor daemon to avoid the no such file or directory error. If you are running 64 bit lmgrd and the mvsn version also 64 bit. If you are using 32bit lmgrd then the msvn version also 32bit. Also to run 32 bit version of lmgrd and mvsn on a 64 bit Ubuntu machine, need to use the following command sudo apt update sudo dpkg --add-architecture i386 sudo apt update sudo apt install libc6:i386 libstdc++6:i386 libncurses5:i386 zlib1g:i386 sudo ln -s /lib/i386-linux-gnu/ld-linux.so.2 ld-lsb.so.3   ... View more

Introduction:  This article will show to how to configure an Installer to install only if the user has sudo access else abort the Installation. Instructions: 1. Create a new project. 2. Goto Sequence and Pre-install Sequence, Add Execute Script/Batch file action and then add the following command to check whether the user has the sudo access or not, groups username. Note: If you see the group ‘sudo’ in the output, the user is a member of the sudo group and it should have sudo access. 3. Add a Panel: Display message to display $EXECUTE_STDOUT$ which hold the result of groups username command. 4. Add a rule to display message panel only if Operand 1 : $EXECUTE_STDOUT$ does not contain Operand 2: sudo 5. Add Abort Installation plug-in to abort the installation with a rule of Operand 1 : $EXECUTE_STDOUT$ does not contain Operand 2: sudo To use the Plug-in "AbortInstallAction", please download from this link https://www.revenera.com/install/products/installanywhere/installanywhere-files-utilities and add AbortInstallActionCustomCode.jar in [InstallAnywhere Folder]\plugins. Learn more: https://www.revenera.com/install/products/installanywhere/installanywhere-files-utilities ... View more

Introduction: This article will be useful to know the option available in configuration settings with respect to uninstallation in GUI mode, If the executable is Installed in silent mode(without GUI),Uninstallation wizard does not have GUI mode. Solution: If the product is installed silently, we'd like the uninstaller to run in GUI mode by default (if it's double clicked or launched without any arguments), In order to do this: 1. Create a new project. 2. Installer UI > Look & Feel Settings > General UI Settings > Allowable UI Modes = Select both "GUI" and "Silent" 3. Project > Platforms > Windows > Default Windows UI Mode = Set both Installer UI Mode and Uninstaller UI Mode to "GUI" 4. Project > Platforms > Unix > Default Unix Installer UI Mode = Set both Installer UI Mode and Uninstaller UI Mode to "GUI" 5. Build the project. Outcome:If you run the installer silently then launch the uninstaller without any arguments, the uninstaller will default to running in GUI mode. If you run the uninstaller with the "-i silent" command line switch, the uninstaller will run silently. ... View more

Summary: This Article helps you to understand What does the Free and Total memory which is captured in the Log actually means? ================== Wed Jan 11 02:50:05 GMT-05:00 2023 Free Memory: 5441 kB Total Memory: 44032 kB ================== Discussion: Free memory means, Free memory of JVM. public long freeMemory() Returns the amount of free memory in the Java Virtual Machine. Calling the gc method may result in increasing the value returned by freeMemory. Returns: an approximation to the total amount of memory currently available for future allocated objects, measured in bytes.   Total memory means, total amount of memory in the Java virtual machine. The value comes from a call to Runtime.totalMemory() public long totalMemory() Returns the total amount of memory in the Java virtual machine. The value returned by this method may vary over time, depending on the host environment. Note that the amount of memory required to hold an object of any given type may be implementation-dependent. Returns: the total amount of memory currently available for current and future objects, measured in bytes. ... View more

Summary: This article shows how to Change Installer name at build time in InstallAnywhere. Steps to Change Installer Name: 1. Create New project. 2. Click on Variables and  click Build Time Variables and then Edit variables,  add Build time variable : @IA_BTV_INSTALLER_NAME@ and value as Avengers. 3. Goto General Settings then set the Installer name as @IA_BTV_INSTALLER_NAME@     4. Build and run. 5. After the change, ... View more

  Summary : Installers built on InstallAnywhere 2020 are not supporting Windows 2022 Symptoms : Installers built on InstallAnywhere 2020 Throws 'Fatal Application Error' in Windows server 2022 Error Messages: Flexerafgh$: Windows DLL failed to load at Flexeraaxd.af(Unknown Source) at Flexeraaxd.aa(Unknown Source) at com.zerog.ia.installer.LifeCycleManager.init(Unknown Source) at com.zerog.ia.installer.LifeCycleManager.executeApplication(Unknown Source) at com.zerog.ia.installer.Main.main(Unknown Source) Cause: The 'Fatal Application Error' in IA2020 is due to unsupported OS Solution: Support for Windows Server 2022 was introduced in IA 2021 SP1: https://docs.revenera.com/installanywhere2021sp1/rn/Content/helplibrary/Support_for_Windows_Server_2022.htm#installanywhere2021sp1_releasenotes_2891729388_1078561 The 'Fatal Application Error: Windows DLL Failed to load' would be generated if the installer was built using a version prior to IA 2021 SP1. Upgrading the project to at least IA 2021 SP1 and rebuild the installer will helps in resolving the issue.   ... View more

Summary: This article shows how to automate passing the license information to a silent install of the InstallShield Standalone Build (SAB). Resolution: Download the InstallShield Standalone Build. For example: InstallShield2021R2StandaloneBuild.exe Open an Administrator command prompt. Run the following command: InstallShield2021R2StandaloneBuild.exe /S /v/qn /VSERVERNAME=<IPADDRESS OR LICENSE_SERVER_NAME> /VPORTNUMBER=<LICENSE_SERVER_PORT> /VLICENSETYPE=2 /VADDLOCAL=ALL The following tasks will be completed and the install will be done silently without displaying any wizard: 1. Specifying of concurrent license options 2. Specifying of the license server name 3. Installing of all the features In the aforementioned command (see above): The value of 1 for the LICENSETYPE property indicates that you are using a node-locked license of the InstallShield SAB. The value of 2 for the LICENSETYPE property indicates that you are using a concurrent license of the InstallShield SAB. The value of 3 for the LICENSETYPE property indicates that you are using a Cloud License Server (CLS) concurrent license of the InstallShield SAB. Additional Information: Click here for the documentation about the command line parameters that the InstallShield SAB (ISCmdBld.exe) takes. ... View more

Summary: The driver package from the driver store is not removed during uninstall. Synopsis: This article will provide steps for removing the driver package from the driver store during uninstall. Discussion: 1. Set Permanent to No for the component to which the driver is associated. If Yes is selected, none of the component's data (such as files, registry entries, and shortcuts) are removed from the target system when the component's parent feature is uninstalled. As the name Permanent indicates, a component marked Permanent is permanent, meaning that it is not removed during uninstall. 2. For the component that contains the file or folder, right-click the file and click Add Removal. Make sure there is an entry created in the Direct Editor in the RemoveFile MSI Table. 3. Change the General Information > Template Summary to "x64;1033" (the value for a 64-bit installer). 4. On a 64-bit machine, [System64Folder] needs to be used to target the C:\Windows\System32 folder, because this is the 64-bit location. The C:\Windows\SysWOW64 folder is the 32-bit location for the System folder. Example: 1. Create a Basic MSI Project. 2. Add a feature and a component. 3. Set General Information > Template Summary to "x64;1033". 4. Go to the Property Manager and create a new property named "XXXXBUS" with a value of "C:\Windows\System32\xxxxbus". 5. Go to the RemoveFile MSI Table and add the following values: FileKey = Removexxxxbus, Component = xxxbus, FileName = xxxxbus.inf, DirProperty = XXXXBUS, InstallMode=3 6. Build the project. 7. Run the installer. 8. Go to the target machine and create the following folder: C:\Windows\System32\xxxxbus 9. Make sure that the xxxxbus.inf file is in the C:\Windows\System32\xxxxbus folder. 10. Run the installer on the target machine. 11. Run the uninstaller on the target machine. During uninstall the driver package will be removed from driver store at the following location: C:\Windows\System32\DriverStore\FileRepository ... View more

Summary: This article discusses how to launch / run an .exe file if the .exe file is found by using a System Search and how to force a restart / reboot of the machine. Resolution: 1. Create a Basic MSI Project. 2. Navigate to Behavior and Logic > System Search. 3. Add a File path, by searching folders System Search. 4. Click Next. 5. Enter the .exe filename and the full path, in the System Search Wizard, by finding the full path in File Explorer then specifying the same path in the wizard. The full path to the Notepad++ installer .exe file in File Explorer (C:\Windows): The System Search Wizard represents C:\Windows with [WindowsFolder]: 6. Specify the property to store the value of the search result in. 7. Navigate to the InstallScript View. 8. Create a Setup.rul file with the following InstallScript code: #include "ifx.h" export prototype Func1(HWND); function Func1(hMSI) STRING PropertyName; NUMBER nResponse,nvSize; begin nvSize=MAX_PATH; nResponse=MsiGetProperty (hMSI,"TEST",PropertyName,nvSize); MessageBox("PropertyName:"+PropertyName,INFORMATION); if (nResponse==0) then LaunchApp(WINDIR ^ "npp.8.3.3.Installer.x64.exe", ""); MessageBox(WINDIR^ "npp.8.3.3.Installer.x64.exe",INFORMATION); else MessageBox ("Setup will now exit.", INFORMATION); endif; end; 9. Add an InstallScript custom action. 10. Schedule the InstallScript custom action in the Execute Sequence (Install Exec Sequence) after the standard CostFinalize Action. 11. In the Property Manager, set a property named: REBOOT to a value of: Force 12. Build the project. 13. Run the installer. The Notepad++ installer will be launched if it is found in the Windows folder. Additional Information: Here is a link to the official Microsoft documentation about the standard CostFinalize Action: https://docs.microsoft.com/en-us/windows/win32/msi/costfinalize-action ... View more

Summary : This article explains how to use a powershell custom action to access an MSI property with deferred custom action. This information applies to the following InstallShield project types: Basic MSI InstallScript MSI Solution: 1. Create Basic MSI Project 2. Create powershell script file names shell.ps1 function Show-CustomActionData { param ($propertyName) $myProps = get-property -name $propertyName $myPropArray = $myProps.split(";") $ARPINSTALLLOCATION = $myPropArray[0] $INSTALLDIR = $myPropArray[1] $TEST = $myPropArray[2] #$wshell = New-Object -ComObject Wscript.Shell #$wshell.Popup("ARPINSTALLLOCATION: $ARPINSTALLLOCATION",0,"Property Value",0x1) #$wshell.Popup("INSTALLDIR: $INSTALLDIR",0,"Property Value",0x1) #$wshell.Popup("TEST: $TEST",0,"Property Value",0x1) "Test" | Out-File -FilePath C:\Test\testtest.txt $installdir | Out-File -FilePath C:\Test\testinstalldir.txt $user | Out-File -FilePath C:\Test\testuser.txt 3. Create feature called Power and add the shell.ps1 file 4. Create Custom Action(POWERCAS) and select the shell.ps1 file, Deferred Execution in system context and After SetCustomActionData. 5. Create SetCustomActionData and set the below, 6. Build and Run the project. 7. The file C:\Test\testinstalldir.txt is created with the expected Value. ... View more

Summary: Execution failed with exit code -2147213312 Synopsis : During a silent Installation the following error may be seen:  "Execution failed with exit code -2147213312" Discussion: This error has been seen to occur due to a corrupted or missing  .iss file. Resolution: We can pass /r switch, which should create the silent install response file and then use the –s swtich to look for the silent response file as system account needs a setup.iss (answer/response) file to write to / read from. Example: Setup.exe /r /f1”C:\temp\Install.iss” ... View more