InstallShield Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 
Knowledge Base Categories
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 full article
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 full article
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 full article
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 full article
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 full article
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 full article
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 full article
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 full article
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 full article
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 full article
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 full article
Summary Error 9563 occurs from the Dependency Package Name. Symptoms Building a release could not merge registry data from dependency [Dependency Package Name]. Cause This build error may be caused while merging registry data as the specified dependency package fails while extracting registry.dat file. Workaround Not available.
View full article
Summary Error 9562 occurs while building the MSIX/Appx package. Symptoms Building a release could not merge files from dependency [Dependency Package Name]. Cause This build error may be caused while merging the dependency package to building MSIX/Appx package. Workaround To workaround the issue at this point, Check whether the dependency package specified exists in the source location as well as for valid packages.
View full article
Summary Error 9561 occurs while setting the NT Service Name. Symptoms Building a release is when the NT Service [Service Name] is set to start in an unsupported way. Cause This build error may be caused when the added service doesn't have valid start type. Workaround To workaround the issue at this point, check the service you added. Any service should always have the proper properties like Path, Startup Account, Type, Error Control, Start Type, etc.
View full article
Summary Error 9560 occurs while setting the NT Service Name. Symptoms Building a release when the NT service [Service Name] uses an unsupported startup user action error control option (SERVICE_ERROR_CRITICAL) Cause This build error may be caused is when the added service doesn't have proper error control which can be either NORMAL or IGNORE type. Workaround To workaround the issue at this point, check the service you added. Any service should always have the proper properties like Path, Startup Account, Type, Error Control, Start Type, etc.
View full article
Summary Error 9559 occurs while setting the NT Service Name. Symptoms Building a release is when the NT service [Service Name] uses an unsupported startup account [Account], skips this service since no appropriate default account is available. Cause This build error may be caused when the added service doesn't have a startup account which may come as any one of the below: LocalSystem NetworkService LocalService Workaround To workaround the issue at this point, check the service you added. Any service should always have the proper properties like Path, Startup Account, Type, Error Control, Start Type, etc.
View full article
Summary Error 9558 occurs when the Server Extension is not included while building the UWP app package. Symptoms Building a release is when this MSI includes [Count of service] NT services. But, the built UWP app package will not include them as the package does not include the Server target. Cause This build error may be caused is when the MSI has NT services enabled, but the UWP app package doesn't have the server target support enabled. Workaround To workaround the issue at this point, Enable the server extensions and further update to its version details in Releases->Release-Name->APPX/MSIX->Include Server Extension
View full article
Summary Error 9557 occurs while creating resources.pri. Symptoms Building a release is when you are unable to create resources.pri. Without resources.pri, the scaled logos cannot be used. Cause This build error may be caused by unavailability of Windows 10 SDK. Workaround To workaround the issue at this point, Check whether Windows 10 SDK is installed in the system, if not, install Window 10 SDK.
View full article
Summary Error 9556 occurs while building the package. Symptoms Building a release is when you are unable to locate the Windows 10 SDK. Cause This build error may be caused by unavailability of Windows 10 SDK. Workaround To workaround the issue at this point, Check whether Windows 10 SDK is installed in the system, if not, install Window 10 SDK.
View full article
Summary Error 9553 occurs when while building the MSIX app package. Symptoms Building a release is when the file type association for extension [extension] does not contain any 'open' verbs but does contain other verbs. Cause This build error may be caused by an open verb that is included as MSIX app packages force at least open to be supported. Workaround To workaround the issue at this point, Add and 'open' verb in the File Association.
View full article