InstallShield 2012 Spring Express Edition User Guide

Chapter 25: Errors and Warnings
Build Errors and Warnings
Table 25-2: Build Errors and Warnings (cont.)
Error Description Troubleshooting Tips
-6550 %1 is not a valid .NET assembly to
be installed to the Global Assembly
Cache (where %1 is replaced with a
full file path).
-6530 Error processing setup [1] for
Upgrade Item [2]. This does not
appear to be a valid setup.
-6525 The custom action %1 in the
InstallExecuteSequence table is run
from an installed file. It must be
sequenced after the %2 action.
Ensure that the custom action is
sequenced properly and that the
base action exists in the sequence.
-6499 The Shallow folder structure setting
should not be used with multi-disk
releases.
Only valid assemblies can be installed to the Global Assembly
Cache. Ensure that the file selected for installation is a valid
assembly.
This error occurs when an upgrade entry exists in the Upgrade
Paths view, but the earlier installation that is specified does not
exist in the location indicated. This can occur if the earlier
installation has been moved because it was referenced in the
Upgrade Paths view or if the folder that contains the earlier
installation cannot be accessed because of permissions. This error
can also occur if the earlier installation referenced (Setup.exe or
.msi) is not a valid Windows Installer–based installation.
This error occurs when you have authored a custom action that
runs from a file that is installed during your setup. The custom
action must be launched during the After Setup Complete Success
dialog part of the installation. Otherwise the file will not exist on the
target system when Windows Installer runs the custom action.
The Shallow folder structure setting can be set from the Releases
property grid of the Releases view. If error -6499 appears, switch
the Shallow folder structure option to "No" so it will create a regular
build folder structure.
-6479 Internal build error. A corrupted merge module in your project causes this error. The
error message has been reported with third-party merge modules
that are not shipped with InstallShield or merge modules that are
shipped with the beta version of Microsoft Visual Studio .NET 2003.
To resolve this error message, determine the merge module
causing the issue and remove it from the project. To find the merge
module, remove all merge modules from your project in the
Redistributables view. Then add one merge module at a time to
your project, and build the release until error -6479 occurs. This is
the merge module causing the error.
After you determine which merge module causes the issue, contact
the vendor of the merge module for more information about the
module. If the merge module is a Microsoft-specific module,
download the latest service pack of Visual Studio to acquire the
updated merge modules. If the merge module is Visual Studio .NETspecific,
make sure that it is acquired from the latest service pack
of Visual Studio .NET.
-6478 FON Files must have a Font Title.
Font %1 in Feature %2.
Set the Font Title property for the file. To do this, right-click the file
in the Files view, select Properties, and type a title in the Font Title
field. If there is no Font Title, a run-time error occurs upon
installation.
622 ISE-1900-UG00 InstallShield 2012 Spring Express Edition User Guide