InstallShield Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 
Knowledge Base Categories
Summary Build Warning -7235 Synopsis When building an InstallShield Express project, the following warning may occur: ISEXP : warning -7235: InstallShield could not create the software identification tag because the Tag Creator ID setting in the General Information view is empty. Discussion By default, software identification tagging is enabled in all Express projects. This applies to new projects created with InstallShield Express, as well as projects that were upgraded from earlier versions of the InstallShield Express Edition.   If you build a release in an Express project without entering data in the required software identification tag setting (the Unique ID, Tag Creator, and Tag Creator ID settings in the General Information view), and you leave software tagging enabled in the project, the build warning -7235 occurs. This build warning explains that the software identification tag could not be created and included in the installation because a specific required setting was left blank. To resolve this warning, enter an appropriate value in each specific setting, or set the 'Use Software Identification Tag' setting in the General Information view to 'No'.   Related Documents Including a Software Identification Tag for Your Product http://helpnet.flexerasoftware.com/isxhelp23/isxhelp23.htm#helplibrary/SWIDOverview.htm
View full article
Summary Error 9510 occurs while building the Windows Installer package. Symptoms Building a release is when you are building Windows Installer package. Cause This build error may be caused if a latest image in the Patch Design view does not have at least one previous image. Workaround To workaround the issue at this point, A latest image must have at least one previous image to create a patch.
View full article
Summary Error 9512 occurs while building the MSIX package. Symptoms Building a release is when you are unable to add file [File Name] to package. Cause This build error may be caused while adding the specified file to the MSIX package. Workaround To workaround the issue at this point, The specified file should exist on the system and there is enough disk space available.
View full article
Summary Error 9552 occurs while building the MSIX package. Symptoms Building a release is when an unexpected error displays MSIX App file entry. Cause This build error may be caused while adding payload file/folder to the MSIX package. Workaround To workaround the issue at this point, Check whether the source files exist in the system during the build.
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
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 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 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 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 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 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 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 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 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 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 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 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 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