This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
JayantIyer
Flexera Alumni
- Revenera Community
- :
- About JayantIyer
Feb 08, 2021
04:54 AM
Summary
While performing a binary scan to a build output, experienced Zlib 1.2.3 version vulnerability in InstallShield 2018 R2.
Symptoms
While scanning with FlexNet Code Insight for the InstallShield generated executables as part of cybersecurity compliance, InstallShield received a vulnerability of Zlib 1.2.3 version.
Even with an empty Basic MSI installer, experienced Zlib 1.2.3 version vulnerability in InstallShield 2018 R2 .
Resolution
Engineering has released a hotfix that resolves this issue by removing the old Zlib version 1.2.3.
Currently, there are no files marked as vulnerable and the latest version Zlib 1.2.11 has been merged to InstallShield.
Additional Information
Below is the download link for the Zlib Patch of InstallShield 2018:
https://flexerasoftware.flexnetoperations.com/control/inst/AnonymousDownload?dkey=14557347
... View more
Oct 23, 2019
05:19 AM
Advanced UI and Suite/Advanced UI installations are bootstrap applications that package together installations and InstallShield prerequisites as a single installation while providing a unified, fully customizable user interface. They use a setup launcher (Setup.exe) to conditionally launch packages on target systems as needed.
You can add msi/ism/pre-requisite as package to your main Suite application.
Say the added msi has minor upgrade to get installed. Wondering why it is not working by default, here is the solution:
Add the required msi package to your package with the required settings
On clicking Package, you would be able to see a list of package settings
There will be an option called Minor Upgrade Handling which will be set to None by default
You can set the same to Automatic if you want minor updates to happen if configured
It can also be set to Ask the User if you want user to select this handling.
... View more
Labels:
Oct 23, 2019
02:31 AM
Symptoms:
Vulnerabilities CVE-2016-9843, CVE-2016-9842, CVE-2016-9841, CVE-2016-9840 are generically flagged against version 1.2.8 and less of zlib. Although there is no specific tagging of zlib version 1.2.3, InstallShield has proactively upgraded the version of zlib used from 1.2.3 to 1.2.11 to avoid generic vulnerability flagging.
Diagnosis:
A few binary scans show vulnerabilities associated with a different version of zlib (Ex 1.2.2 or 1.2.8) against compressed bootstrappers(setup.exe) built out of InstallShield 2018 R2. The results are confusing since the vulnerabilities are not for version 1.2.3 and yet appear in security scans causing customers to be concerned.
Solution:
This issue is being tracked under issue #IOJ-1900586. Engineering has released a hotfix that avoids generic vulnerability flagging by upgrading the version of Zlib to 1.2.11 which has no known vulnerabilities at the time of writing this article.
Additional Information:
Below is the download link for the zlib Patch of InstallShield 2018 R2:
https://flexerasoftware.flexnetoperations.com/control/inst/AnonymousDownload?dkey=14557347
... View more
Labels:
Jul 22, 2019
06:58 AM
Summary
InstallShield fails to create Patch/Upgrade from a compressed setup.exe built in InstallShield 2019.
Symptoms
Building a Patch Installer from a compressed setup.exe.
Building a Major/Minor Upgrade from a compressed setup.exe.
Building a Quick Patch Installer from a compressed setup.exe.
Cause
InstallShield fails to create Patch/Upgrade from a compressed setup.exe built in InstallShield 2019.
Workaround
When you try to create a Patch Installer or Upgrades from a compressed setup.exe, you can manually extract MSI from setup.exe instead of allowing InstallShield extract the content. Now use the extracted MSI in your Patch Installer or Upgrades instead of the compressed setup.exe.
Use the following command to extract MSI from a compressed setup.exe in the current directory.
setup.exe /s /x /b"." /v"/qn"
... View more
Labels:
Jul 02, 2019
04:20 AM
Summary
It is always a best practice for an installer to check for a dependent software, so that the installer can alert the end-user to install prior to the main installation.
InstallShield has Project Assistant to guide you on the same. It is under the section - “Installation Requirement”.
Project Assistant’s installation requirement has two parts:
One for the operating system
Second one for the software requirement
This article talks about the software requirement.
By default, InstallShield has certain number of software entries in the section, say you want to add a new one.
Discussion
Let us see how to add in the detailed section below:
Adding an entry to this section is handled by a configuration file(.ini) which you can view under <InstallShield Installed Path>\<InstallShield Version>\Searches
The Configuration file details are given below:
1. Create a new configuration file named Eg: SQLSERVEREXPRESS2017.ini.
2. Take any existing configuration file as a template from the Searches folder.
Configuration file contains the following sections:
[Title0409]
Name-Display string you want to name, the same will be displayed in Installation requirement section
Type-Type of check you would like to do, most commonly it would be registry
Description-Describes in detail about what the specific requirement does
3. On supporting German & Japanese, you can add [Tile0407],[Title0411]
4. [AppSearch]- The AppSearch table contains properties needed to search for a file which has a particular file signature. The AppSearch table can also be used to set a property to the existing value of a registry or .ini file entry.
Signature-Name of the signature to use for an application search
Property-Property to be set if the application is found
5. [RegLocator]-The RegLocator table holds the information needed to search for a file or directory using the registry, or to search for a particular registry entry itself. This table has the following columns.
6. [Reg Entry]-
Signature_=Signature name of the file to be used for search
Root-The predefined root key for the registry value.
Constant
HexaDecimal
Decimal
RootKey
msidbRegistryRootClassesRoot
0x000
0
HKEY_CLASSES_ROOT
msidbRegistryRootCurrentUser
0x001
1
HKEY_CURRENT_USER
msidbRegistryRootLocalMachine
0x002
2
HKEY_LOCAL_MACHINE
msidbRegistryRootUsers
0x003
3
HKEY_USER
Key-The key for the registry value.
Name-The registry value name. If this value is null, then the value from the key's unnamed or default value, if any, is retrieved.
Type-A value that determines if the registry value is a file name, a directory location, or raw registry value.
Constant
Hexadecimal
Decimal
Description
msidbLocatorTypeDirectory
0x000
0
Key path is a directory.
msidbLocatorTypeFileName
0x001
1
Key path is a file name.
msidbLocatorTypeRawValue
0x002
2
Key path is a registry value.
msidbLocatorType64bit
0x010
16
Set this bit to have the installer search the 64-bit portion of the registry. Do not set this bit to have the installer search the 32-bit portion of the registry.
7. [ExpressCondition0409]-Condition to validate the existence of file in the machine
Name=Display name of the condition to be added
Condition=Condition to validate based the property and value
Message=Message to be displayed on failing to satisfy the condition
8. On supporting German, Japanese you can add [ExpressCondition0407],[ExpressCondition0411]
Let us take an example of SQLServerExpress2017 as an installation requirement to be added to the installer: [Title0409] Name=SQL Server 2017 Express Type=Registry Desc=Look for the existence of SQL Server 2017 Express on a system and sets the version of SQL Server Express 2017 as the value of the property SQLEXP2017FOUND. [AppSearch] Signature_=NewRegSignature Property=SQLEXP2017FOUND [RegLocator] Records=Reg1 [Reg1] Signature_=NewRegSignature Root=2(Here value stands for msidbRegistryRootLocalMachine) Key=SOFTWARE\Microsoft\Microsoft SQL Server\SQLEXPRESS\MSSQLServer\CurrentVersion Name=CurrentVersion Type=2(Here the value stands for msidbLocatorTypeRawValue) [ExpressCondition0409] Name=SQL Server 2017 Express is Installed Condition=SQLEXP2017FOUND>="14.0.1000.169"(These conditions you can retrieve after installation of the dependent software in registry) Message=SQL Server 2017 Express needs to be installed for this installation to continue.
... View more
Labels:
Jul 02, 2019
04:19 AM
Summary
There are many scenarios where we might need to handle navigation controls like button, click or visibility based on checkbox state in Suite wizard pages.
In this article, let us see two scenarios in Suite wizard pages in detail:
Controlling visibility of navigation control using checkbox state
Handling navigation control click based on checkbox state
Discussion
Controlling Visibility of Navigation Control using Checkbox state
Let us take a real-time scenario:
Install Welcome Suite wizard which has the License Terms and Conditions Agree checkbox, based on the selection of the checkbox, the Next button should be enabled/disabled.
How can we achieve this?
1. Create a new property say “IsLicenseAgreed” in the property manager and assign the value to false by default
2. Add a new checkbox in the Install Welcome wizard-page and fill the Property field with: ISLicenseAgreed==true
3. Set the Next button’s Enabled field’s condition property as IsLicenseAgreed Is Equal To True
4. Build the project by adding the required packages.
When you launch, the results will be displayed.
Handling Navigation Control Click based on Checkbox state
Another useful scenario we package using InstallShield-Suite project would be launching the main application on a successful installation of the software.
Just like the previous scenario, it can be achieved in the similar way. However, we might need to set an additional Click Property of Navigation Control.
How can we achieve this?
1. Create a new property “IsLaunchProduct” in property manager and assign the value to True by default
2. Add a new checkbox in Install Success wizard and fill the property field with: ISLicenseAgreed==true
3. Fill the Click property of the Finish button with an open action:
Add an open action, mention the main application to be launched when the launch checkbox is checked
Fill the condition property as IsLaunchProduct Is Equal to true which is the checked state of the Launch checkbox.
4. Build the project by adding the required packages.
When you launch, the results will be displayed.
... View more
Labels:
Jun 06, 2019
01:40 AM
Summary
Error 9513 occurs while validating the MSIX/Appx manifest xml.
Symptoms
Building a release is when validating schema in [File Name ([Line number)].
Cause
This build error may be caused while validating the MSIX/Appx manifest xml against the schema files.
Workaround
To workaround the issue at this point,
Refer https://docs.microsoft.com/en-us/uwp/schemas/ to compose the manifest entries, like the mandatory and supported values.
You are required to correct the values in the corresponding views in the MSIX project.
For example, recheck the values specified for the added declaration and check whether the values are as per the schema or not.
... View more
Labels:
Jun 06, 2019
01:39 AM
Summary
Error 9570 occurs while setting the Background Tasks declaration.
Symptoms
Building a release requires to select at least one supported task type for the Background Tasks declaration.
Cause
This build error may be caused because the Background Tasks declaration requires to select at least one supported task.
Workaround
To workaround the issue at this point,
Add a Supported Task in the Background Tasks declaration from the Declaration view.
... View more
Labels:
Jun 06, 2019
01:38 AM
Summary
Error 9571 occurs while setting the Wide Tile Image for the Visual Asset.
Symptoms
Building a release requires to set the Wide Tile Image for the Visual Asset: ‘%1’.
Cause
This build error may be caused when the Wide Tile Image is missing for the Visual Asset.
Workaround
To workaround the issue at this point, if the Large Tile Image is specified in the Visual Asset in order to install the package,
Specify the Wide Tile Image
... View more
Labels:
Jun 06, 2019
01:38 AM
Summary
Error 9568 occurs while setting the Web Account Provider declaration.
Symptoms
Building a release is managed URL ‘%1’ specified is a duplicate of the base URL specified for the Web Account Provider Declaration.
Cause
This build error may be caused by one of the Managed URL which is a duplicate with the base URL specified for the Web Account Provider Declaration.
Workaround
To workaround the issue at this point,
Specify a unique Managed URL in the Web Account Provider Declaration.
... View more
Labels:
Jun 06, 2019
01:37 AM
Summary
Error 9569 occurs while setting the Shared Target declaration.
Symptoms
Building a release requires at least one supported File type or Data format.
Cause
This build error may be caused by Share Target Declaration which requires to specify at least one supported File type or Data.
Workaround
To workaround the issue at this point,
Select 'Supports any File type' or explicitly to add one or more File types or Data formats in the Share Target Declaration.
... View more
Labels:
Jun 06, 2019
01:36 AM
Summary
Error 9567 occurs while setting the Appointments Provider declaration.
Symptoms
Building a release is when the Start page ‘%1’ must not be specified if the 'Entry point', 'Executable' or 'Runtime type' is specified in Appointments Provider Declaration.
Cause
This build error may be caused by the 'Entry point', 'Executable' or 'Runtime type' cannot be specified if the ‘Start page’ is specified in the Appointments Provider Declaration Launch Action.
Workaround
To workaround the issue at this point,
Specify either ‘Entry point’ or ‘Start page’ entries in the Launch Action.
... View more
Labels:
Jun 06, 2019
01:27 AM
Summary
Error 9564 occurs when the module [COM Module Name] contains the COM data.
Symptoms
Building a release is when this COM server will not be activatable outside the Appx package.
Cause
This build error may be caused by a specified COM server that will not be activatable outside of this Appx package as all its registry entries and extension points are in its private hive and not exposed publicly to the system.
Workaround
To workaround the issue at this point, if your application uses COM only for its own personal use, then you can ignore this warning and rely on COM entries in the application’s private hive (Registry.dat) to support your app.
All binaries in the same appx\msix package have access to that registry, but any other apps on the system cannot see into your app’s private hive.
... View more
Labels:
Jun 06, 2019
01:24 AM
Summary
Error 9566 occurs while setting a declaration.
Symptoms
Building a release is when the executable ‘%1’ defined for declaration element does not exist in the package.
Cause
This build error may be caused by the custom executable specified for the declaration is not found in the package.
Workaround
To workaround the issue at this point,
Redefine with the correct executable or add the executable to the package.
... View more
Labels:
Jun 06, 2019
01:23 AM
Summary
Error 9565 occurs when the target executable 'Application Name' requires elevation when launching the application.
Symptoms
Building a release is when the Desktop Bridge does not support packaged executables that require administrator/elevated privileges.
Cause
This build error may be caused if your application specifies:
UIAccess=true or level="highestAvailable|requireAdministrator"
in the requestedExecutionLevel element of the UAC manifest, conversion to UWP isn't supported currently.
Setting the below capability flag in the package manifest will allow your application to request for elevation.
<rescap:Capability Name="allowElevation"/>.
Workaround
To workaround the issue at this point, you will need to set a flag.
Go to the ‘ISVirtualPackage’ table in the InstallShield ‘Direct Editor’ view
Create the below entry.
Use space as delimiter to specify multiple capabilities.
Name: AppxCapabilityList
Value: rescap:allowElevation
... View more
Labels:
Latest posts by JayantIyer
Subject | Views | Posted |
---|---|---|
908 | Feb 08, 2021 04:54 AM | |
989 | Oct 23, 2019 05:19 AM | |
2449 | Oct 23, 2019 02:31 AM | |
1085 | Jul 22, 2019 06:58 AM | |
1723 | Jul 02, 2019 04:20 AM | |
1685 | Jul 02, 2019 04:19 AM | |
2227 | Jun 06, 2019 01:40 AM | |
746 | Jun 06, 2019 01:39 AM | |
599 | Jun 06, 2019 01:38 AM | |
649 | Jun 06, 2019 01:38 AM |
Activity Feed
- Posted HOTFIX: Zlib 1.2.3 version vulnerability in InstallShield 2018 on InstallShield Knowledge Base. Feb 08, 2021 04:54 AM
- Posted How to enable minor upgrade in Suite/Advanced UI MSI packages? on InstallShield Knowledge Base. Oct 23, 2019 05:19 AM
- Posted HOTFIX: Vulnerabilities in installers created from InstallShield 2018 R2 due to zlib 1.2.3 on InstallShield Knowledge Base. Oct 23, 2019 02:31 AM
- Posted InstallShield fails to create Patch/Upgrade from a compressed setup.exe on InstallShield Knowledge Base. Jul 22, 2019 06:58 AM
- Posted How do I add a Software under Installation Requirement section of Project Assistant? on InstallShield Knowledge Base. Jul 02, 2019 04:20 AM
- Posted How to handle Navigation Controls using Checkbox property in Suite wizard pages? on InstallShield Knowledge Base. Jul 02, 2019 04:19 AM
- Posted Build Error 9513 on InstallShield Knowledge Base. Jun 06, 2019 01:40 AM
- Posted Build Error 9570 on InstallShield Knowledge Base. Jun 06, 2019 01:39 AM
- Posted Build Error 9571 on InstallShield Knowledge Base. Jun 06, 2019 01:38 AM
- Posted Build Error 9568 on InstallShield Knowledge Base. Jun 06, 2019 01:38 AM
- Posted Build Error 9569 on InstallShield Knowledge Base. Jun 06, 2019 01:37 AM
- Posted Build Error 9567 on InstallShield Knowledge Base. Jun 06, 2019 01:36 AM
- Posted Build Error 9564 on InstallShield Knowledge Base. Jun 06, 2019 01:27 AM
- Posted Build Error 9566 on InstallShield Knowledge Base. Jun 06, 2019 01:24 AM
- Posted Build Error 9565 on InstallShield Knowledge Base. Jun 06, 2019 01:23 AM
- Posted Build Error 9563 on InstallShield Knowledge Base. Jun 06, 2019 12:59 AM
- Posted Build Error 9562 on InstallShield Knowledge Base. Jun 06, 2019 12:58 AM
- Posted Build Error 9561 on InstallShield Knowledge Base. Jun 06, 2019 12:58 AM
- Posted Build Error 9560 on InstallShield Knowledge Base. Jun 06, 2019 12:57 AM
- Posted Build Error 9559 on InstallShield Knowledge Base. Jun 06, 2019 12:56 AM
Contact Me
Online Status |
Offline
|
Date Last Visited |
Oct 31, 2019
08:59 AM
|