InstallShield 2012 Express Edition User Guide - Knowledge Base ...

Table 25-2: Build Errors and Warnings (cont.)
Error Description Troubleshooting Tips
-7128 Error embedding
setup.exe.manifest.
-7127 The file '%1' appears to be zero
bytes. Zero byte files are not
supported in mobile installations.
-7124 Could not invoke MSBuild. Make
sure that the .NET Framework %1 is
installed at '%2' on the system. If
you are running InstallShield from
within Visual Studio, you must use
Visual Studio 2005 or later.
-7113 Language support for %1 is not
included in this edition.
-7084 The VBScript Custom Action %1
does not point to a valid VBS file.
Chapter 25: Errors and Warnings
Build Errors and Warnings
This error occurs if there is a problem embedding the application
manifest in the Setup.exe launcher. The application manifest
specifies the minimum privilege level required by your installation’s
Setup.exe file for running the installation (the setup launcher, any
InstallShield prerequisites, and the .msi file) on Windows Vista and
later platforms.
This error may occur if the template manifest file is missing from
the InstallShield Support folder. It also may occur if the
Setup.exe template is missing from the InstallShield
Redist\Language Independent\i386 folder.
To resolve this error, try running a repair of InstallShield.
This error occurs if your project contains a mobile device
installation that has a 0-byte file.
To resolve this error:
1. In the View List under Specify Application Data, click Mobile
Devices.
2. In the Mobile Device Installations explorer, click the mobile
device installation that contains the file that is mentioned in the
error message.
3. In the right pane in the Application Data area, click the
Additional Files link. The Device Files panel opens.
4. Delete the file that is mentioned in the error message, or
replace it with an appropriate file.
If you use MSBuild to build Visual Studio solutions with InstallShield
projects, you must have .NET Framework 3.5 or later on your
machine. In addition, you must be using Visual Studio 2005 or later.
This error appears if you try to enable too many languages in a
project, building with more than two in a non-Premier edition. The
build is successful (unless stop at first error is enabled), but the
extra languages are not built. The first two qualified languages are
built. %1 is replaced with the name of the language that is not
included in this release. To resolve this error, use the Premier
edition of InstallShield to build your release.
This warning message is displayed if you add a VBScript custom
action to your installation but the file specified for the custom
action is not a VBScript file. To resolve this error, select the
appropriate type of file for the specified custom action in the
Custom Actions view.
-7076 Internal build error. Check the Knowledge Base for information about this error, or
request technical support.
InstallShield 2012 Express Edition User Guide ISE-1800-UG01 613