Suite Installer MSI Package is Not Found When Installing New Features via the Windows Control Panel

Title

Summary

When installing new features via Control Panel the following message is diaslayed. "The package that you are trying to install requires a file that is not available. To continue, specify an alternate path to this file: "

Symptoms

For a Suite installation that has multiple MSI Packages and each Package is associated with a separate Feature, if during the initial install, a Custom Type install is performed where not all Features are installed, when the installation is run a subsequent time from the Windows Control Panel to install additional Features, the following error is thrown:

The package that you are trying to install requires a file that is not available. To continue, specify an alternate path to this file: <name of package>

The MSI installation package is not cached to the [LocalAppDataFolder]Downloaded Installations folder.

Cause

This behavior occurs because in the Suite project, the packages are set to Copy from Source Media. When maintenance is launched from the Windows Add and Remove Programs Control Panel rather than from the original setup location, the Suite engine does not know where the installation Source Media is located. Therefore, the end user is prompted to specify the location of the required installation files.

Steps To Reproduce

This behavior can be reproduced by performing the following steps:

Create a new Suite project
Add two Features, FeatureA and FeatureB
Add two MSI type packages, associating the first MSI package to FeatureA and the second MSI package to FeatureB
Build a release of the Suite project
Perform an installation of the Suite package, select a Custom type install and only select FeatureA
After the installation completes, select Change from the Windows Program Control Panel to run the Suite setup in maintenance mode.
Select FeatureB for installation

Resolution

This behavior can be modified by editing the Suite project and changing the Package's Location setting to Extract From Setup.exe or Download From The Web. With these options, a prompt for the installation source is not required, as the files are either streamed into the running setup or downloaded from a specified URL.

Note the option selected in the Package's Location setting may be overridden in the Suite project's Releases view.

Workaround

Instead of invoking the maintenance from the Windows Control Panel, execute the Suite Setup Launcher from the original installation media.

Additional Information

This behavior is being tracked internally with issue number IOA-000073466.

Was this helpful?

Support Hub

Product

InstallShield

Visibility

Guest

URL Name

suite-installer-msi-package-is-not-found-when-installing-new-features-via-the-windows-control-panel

Are you sure you want to cancel the case creation?

Case closed successfully

Action performed successfully

Upload Attachment

Maximum file size allowed is 3 MB.

File type not supported.

Supported file types:

Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files (.csv) Speadsheets (.xlsx, .xls)

Are you sure you want to close this case

Get Hotline support

Products	Region	Phone Numbers
FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield	North America *	+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America)
	Europe *	+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe)
	Japan *	+81 3-4540-5335 (select option 2)
	Australia *	+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia)
Usage Intelligence (formerly Revulytics) Compliance Intelligence	Please use the Case Portal to submit your support ticket or reach out to your Revenera contact.