Build Errors and Warnings

InstallShield 2012 Spring

The following table contains a listing of errors and warnings that may occur during the build process.

Note: You can find detailed information—including resolution information—on most InstallShield build errors and warnings in the Knowledge Base.

For troubleshooting information about errors and warnings that may occur when you are building a virtual application, see Virtualization Conversion Errors and Warnings.

Build Errors and Warnings

Error or Warning Number

Message

Troubleshooting Information

-32000

Build canceled by the user.

This error occurs only when the build is terminated during the build process.

-7311

Unable to load manifest file for sideloading app package '%1'.

This build error occurs if you are trying to build a Suite/Advanced UI installation that includes a sideloading app package (.appx) but InstallShield cannot read the app package's manifest file. This may occur if you are trying to build on a Windows XP or Windows Server 2003 system. The ability to create and build a Suite/Advanced UI installation that includes a sideloading app package (.appx) requires Windows Vista or later or Windows Server 2008 or later on the machine that has InstallShield or the Standalone Build.

To resolve this error, remove the .appx package from the Packages view, or build your release on Windows Vista or later or on Windows Server 2008 or later.

-7309

No certificate file is selected in the Packages view for sideloading app '%1'.

If you include a sideloading app package (.appx) in a Suite/Advanced UI project but do not specify a certificate file for the package in the Certificate File setting in the Packages view, InstallShield generates this warning at build time.

The versions of Windows that support .appx packages do not install a sideloading package unless they trust the source of the package. If you are using a custom certificate, such as the one that is generated in Visual Studio, the Suite/Advanced UI installation can make Windows trust the source of your package by adding the custom certificate to the certificate store of target systems. The Suite/Advanced UI installation does this if you include the .cer file in your sideloading package, and specify it in the Certificate File setting in the Packages view.

To resolve this warning, consider using the Certificate File setting in the Packages view to specify the package's .cer file.

-7308

Suite/Advanced UI installations do not support sideloading app packages (.appx) that are built for only ARM processors.

This error occurs if you include an .appx package that targets the ARM processor architecture in a Suite/Advanced project. InstallShield does not have support for including that type of package in an installation.

To resolve this error, use the Packages view remove the package that is listed in the error message from your project, and consider replacing it with a package that targets x86 or x64 systems, or that is neutral.

-7295

Advanced UI projects do not have support for .exe primary packages.

InstallShield lets you add .exe packages as a primary package to a Suite/Advanced UI project, which is available in the Premier edition of InstallShield; however, InstallShield does not let you add .exe packages as primary packages to an Advanced UI project, which is available in the Professional edition of InstallShield.

If you use the Professional edition of InstallShield to open a project that was created in the Premier edition, and if the project contains an .exe package as a primary package, this build error occurs.

To resolve this build error, either use the Premier edition of InstallShield to build the release, or use the Packages view to remove the .exe package from the project.

For more information about the differences between Advanced UI and Suite/Advanced UI projects, see Advanced UI Projects vs. Suite/Advanced UI Projects.

-7294

An Advanced UI project can include only one language.

A Suite/Advanced UI project, which is available in the Premier edition of InstallShield, includes support for multiple languages; however, an Advanced UI project, which is available in the Professional edition of InstallShield, includes support for only one.

If you use the Professional edition of InstallShield to open a project that was created in the Premier edition, and if the project contains more than one language, this build error occurs.

To resolve this build error, either use the Premier edition of InstallShield to build the release, or remove all but one language from the Setup Languages setting in the General Information view of the project. You may also need to remove all but one language from the UI Languages setting on the Build tab in the Releases view.

For more information about the differences between Advanced UI and Suite/Advanced UI projects, see Advanced UI Projects vs. Suite/Advanced UI Projects.

-7293

An Advanced UI project can include only one primary package.

A Suite/Advanced UI project, which is available in the Premier edition of InstallShield, includes support for multiple primary packages; however, an Advanced UI project, which is available in the Professional edition of InstallShield, includes support for only one.

If you use the Professional edition of InstallShield to open a project that was created in the Premier edition, and if the project contains more than one primary package, this build error occurs.

To resolve this build error, either use the Premier edition of InstallShield to build the release, or remove all but one primary package from the Packages view of the project.

For more information about the differences between Advanced UI and Suite/Advanced UI projects, see Advanced UI Projects vs. Suite/Advanced UI Projects.

-7292

An update URL is set but this release is not configured to be digitally signed.

This build warning occurs if a URL is specified in the Update URL setting on the Setup.exe tab in the Releases view of the Advanced UI or Suite/Advanced UI project, but the release is not configured to be digitally signed.

To resolve this warning, specify digital signature information on the Signing tab for the release in the Releases view.

To learn more about updates, see Adding Support for Automatic Updates to an Advanced UI or Suite/Advanced UI Installation.

-7291

An update URL is set but the project contains packages with files located on the source media.

This warning occurs if a URL is specified in the Update URL setting on the Setup.exe tab in the Releases view of the Advanced UI or Suite/Advanced UI project, but one or more packages in the Advanced UI or Suite/Advanced UI project is configured to be stored on the source media.

If you are building a base Advanced UI or Suite/Advanced UI setup launcher, you can ignore this warning.

If you are building the update Advanced UI or Suite/Advanced UI setup launcher that will be downloaded and launched when an earlier base setup launcher is run on a target system, change the run-time location of the packages in your project to either extracted from the setup launcher or downloaded from the Web. The update setup launcher cannot rely on packages that are stored on the source media. For more information, see Specifying a Run-Time Location for a Specific Package in an Advanced UI or Suite/Advanced UI Project.

To learn more, see Adding Support for Automatic Updates to an Advanced UI or Suite/Advanced UI Installation.

-7277

InstallShield does not support using .pfx files to sign media header files (.hdr files).

InstallShield does not support using .pfx files to sign media header files (.hdr files), which are used for the One-Click Install type of installation for InstallScript projects. To resolve this build warning, consider one of the following alternatives for this type of installation:

Use .spc and .pvk files instead of a .pfx file for your digital signature.
Build a compressed installation, which would enable you to sign with a .pfx file.

To learn more about digital signing, see Digital Signing and Security.

-7256

To digitally sign a software identification tag file, .NET Framework 3.5 must be installed.

If your project is configured to include a software identification tag and if the release that you are building is configured to use a .pfx file to digitally sign your release, InstallShield attempts to digitally sign the tag that it creates at build time. If your build machine does not have .NET Framework 3.5, this build warning is displayed.

To resolve this build warning, install .NET Framework 3.5 on your build machine.

-7255

Only .pfx files can be used to digitally sign a software identification tag file.

If your project is configured to include a software identification tag and if the release that you are building is configured to use an .spc file and a .pvk file to digitally sign your release, InstallShield generates this build warning.

To resolve this build warning, switch from an .spc file and a .pvk file to a .pfx file. If you do not need to have a digitally signed tag, you can ignore this warning.

-7246

Package "%1" has an MSI Package condition in which an asterisk (*) is used as a placeholder for one of the condition's settings. InstallShield cannot substitute this placeholder because the appropriate .msi package could not be found.

In order for InstallShield to replace an asterisk in a condition with the appropriate information (such as the product code or product version) from a package in an Advanced UI or Suite/Advanced UI project, the package must be available at build time.

To resolve this error, ensure that the package file is in the source location. If dynamic file linking is used for the package, ensure that the dynamic link filters are not excluding the package file from the build.

-7244

The project does not contain any primary packages. You may need to add a package, or select Primary in the Package Type setting for a package in the Packages view.

This error occurs if your Advanced UI or Suite/Advanced UI project does not contain any packages that are configured to be the primary package.

To resolve this error if your project does not contain any packages, use the Packages view to add a package to your project. For more information, see Guidelines for Adding Packages to an Advanced UI or Suite/Advanced UI Project.

If you already have a dependency package in your project and you want to make it a primary package, use the Package Type setting in the Packages view. To learn more, see Primary Packages vs. Dependency Packages in Advanced UI and Suite/Advanced UI Projects.

-7243

The Detection Condition setting for package '%1' in the Packages view is empty. This type of condition evaluates whether the package is already installed on target systems.

The Detection Condition setting cannot be empty for an .exe type of package in an Advanced UI or Suite/Advanced UI project.

For more information, see Building Conditional Statements in Advanced UI and Suite/Advanced UI Projects.

-7240

Package '%1' is not associated with any features.

Each package that is included in the Packages view of an Advanced UI or Suite/Advanced UI project should be associated with one or more features. Otherwise, the package are not included in any releases that you build.

For more information, see Associating a Package in an Advanced UI or Suite/Advanced UI Project with a Feature.

-7239

The target file '%1' that was selected for an operation's Target setting in the Packages view for package '%2' was not found in the project.

This error occurs if the target file for one of the packages in the Advanced UI or Suite/Advanced UI installation is missing at build time.

To resolve this error, ensure that the target file is in the source location. If dynamic file linking is used for the package, ensure that the dynamic link filters are not excluding the target file from the build.

-7236

InstallShield could not create the software identification tag because the value for the %1 setting in the General Information view is invalid. Ensure that it does not contain any of the following characters:

\ / : * ? " < > |

InstallShield uses the values that you enter for the Unique ID and Tag Creator ID settings as part of the name of the tag file (TagCreatorID_UniqueID.swidtag). Therefore, the ID that you enter must not contain any characters that are invalid for file names.

To resolve this issue, enter a valid value in the setting that is mentioned in the warning message.

For more information, see Including a Software Identification Tag for Your Product.

-7235

InstallShield could not create the software identification tag because the %1 setting in the General Information view is empty.

Creation of a software identification tag requires that several settings in the General Information view have values. To resolve this warning, enter the appropriate value in the setting that is mentioned in the warning message, or select No for the Use Software Identification Tag setting.

For more information, see Including a Software Identification Tag for Your Product.

-7234

InstallShield could not create the software identification tag because the template file Swidtag.xml could not be opened.

InstallShield uses the Swidtag.xml file, which is installed to one of the following locations, to build tag files:

InstallShield Program Files folder\Support\0409

InstallShield Program Files folder\Support\0411

To resolve this issue, ensure that the Swidtag.xml file is present and not locked.

For more information, see Including a Software Identification Tag for Your Product.

-7233

An invalid URL (%2) is specified in the Packages view for package %1.

This build error occurs if you selected Download From The Web for a package in the Packages view of an Advanced UI or Suite/Advanced UI project, but the URL setting under the Location setting is blank, or it contains an invalid URL. To resolve this error, enter a URL that starts with one of the following strings:

http://
https://
ftp://

-7225

The project does not contain any packages.

This build error occurs if try to build an Advanced UI or Suite/Advanced UI project that does not contain any packages.

To resolve this error, use the Packages view to add a package to your project. For more information, see Guidelines for Adding Packages to an Advanced UI or Suite/Advanced UI Project.

-7223

A Mode condition or a Detection condition is required for the Setup.exe to run correctly.

This build error occurs if your Advanced UI or Suite/Advanced UI project includes an .exe package but you have not configured the appropriate conditions for it yet.

For information on adding detection conditions to a package in a project, see the following:

Building Conditional Statements in Advanced UI and Suite/Advanced UI Projects
Guidelines for Defining Conditions in an Advanced UI or Suite/Advanced UI Project

For information on how mode conditions are created, see Triggering Install Mode or Maintenance Mode of an Advanced UI or Suite/Advanced UI Installation.

-7222

No supported languages included in the media. You must select at least one supported language for the media.

This error occurs only when no supported language is selected in the media. To resolve this issue, ensure that at least one language is selected for the Language(s) setting in the Releases view.

-7220

InstallShield encountered an error while including a DIM reference.

This error occurs if your project includes a DIM reference, as shown in the DIM References view, but InstallShield cannot find the DIM project file (.dim). This might occur if the .dim file was moved to a different location or it was renamed, but the path or file name in the installation project that contains the DIM references has not been updated.

-7218

Conflicts were detected building DIMs. In Table %1 Row %2, data files differ in the following columns: %3.

This warning occurs if InstallShield encounters a data conflict between the installation project that is open and one of its DIM references. In this warning message, %1 indicates the name of the table that contains the conflict, and %2 indicates the applicable row; %3 is in the following format:

ColumnName ("InstallationUnitValue" <> "InstallationProjectValue")

The table data for the DIM reference is available in the Direct Editor view of the DIM project. The table data for the installation is available in the Direct Editor view of the installation project.

If a data conflict occurs, InstallShield uses either the installation project data or the DIM data; it depends on which value is selected in the Conflict Resolution setting on the Build Options tab in the DIM References view:

Use Base Project Value— If this value is selected, InstallShield uses the value that is in the installation project instead of the value that is in the DIM project.
Use DIM Project Value—If this value is selected, InstallShield uses the value that is in the DIM project instead of the value that is in the installation project.

If the appropriate value is being used, you can ignore this warning message. If you want to use the value that is being overridden, you can either revise the value in that project, or change the value of the Conflict Resolution setting. Note, however, that if other conflicts occur for this DIM reference, changing the value of the Conflict Resolution setting may also change the resulting built values for those other conflicts.

For more information, see Resolving Build-Time Conflicts Between a Basic MSI Project and a DIM Reference.

-7216

This project includes InstallScript objects that are deprecated. These objects should be removed from the project. A prerequisite should be used instead where possible.

InstallScript objects have been deprecated in favor of InstallShield prerequisites. The recommended alternative for InstallScript objects is InstallShield prerequisites. You can use the InstallShield Prerequisite Editor to create your own InstallShield prerequisites. You can share these InstallShield prerequisites among InstallScript, InstallScript MSI, and Basic MSI projects. To learn more, see:

Defining InstallShield Prerequisites
Adding InstallShield Prerequisites, Merge Modules, and Objects to InstallScript Projects

-7215

Skipping build events. Build events are supported only in the Premier edition of InstallShield.

InstallShield lets you specify commands that you want to be run at various stages of the build process. This build event functionality is available in the Premier edition of InstallShield. For more information, see Specifying Commands that Run Before, During, and After Builds.

If you try to use the Professional edition of InstallShield to build a release that includes build events, InstallShield ignores the build event settings and generates this warning.

To resolve this warning, use the Premier edition of InstallShield to build the release.

-7214

Error loading table %1.

This error occurs if the table that is mentioned in the error message is missing from your project, or it is missing columns.

To resolve this error, open the Direct Editor view, and look for the table that is mentioned in the error message. If it exists, compare the columns in the table with those in a new project, and add any missing tables. If the table does not exist, you can export it from a new project as an .idt file, and then import the .idt file into your existing project. For more information, see:

Exporting Tables from the Direct Editor
Importing Tables with the Direct Editor

-7211

Building a compressed Network Image Setup.exe. All other build types are not allowed in the evaluation mode of InstallShield.

If you are using InstallShield in evaluation mode (that is, you have not activated it), you can build compressed Setup.exe files, but no other release types. If you are creating a Windows Installer–based release, the .msi database is always embedded in the Setup.exe file.

If you try to build an uncompressed release in evaluation mode, the uncompressed option is ignored, and InstallShield displays this build warning.

Once you have activated InstallShield, the evaluation-mode limitations are removed.

-7209

The current Windows Installer package name includes Unicode characters that may cause a run-time error if a compressed Network Image Setup.exe is built.

This build warning occurs if the following conditions are true:

For the name of the .msi package, you include Unicode characters that are not supported by your build machine's ANSI code page.
You include a setup launcher (Setup.exe file) with your release.

This warning occurs to inform you that when the Windows Installer package is extracted from Setup.exe to a temporary location on the target system, run-time error 1152 may occur.

To resolve this warning, change the name of the .msi package so that it does not contain Unicode characters that are not supported by your machine's ANSI code page. To do so, you can use the MSI Package File Name setting on the General tab for a product configuration in the Releases view.

-7208

The current location for this package includes Unicode characters that may cause a run-time error when Windows Installer tries to extract its .cab files.

This warning occurs if the following conditions are true:

The path for the release that InstallShield is building contains Unicode characters that are not supported by your build machine's ANSI code page.
You configure the release so that your product's program files are compressed into .cab files.

You can ignore this warning if end users will launch your release from a location whose path does not contain Unicode characters that are not supported by your build machine's ANSI code page.

If end users try to launch your installation from a path that contains Unicode characters that are not supported by the target system's ANSI code page, run-time error 1311 occurs when Windows Installer tries to extract the .cab files.

-7207

A package cannot contain both the MsiLockPermissionsEx and LockPermissions tables.

An installation should not contain both the MsiLockPermissionsEx table and the LockPermissions table. If you use the Permissions setting for a service, and the settings under it, you are configuring the MsiLockPermissionsEx table of the package. If Traditional Windows Installer handling is selected for the Locked-Down Permissions setting in the General Information view and you have set permissions for one or more files, folders, or registry keys in your project, you are configuring the LockPermissions table of the package.

For more information, see Securing Files, Folders, Registry Keys, and Windows Services in a Locked-Down Environment.

-7201

The language '%1' is missing from this project but included in this release.

This build warning occurs if a language is selected in the UI Languages setting on the Build tab in the Releases view, but it is not also selected in the Setup Languages setting in the General Information view.

This build warning is alerting you that the release will not include the specified run-time language. If you do not want to include the specified run-time language in your release, you can ignore this warning.

If you do want to include the specified run-time language in your release, add the language to the Setup Languages setting.

-7187

The Find What setting for the %1 text replacement is not configured. This text replacement will not be performed.

You have added a replacement item to a replacement set in the Text File Changes view; however, the value for the Find What setting is blank. This setting must have a value; otherwise, the text file changes are not made at run time.

For more information, see Specifying Search-and-Replace Criteria for a Text File Change.

-7186

The Include Files setting for the %1 text replacement set is not configured. None of the text replacements associated with this text replacement set will be performed.

You have added a replacement set in the Text File Changes view; however, the value for the Include Files setting is blank. This setting must have a value; otherwise, the text file changes are not made at run time.

For more information, see Creating a Text File Reference.

-7185

The %1 translation for string identifier %2 includes characters that are not available on code page %3.

This error occurs if both of the following conditions are true:

The string identifier value that you entered for the specified language contains characters that are not available in that language's code page.
You are building a language-specific (ANSI) database.

To resolve this error, consider using the String Editor view to edit the value of the string identifier so that it uses characters from the appropriate code page.

If you must use characters that are not available in the target language's code page, consider selecting Yes for the Build UTF-8 Database setting. Note, however, that this may result in user interface issues in some scenarios because the Windows Installer does not fully support UTF-8 databases. For more information, see the description of the Build UTF-8 Database setting.

-7184

The %1 column of the %2 table includes characters that are not available on code page %3: "%4"

This error occurs if both of the following conditions are true:

A table in the source project database contains characters that are not available in the code page for one or more target languages.
You are building a language-specific (ANSI) database.

To resolve this error, consider changing the data that is described in the error message so that it uses characters from the appropriate code page. For example, if the error message mentions the Shortcut table, consider changing the string in the Shortcuts view.

If you must use characters that are not available in the target language's code page, consider selecting Yes for the Build UTF-8 Database setting. Note, however, that this may result in user interface issues in some scenarios because the Windows Installer does not fully support UTF-8 databases. For more information, see the description of the Build UTF-8 Database setting.

-7174

"%1" contains a reference to a string table entry '%2' that is not included in the project's string table.

In this warning message, %1 indicates the fully qualified path to an InstallScript file (.rul) in the project, and %2 indicates the string ID that is used in that .rul file but is not listed as one of the project's string entries.

InstallShield displays this warning at build time for each string identifier that is found in the project's InstallScript file but not in the String Editor view.

To see the line in the InstallScript code that has the string identifier, double-click the warning message that is displayed on the Tasks tab of the Output window at build time. The string identifier is preceded by the string constant operator (@).

To resolve this build issue, ensure that the string identifier is defined in the String Editor view. In addition, ensure that the spelling of the string identifier in the InstallScript code matches that in the String Editor view.

-7143

Component %1 installs to a 64-bit folder but is not marked as a 64-bit component. This may result in an incorrect installation path for this component's files.

If a component is not configured to be 64 bit, Windows Installer may not install the component's files to the appropriate 64-bit location.

To specify that a component is 64 bit, select Yes for the component's 64-Bit Component setting.

For more information about the 64-Bit Component setting, as well as additional component settings, see Component Settings.

-7138

The Msi Command Line of the release currently being built contains REINSTALLMODE. The parameter appears to have the 'a' option which will force all files to be reinstalled, regardless of checksum or version.

Check the Knowledge Base for information about this error, or request technical support.

-7137

The %1 file that you selected for the Help File Path setting in the Custom Actions view for the %2 custom action does not contain any text.

Create a file that describes the intended behavior of the custom action that is mentioned in the warning. The file should be a text-based file such as a .txt, .htm, or .rtf file. Then in the Custom Actions and Sequences view (or the Custom Actions view), select the custom action and select the file that you created for the Help File Path setting.

To learn more, see Documenting the Behavior of Custom Actions.

-7135

Internal build error

Check the Knowledge Base for information about this error, or request technical support.

-7128

Error embedding setup.exe.manifest.

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 InstallShieldSupport folder. It also may occur if the Setup.exe template is missing from the InstallShieldRedist\Language Independent\i386 folder.

To resolve this error, try running a repair of InstallShield.

-7127

The file '%1' appears to be zero bytes. Zero byte files are not supported in mobile installations.

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 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.

-7125

Internal build error

Check the Knowledge Base for information about this error, or request technical support.

-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.

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.

-7123

Internal build error

Check the Knowledge Base for information about this error, or request technical support.

-7122

Error writing information to the source file for %1. Verify that the file is writeable, and\or that the file ISTemplate.manifest is not read only.

Check the Knowledge Base for information about this error, or request technical support.

-7121

The manifest file %1 does not contain COM information in at least one file element. Please ensure that all COM modules associated with the manifest are self-registering and verify that the self-registration process does not fail for each COM module.

Check the Knowledge Base for information about this error, or request technical support.

-7120

Error building table %1

Check the Knowledge Base for information about this error, or request technical support.

-7119

Could not locate a key file for component %1. Advertised shortcut %2 points to the key file of this component.

Check the Knowledge Base for information about this error, or request technical support.

-7118

The InstallScript Custom Action %1 cannot be sequenced in InstallUISequence for an InstallScript MSI project.

The User Interface sequence does not run in InstallScript MSI installations; the event-driven InstallScript code handles the user interface. To resolve this issue, do one of the following:

Schedule the InstallScript custom action for the Execute sequence.
Use InstallScript event–driven code instead of an InstallScript custom action.

-7117

Custom Action %1 called from Standard dll and stored in Binary table cannot have deferred/rollback/commit execution.

This error occurs if you try to call a deferred-, rollback-, or commit-execution custom action using a standard .dll. When you call a non-Windows Installer .dll (that is, one that does not have the MyFunc(MSIHANDLE) entry point), InstallShield does the following:

InstallShield creates a wrapper .dll with the standard Windows Installer entry point.
InstallShield stores your .dll plus the InstallShield wrapper .dll in the Binary table.

When the custom action is called, Windows Installer calls the InstallShield wrapper .dll. This, in turn, extracts your .dll from the Binary table and calls the function that you specified. However, the InstallShield wrapper .dll does not have access to the Binary table during deferred, rollback, or commit custom actions, and thus it cannot extract and call into your .dll.

To resolve this error, try one of the following options:

Create a new .dll that has a standard Windows Installer entry point and call it directly.
Use InstallScript code to do perform the same functionality if you do not want to write your own .dll.
Schedule your custom action to run in immediate mode instead of deferred, rollback, or commit mode.

-7116

Custom Action DLL %1 not found in release.

Check the Knowledge Base for information about this error, or request technical support.

-7113

Language support for %1 is not included in this edition.

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.

-7108

%s is too large to store in a CAB (2GB maximum).

Check the Knowledge Base for information about this error, or request technical support.

-7107

The merge module %1 silently fails to install from a compressed build. Applying compression post-build may work properly.

Check the Knowledge Base for information about this error, or request technical support.

-7104

The destination of component %1 is the GlobalAssemblyCache. The component must contain a key file.

Check the Knowledge Base for information about this error, or request technical support.

-7101

This component %1 is shared between multiple features, which can create problems for features that are going to use MSI's Install On Demand technology.

Check the Knowledge Base for information about this error, or request technical support.

-7098

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-7097

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-7096

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-7095

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-7092

Missing binary entry ISSetup.dll

This error occurs if you build a project that includes an InstallScript custom action, but the InstallScript engine (ISSetup.dll) has been removed from the Binary table. To resolve this error, manually add a new entry called ISSetup.dll to the Binary table and browse to the following DLL:

InstallShield Program Files Folder\Redist\Language Independent\i386\ISSetup.dll

-7088

Failed to load %1. This file needs to be loaded in order to build the associated custom object.

Verify that the file, %1, is in the System subfolder within the InstallShield Program Files folder.

-7087

Custom objects cannot be included with your installation media due to an error creating the Windows Installer Object. In order to include custom objects, Windows Installer needs to be installed on the build system.

Verify that Windows Installer is installed properly on the build system.

-7086

The device driver installation framework is not currently available. The device driver feature will not be fully functional until an update has been provided. Please contact technical support for more details.

This error occurs when you build a release for a project in which you used the Device Driver Wizard to include a device driver package with your installation. The redistributable needed to install the device driver will be available in an update to InstallShield. Instructions for obtaining the update will be posted in an article for this build error in the Knowledge Base when the redistributable is available. To resolve the build error before you receive the redistributable, you can remove the device driver component in the Components view and then rebuild the release.

-7084

The VBScript Custom Action %1 does not point to a valid VBS file.

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 and Sequences view (or the Custom Actions view).

-7083

Script '%s' is not associated with any connection.

Check the Knowledge Base for information about this error, or request technical support.

-7082

An error occurred while generating your Sql Script.

Check the Knowledge Base for information about this error, or request technical support.

-7080

An error occurred while testing the component to see if the device driver package scan at build property is set.

Check the Knowledge Base for information about this error, or request technical support.

-7079

An error occurred while getting the path to the device driver package.

Check the Knowledge Base for information about this error, or request technical support.

-7078

Unable to scan device driver package %1. The file is missing.

Check the Knowledge Base for information about this error, or request technical support.

-7077

An error occurred while scanning a device driver package.

Check the Knowledge Base for information about this error, or request technical support.

-7065

The MSI 3.1 Engine could not be found. You can download this using the Redistributable Downloader under the Tools menu, if it has been made available by Microsoft. We have included the 3.0 Engine in your built installation.

This message is displayed as a build error if version 3.1 of the Windows Installer engine was selected to be included but it was not found on the build machine.

This message is displayed as a build warning if the version 3.1 or 2.0 best-fit option was selected but version 3.1 of the Windows Installer engine was not found on the build machine.

-7064

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-7063

The File %1 in Component %2 is being installed to the Windows Fonts folder, but there is no corresponding record in the Font table. The Font will not be registered properly on the target system.

To resolve this warning, open the Files and Folders view and remove the font mentioned in the message. Then re-add the font to the Fonts folder; InstallShield adds the corresponding record to the Font table automatically.

-7062

Refreshing the COM+ settings from the client machine. An error occurred while refreshing the COM+ settings from the client machine.

This build error occurs when an exception error has occurred with a COM+ application that is selected in the Component Services view. An option is provided to refresh the COM+ settings during the build process, and build error -7062 occurs when this option is selected and the refreshing process has failed. To resolve this error, you can open the Component Services view, select the COM+ application, and clear the Refresh the COM+ settings from the client machine at build check box on the Installation tab.

-7061

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-7060

Due to licensing requirements, InstallShield requires that you provide the MSI 3.0 engine redistributable from the MSI 3.0 Beta. Please copy instmsi.exe from the MSI 3.0 Beta folder to \redist\Language Independent\i386\MSI3.0\instmsiw.exe.

Check the Knowledge Base for information about this error, or request technical support.

-7059

Unable to update the latest patch version property. As a result, future patches built from this project may not be sequenced properly. Make sure the project is not marked as read-only.

Check the Knowledge Base for information about this error, or request technical support.

-7058

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-7057

You have enabled FlexNet Connect for this deployment, however, you have not provided a URL to check for updates. This is required for 'CD-ROM' deployment configurations.

Check the Knowledge Base for information about this error, or request technical support.

-7055

Due to licensing requirements, InstallShield requires that you provide the .NET redistributable from the Whidbey release of Visual Studio .NET. Please copy the contents of Common7\IDE\Packages\DotNetFX to \Support\Whidbey. ClickOnce deployments will not run properly unless this is installed to the target machine.

Check the Knowledge Base for information about this error, or request technical support.

-7053

The 'Internet' deployment configuration is enabled, but the 'install location' field has not been authored. This will result in errors when running your deployment.

Check the Knowledge Base for information about this error, or request technical support.

-7052

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-7051

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-7050

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-7049

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-7048

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-7047

An error occurred while building the 'File Share' configuration of the ClickOnce deployment.

Check the Knowledge Base for information about this error, or request technical support.

-7046

An error occurred while building the 'CD-ROM' configuration of the ClickOnce deployment.

Check the Knowledge Base for information about this error, or request technical support.

-7045

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-7044

An error occurred while copying the main application manifest to the release specific location.

Check the Knowledge Base for information about this error, or request technical support.

-7043

An error occurred while building the 'Internet' configuration of the ClickOnce deployment.

Check the Knowledge Base for information about this error, or request technical support.

-7042

An error occurred while determining the source location for the primary application assembly.

Check the Knowledge Base for information about this error, or request technical support.

-7041

Initializing the default deployment manifest.

Check the Knowledge Base for information about this error, or request technical support.

-7040

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-7039

An error occurred while creating the base ClickOnce deployment.

Check the Knowledge Base for information about this error, or request technical support.

-7038

An error occurred while creating the base deployment folders in the release location.

Check the Knowledge Base for information about this error, or request technical support.

-7037

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-7036

An error occurred while loading the primary application assembly.

Check the Knowledge Base for information about this error, or request technical support.

-7035

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-7030

An error occurred while loading the releases that need to be built.

Check the Knowledge Base for information about this error, or request technical support.

-7029

The build engine is unable to load the settings for the 'CD-ROM' release type.

Check the Knowledge Base for information about this error, or request technical support.

-7028

The build engine is unable to load the settings for the 'File Share' release type.

Check the Knowledge Base for information about this error, or request technical support.

-7027

The build engine is unable to load the settings for the 'Internet' release type.

Check the Knowledge Base for information about this error, or request technical support.

-7026

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-7025

The COM+ component server file '%1' cannot be found on your system. The component '%2' will not be installed on the target system. You will need to install the component manually after your COM+ application is installed.

%1 refers to the COM+ DLL that is missing, and %2 refers to the ProgID. To resolve this warning, add the DLL to your system in the appropriate location, or remove the COM+ component from your project.

-7024

To include J# in the build you must also include .NET.

J# requires the .NET Framework Redistributable Package, but it is not included in the installation. If you are sure that your end users already have the .NET Framework on their systems, you can ignore this warning message. However, if there is a chance that they will not have the .NET Framework, add it to your installation. If the .NET Framework is not on their systems, they might have trouble installing J# as part of your installation.

For more information, see Adding .NET Framework Redistributables to Projects.

-7023

Internal build error.

This error occurs if a merge module such as MFC 7.1 is not configured correctly or it is corrupted. If you have more than one merge module in your project but you do not know which one is causing the error, you need to first identify the problematic merge module. You can do this by removing a merge module from your project and then building your release. If the error recurs, you have identified the problematic merge module. If not, remove a different merge module and then build. Once you have identified the merge module causing the error, try reinstalling it. If that does not resolve the error, contact the author to obtain the latest version.

-7016

The CabFiles key in the ini file that supports the "%1" Windows Mobile installation is too long. Shorten the Application Name, Company Name, or reduce the number of platforms/processors targeted.

To resolve this error, open the Mobile Devices view and select the installation mentioned in the error message. If possible, shorten the company name or the application name, or reduce the number of platforms and/or processors that your installation supports. As an alternative, set up your installation so that it supports all platforms and/or processors.

-7015

Error copying setup.inx to media folder. Unexpected error.

This error occurs if Setup.inx, the compiled script file, cannot be copied to the Media folder located in the \Media\\Disk Images\Disk 1 folder. This can occur if you are out of disk space or the file is locked.

-7014

Error copying setup.inx to media folder. Script is read-only.

This error occurs if Setup.inx, the compiled script file, is marked as read-only. To resolve this error, find the Setup.inx file, which is usually in the \Media\\Disk Images\Disk 1 folder. Right-click this file and select Properties. Then clear the Read-only check box.

-7012

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-7011

%1 must have a strong name to be installed to the GlobalAssemblyCache.

You can install an assembly to the Global Assembly Cache only if it has a strong name. A strong name contains the assembly's simple text name, version number, culture information (if available), a public key, and a digital signature. Using strong-named assemblies in the Global Assembly Cache enables you to have multiple versions of an assembly with the same name but with different versions of .dll files. The assemblies stored in the Global Assembly Cache can be shared by different applications on a computer. To resolve this error message, you have two options.

Change the target destination for the assembly to a location other than the Global Assembly Cache if sharing that assembly with other applications is not explicitly required. Note that it is not necessary to install assemblies into the Global Assembly Cache to make them accessible to COM interop.
Select an assembly that has a strong name for installation to the Global Assembly Cache. Note that once an assembly is created, you cannot sign it with a strong name. You can sign an assembly with a strong name only when you create it.

-7001

During the last build, the .msi file was only partially built. In order to stream the script into the .msi file, you must have a complete .msi file. Build a complete .msi file by selecting "Build <ReleaseName>" from the Build menu.

When you cancel the build, a partially built .msi file exists. If you attempt to compile script into the partial .msi file, this error occurs. Select "Build <ReleaseName>" from the Build menu to build a complete .msi file.

-6654

The file %1 is not the key file of component %2. If you call a function in a standard DLL that is installed with the product and the action is scheduled as deferred, the DLL you are calling must be the component's key file.

Set the called DLL as the component's key file.

-6653

The feature %1 in the installation contains more than 1600 components. There is a maximum limit of 1600 components per feature.

For more information, see ICE47 and FeatureComponents Table.

-6652

Could not create _isconfig.xml for use with InstallUtilLib.dll.

Check the Knowledge Base for information about this error, or request technical support.

-6651

The setup you are building contains more than 32,767 files. Automatically switching setup package to appropriate MSI schema.

This warning appears if your installation package contains more than 32,767 files. InstallShield automatically applies the large package schema.

Caution: There is an issue with patching if your package uses the large package schema. When you build the patch, the following error is triggered: "Can't Generate Primary Transform."

-6647

Cannot move file from %1 to %2.

Check the Knowledge Base for information about this error, or request technical support.

-6646

The %1 property in the merge module %2 is set to NULL. This property cannot be NULL.

Check the Knowledge Base for information about this error, or request technical support.

-6645

%1 failed to load. Error: %2 Error Description: %3

Check the Knowledge Base for information about this error, or request technical support.

-6641

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6640

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6639

The merge module %1 requires one of the following merge modules also to be included in the setup: %2.

Check the Knowledge Base for information about this error, or request technical support.

-6638

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6637

Invalid registry data for component NewComponent1 while importing "C:\RegTest\SingleSlashl"=dword:2 (where the information in italics represents the invalid data).

The invalid data in this example is the use of a single backslash instead of two backslashes. Another example would be an entry with DWORD in it instead of dword.

-6636

The file key %1 and %2 are found in the File table. Despite having different cases, the identical key names will cause an unexpected result when the files are installed on the target system. This occurs because the compressed files in the cabinet file are named using the file keys. To correct this issue, change one of the file keys to be unique in the cabinet file if you are building a compressed setup or a merge module. You can change the file key name in the Direct Editor view.

Check the Knowledge Base for information about this error, or request technical support.

-6635

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6634

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6633

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6632

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6631

InstallScript MSI projects do not have Multiple Instance support.

Check the Knowledge Base for information about this error, or request technical support.

-6630

The property InstanceId does not appear in the Property table.

Check the Knowledge Base for information about this error, or request technical support.

-6629

The value for the property InstanceId is not numeric.

Check the Knowledge Base for information about this error, or request technical support.

-6628

The value for the property InstanceId is duplicated with a value in the ISProductConfigurationInstance table.

Check the Knowledge Base for information about this error, or request technical support.

-6627

Component %1 has nonfile data but does not have InstanceId in its condition.

Check the Knowledge Base for information about this error, or request technical support.

-6626

Could not add instance transform %1 to substorage.

Check the Knowledge Base for information about this error, or request technical support.

-6625

Could not create instance transform %1.

Check the Knowledge Base for information about this error, or request technical support.

-6624

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6623

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6622

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6620

Could not open the reference package %1 for key synchronization.

Check the Knowledge Base for information about this error, or request technical support.

-6619

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6618

An error occurred while setting the key paths for dynamically created components.

Check the Knowledge Base for information about this error, or request technical support.

-6617

An Error occurred while adding the file '%1' to the synchronization maps.

Check the Knowledge Base for information about this error, or request technical support.

-6616

An error occurred while setting the key path for component %1.

Check the Knowledge Base for information about this error, or request technical support.

-6615

Could not update File.FileName for File %1.

Check the Knowledge Base for information about this error, or request technical support.

-6614

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6613

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6612

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6611

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6610

An error occurred determining if the dynamically linked file %1 is a modified file.

Check the Knowledge Base for information about this error, or request technical support.

-6609

An error occurred determining if the dynamically linked file %1 is a new file.

Check the Knowledge Base for information about this error, or request technical support.

-6608

Your splash screen will not be displayed during the installation because %1 is a compressed bitmap file. To display a splash screen, you must specify a uncompressed bitmap file.

Check the Knowledge Base for information about this error, or request technical support.

-6607

Your splash screen will not be displayed during the installation because %1 is not a bitmap file. To display a splash screen, you must specify a valid bitmap file.

Check the Knowledge Base for information about this error, or request technical support.

-6606

This setup has the same package code as the setup specified by minor upgrade item '%1'. The package codes must be unique.

Check the Knowledge Base for information about this error, or request technical support.

-6605

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6604

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6603

An error occurred while attempting to open the upgraded image %1.

Check the Knowledge Base for information about this error, or request technical support.

-6602

An error occurred while attempting to close the upgraded image %1.

Check the Knowledge Base for information about this error, or request technical support.

-6601

An error occurred while attempting to set the property %1 in the upgraded image.

Check the Knowledge Base for information about this error, or request technical support.

-6600

An error occurred while attempting to retrieve the property %1 from the upgraded image.

Check the Knowledge Base for information about this error, or request technical support.

-6599

An error occurred while creating the standard QuickPatch actions to the upgraded image.

Check the Knowledge Base for information about this error, or request technical support.

-6598

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6597

An error occurred while attempting add ISQuickPatchHelper.dll to the binary table in the upgraded image.

Check the Knowledge Base for information about this error, or request technical support.

-6596

An error occurred while attempting to sequence the action %1 in the upgraded image.

Check the Knowledge Base for information about this error, or request technical support.

-6595

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6594

An error occurred while attempting to determine the sequence number for the base action %1 in the upgraded image.

Check the Knowledge Base for information about this error, or request technical support.

-6593

An error occurred while initializing file class wrapper for %1.

Check the Knowledge Base for information about this error, or request technical support.

-6592

An error occurred while attempting to determine how to process the file %1.

Check the Knowledge Base for information about this error, or request technical support.

-6591

An error occurred while attempting to make the settings required to patch the file %1.

Check the Knowledge Base for information about this error, or request technical support.

-6590

An error occurred while attempting to create the RemoveFile table entry for %1.

Check the Knowledge Base for information about this error, or request technical support.

-6589

An error occurred while attempting to attach the component '%1' to its designated features.

Check the Knowledge Base for information about this error, or request technical support.

-6588

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6587

An error occurred while generating a formatted file name for %1.

Check the Knowledge Base for information about this error, or request technical support.

-6586

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6585

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6584

An error occurred while attempting to create a new component.

Check the Knowledge Base for information about this error, or request technical support.

-6583

An error occurred while attempting to load the component %1.

Check the Knowledge Base for information about this error, or request technical support.

-6582

An error occurred while saving the component %1.

Check the Knowledge Base for information about this error, or request technical support.

-6581

An error occurred while adding component '%1' to feature %2.

Check the Knowledge Base for information about this error, or request technical support.

-6580

An error occurred while generating a sub feature for feature %1.

Check the Knowledge Base for information about this error, or request technical support.

-6579

An error occurred while synchronizing data in table '%1' for component %2.

Check the Knowledge Base for information about this error, or request technical support.

-6578

An error occurred while synchronizing shortcuts from component '%1' while creating the upgraded image.

Check the Knowledge Base for information about this error, or request technical support.

-6577

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6576

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6575

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6574

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6573

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6572

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6571

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6570

An error occurred while writing the property '%1' to the patch configuration properties file.

Check the Knowledge Base for information about this error, or request technical support.

-6569

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6568

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6567

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6566

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6565

An error occurred while writing the image family '%1' to the patch configuration properties file.

Check the Knowledge Base for information about this error, or request technical support.

-6564

An error occurred while deleting the target image '%1' from the patch configuration properties file.

Check the Knowledge Base for information about this error, or request technical support.

-6563

An error occurred while writing the target image '%1' to the patch configuration properties file.

Check the Knowledge Base for information about this error, or request technical support.

-6562

An error occurred while writing the upgraded image %1 to the patch configuration properties file.

Check the Knowledge Base for information about this error, or request technical support.

-6561

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6560

The stored package code of %1, does not match %2 which is in the referenced package %3. Modifying a referenced MSI package of a Quick Patch, invalidates all Quick Patches that reference that MSI package.

Check the Knowledge Base for information about this error, or request technical support.

-6558

The Custom Action %1 in the InstallExecuteSequence table is run from an installed file. To run the custom action successfully, you may need to have a condition that checks if the source file is installed locally.

To successfully run a custom action that is run from an installed file, you must ensure that the file is installed locally using a conditional statement:

If the custom action is sequenced before RemoveFiles—Run the action only if the component was installed locally. (?ComponentName=3)
If the custom action is sequenced between RemoveFiles and InstallFiles—Run the action only if the component was installed locally. Do not run the action on an uninstallation. (?ComponentName=3) AND NOT($ComponentName=2)
If the custom action is sequenced after InstallFiles—Run the action only if the component will be installed locally. ($ComponentName=3)

Note: The ComponentName is the component that is associated with the source file.

-6557

Unable to find the .NET Compact Framework for the given platform/processor combination from the InstallShield Program File Folder\Support\NetCF.ini file.

Ensure that the .NET Compact Framework is in the correct location.

-6556

Error in including .NET Compact Framework .cab files in setup.

This error might occur for the following reasons:

The .NET Compact Framework files cannot be found in the locations specified in the InstallShieldProgram Files Folder\Support\.NetCR.ini file.
The CEDefault.ico file is not in the InstallShieldProgram File Folder\Program\04xx folder.
There is an error writing to the ISCEInstall table.

-6555

Unable to copy InstallShield Program File Folder\Support\CFAppMgr.ini file to a temporary location.

Make sure that CFAppMgr.ini file exists at the InstallShieldProgram Files Folder\Support folder. If this file does not exist, launch the InstallShield setup in repair mode. Remove any temporary files to create more disk space on the system.

-6553

Unable to find the .NET Compact Framework .cab file for the processor.

Open the InstallShieldProgram Files Folder\Support\NetCF.ini file and configure the .NET CF selection for this processor to resolve the issue.

-6552

The file key %1 of component %2 could not be synchronized with the previous package because that file key is already in use.

Check the Knowledge Base for information about this error, or request technical support.

-6551

The Name and Value columns are blank in the registry record Registry1 of Component NewComponent1. The Windows Installer will set the (Default) value of HKEY_LOCAL_MACHINE\New Key #1 to an empty string. If you would like to set the (Default) value to (Value Not Set), you need to set "Install if absent, Uninstall if present" for that key in the Registry view. If the key already exists on the Target machine, the (Default) value will not be changed.

This warning appears for every registry key you add to your project and do not manually set the default key. To set the (Default) value to (Value Not Set), you need to set "Install if absent, Uninstall if present" for that key in the Registry view.

-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).

Only valid assemblies can be installed to the Global Assembly Cache. Ensure that the file selected for installation is a valid assembly.

-6549

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6548

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6547

The file '%1' already exists in the setup. Please modify the existing file instead of inserting a new one otherwise this file may not uninstall properly.

Check the Knowledge Base for information about this error, or request technical support.

-6546

An error occurred while testing the new file '%1' for potential conflicts.

Check the Knowledge Base for information about this error, or request technical support.

-6545

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6544

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6543

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6542

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6541

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6540

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6539

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6538

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6537

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6536

An error occurred opening %1.

Check the Knowledge Base for information about this error, or request technical support.

-6535

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6534

An error occurred cloning the component %1.

Check the Knowledge Base for information about this error, or request technical support.

-6533

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6532

An error occurred setting the updated component name for file %1.

Check the Knowledge Base for information about this error, or request technical support.

-6530

Error processing setup [1] for Upgrade Item [2]. This does not appear to be a valid setup.

This error occurs when a minor upgrade entry exists in the Upgrades view of InstallShield, and the previous installation specified does not exist in the location indicated. See Knowledge Base article Q108525 for resolution information.

-6529

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6528

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6528

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6527

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6526

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-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.

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 come after the InstallFiles action in the sequence. Otherwise the file will not exist on the target system when Windows Installer runs the custom action. The only exception to this is when you run this custom action on uninstallation. In that case, the file has already been installed so the custom action does not have to occur after InstallFiles.

-6524

The Custom Action %1 in the InstallExecuteSequence table is deferred and must be sequenced between %2 and %3. Ensure that the Custom Action is sequenced properly and that the base actions exist in the sequence.

Check the Knowledge Base for information about this error, or request technical support.

-6523

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6522

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6521

An error occurred setting the required attribute on the feature %1.

Check the Knowledge Base for information about this error, or request technical support.

-6520

An error occurred deleting the COM data for component %1.

Check the Knowledge Base for information about this error, or request technical support.

-6519

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6518

An error occurred deleting the file %1 from the SelfReg table.

Check the Knowledge Base for information about this error, or request technical support.

-6517

An error occurred adding the file %1 to the SelfReg table.

Check the Knowledge Base for information about this error, or request technical support.

-6506

The Msi Command Line Attribute of the release currently being built is setting the REINSTALL or REINSTALLMODE parameter. This will cause your setup to always run in Resume mode.

Check the Knowledge Base for information about this error, or request technical support.

-6504

The Latest Image %1 does not contain any Previous Images.

Check the Knowledge Base for information about this error, or request technical support.

-6501

An error occurred building the ISDLLWrapper table. Component %1 is not found in the Component table.

Check the Knowledge Base for information about this error, or request technical support.

-6500

An error occurred building the ISDLLWrapper table. The File %1 is not found in the File table.

Check the Knowledge Base for information about this error, or request technical support.

-6499

The Shallow folder structure setting should not be used with multi-disk releases.

You can configure the Shallow Folder Structure setting on the Build tab of the Releases view. If error -6499 appears, select No for the Shallow Folder Structure setting so it will create a regular build folder structure.

-6497

Patch Creation Warning: %1.

Check the Knowledge Base for information about this error, or request technical support.

-6496

The file hash for the unversioned file '%1' does not differ from that of the previous version. This file will not be updated.

Check the Knowledge Base for information about this error, or request technical support.

-6495

The version for file '%1' only differs past the third version element. It must differ within the first three elements of the version string.

Check the Knowledge Base for information about this error, or request technical support.

-6494

The new file for file '%1' has the same version as the file that exists in the setup. This file will not be updated.

Check the Knowledge Base for information about this error, or request technical support.

-6493

The new file for file '%1' has a lower version than the file that exists in the setup. This file will not be updated.

Check the Knowledge Base for information about this error, or request technical support.

-6492

The file '%1' has no associated feature selected. This setting is required for adding new files.

Check the Knowledge Base for information about this error, or request technical support.

-6491

The new file path '%1' does not exist for file '%2'.

Check the Knowledge Base for information about this error, or request technical support.

-6490

Unable to set Just-In-Time compilation at install time because the Component %1 is configured to install to the Global Assembly Cache.

Check the Knowledge Base for information about this error, or request technical support.

-6489

Unable to set Installer Class because the Component %1 is configured to install to the Global Assembly Cache.

Check the Knowledge Base for information about this error, or request technical support.

-6487

The latest image %1 does not contain any previous images.

This error occurs if a latest image in the Patch Design view does not have at least one previous image. A latest image must have at least one previous image to create a patch.

-6486

The CAB files will not be digitally signed because the version of MSI.DLL is less than 2.0.

Check the Knowledge Base for information about this error, or request technical support.

-6485

The MsiFileHash table will not be built because the version of MSI.DLL is less than 2.0.

Check the Knowledge Base for information about this error, or request technical support.

-6584

The External File key '%1' does not exist in the Upgraded Image '%2'.

Check the Knowledge Base for information about this error, or request technical support.

-6483

The External File reference '%1' does not exist.

Check the Knowledge Base for information about this error, or request technical support.

-6482

An error occurred while verifying an External File key.

Check the Knowledge Base for information about this error, or request technical support.

-6481

The Target Image '%1' does not exist.

Check the Knowledge Base for information about this error, or request technical support.

-6480

The Upgraded Image '%1' does not exist.

Check the Knowledge Base for information about this error, or request technical support.

-6479

Unable to resolve target path for Directory Id '%1'.

Check the Knowledge Base for information about this error, or request technical support.

-6478

FON files must have a Font Title. Font %1 in component %2.

Check the Knowledge Base for information about this error, or request technical support.

-6477

An error occurred while adding the remove registry entry for the key '%1' and Value '%2'.

Check the Knowledge Base for information about this error, or request technical support.

-6476

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6475

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6474

An error occurred while processing the registry value modifications made to the project.

Check the Knowledge Base for information about this error, or request technical support.

-6473

An error occurred while preparing to delete the value '%1' from the key '%2'.

Check the Knowledge Base for information about this error, or request technical support.

-6472

An error occurred while deleting the value '%1' from key '%2' for all features.

Check the Knowledge Base for information about this error, or request technical support.

-6471

An error occurred while deleting the value '%1' from key '%2' for feature '%3'.

Check the Knowledge Base for information about this error, or request technical support.

-6470

An error occurred while processing the registry key modifications made to the project.

Check the Knowledge Base for information about this error, or request technical support.

-6469

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6468

An error occurred while making the settings to modify the registry key '%1' to '%2' for all features.

Check the Knowledge Base for information about this error, or request technical support.

-6467

An error occurred while making the settings to modify the registry key '%1' to '%2' for feature '%3'.

Check the Knowledge Base for information about this error, or request technical support.

-6466

Error in populating the CE setup info into the desktop setup.

For additional information regarding this error, see the log file created in the following directory: <Product Config>\<Release>\CEApps\<CE Project Name>

-6465

Error in creating the CE setup media from the .inf file.

For additional information regarding this error, see the log file created in the following directory: <Product Config>\<Release>\CEApps\<CE Project Name>

-6464

Error in adding CE Setup DLLs info while creating the .inf file to build CE setup media.

For additional information regarding this error, see the log file created in the following directory: <Product Config>\<Release>\CEApps\<CE Project Name>

-6463

Error in adding CE registry entries.

For additional information regarding this error, see the log file created in the following directory: <Product Config>\<Release>\CEApps\<CE Project Name>

-6462

Error in adding CE file associations.

For additional information regarding this error, see the log file created in the following directory: <Product Config>\<Release>\CEApps\<CE Project Name>

-6461

Error in adding CE shortcuts.

For additional information regarding this error, see the log file created in the following directory: <Product Config>\<Release>\CEApps\<CE Project Name>

-6460

Error in adding CE setup files.

For additional information regarding this error, see the log file created in the following directory: <Product Config>\<Release>\CEApps\<CE Project Name>

-6459

Error in populating the information for the .inf file to build CE Setup media.

For additional information regarding this error, see the log file created in the following directory: <Product Config>\<Release>\CEApps\<CE Project Name>

-6458

An error occurred while creating an Additional File reference for the upgraded image '%1'.

Check the Knowledge Base for information about this error, or request technical support.

-6457

'Ignore Missing Files' is set on the target image '%1'. This cannot be set when using the 'Include Whole Files' option on the Upgraded Image.

Check the Knowledge Base for information about this error, or request technical support.

-6456

An unexpected error occurred while making the settings required to include whole files in the patch.

Check the Knowledge Base for information about this error, or request technical support.

-6455

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6454

Unable to create whole file patch for '%1'. An error occurred while attempting to rename the file.

Check the Knowledge Base for information about this error, or request technical support.

-6453

An error occurred while trying to rename the file '%1' back to its original file name '%2'.

Check the Knowledge Base for information about this error, or request technical support.

-6452

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6451

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6449

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6448

An error occurred while attempting to remove the file '%1' from the upgraded image.

Check the Knowledge Base for information about this error, or request technical support.

-6447

An error occurred while deleting the file table entry for the file '%1'.

Check the Knowledge Base for information about this error, or request technical support.

-6446

An error occurred while deleting the component key for the upgraded image for the file '%1'.

Check the Knowledge Base for information about this error, or request technical support.

-6445

An error occurred while adding the file '%1' to the upgraded image.

Check the Knowledge Base for information about this error, or request technical support.

-6444

An error occurred while creating the new file entry for file key '%1'.

Check the Knowledge Base for information about this error, or request technical support.

-6443

An error occurred while creating a new component for the file key '%1'.

Check the Knowledge Base for information about this error, or request technical support.

-6442

Unable to create new feature off of the root feature '%1'.

Check the Knowledge Base for information about this error, or request technical support.

-6441

Unable to create feature component entry for feature '%1' and component '%2'.

Check the Knowledge Base for information about this error, or request technical support.

-6440

Unable to find feature '%s' while creating settings for new file.

Check the Knowledge Base for information about this error, or request technical support.

-6434

The setup '%1' specified by ISLatestRelease was built compressed. To use this variable you must build your setup uncompressed.

Check the Knowledge Base for information about this error, or request technical support.

-6433

An error occurred while setting the property %1.

Check the Knowledge Base for information about this error, or request technical support.

-6432

An error occurred while creating the configuration data Properties.

Check the Knowledge Base for information about this error, or request technical support.

-6431

An error occurred while creating configuration data for the Image Family %1.

Check the Knowledge Base for information about this error, or request technical support.

-6430

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6429

An error occurred while creating configuration data for the Target Image %1.

Check the Knowledge Base for information about this error, or request technical support.

-6428

An error occurred while creating configuration data for the Upgraded Image %1.

Check the Knowledge Base for information about this error, or request technical support.

-6427

The setup referred to by , '%1', does not exist.

Check the Knowledge Base for information about this error, or request technical support.

-6426

An error occurred while trying to resolve the variable .

Check the Knowledge Base for information about this error, or request technical support.

-6425

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6424

The project contains a Minor Upgrade item, however the current release does not use a setup launcher. You will have to specify the upgrade command line manually for this minor upgrade to function properly.

Check the Knowledge Base for information about this error, or request technical support.

-6423

The project contains a Minor Upgrade item that references the setup %1. However, the referenced setup can only be upgraded with a Major upgrade. Please use the Major Upgrade item or the automatic upgrade item.

Check the Knowledge Base for information about this error, or request technical support.

-6422

An error occurred while adding Major Upgrade settings for %1.

Check the Knowledge Base for information about this error, or request technical support.

-6421

An error occurred determining if the setup %1 is a major upgrade.

Check the Knowledge Base for information about this error, or request technical support.

-6420

The Upgrade Item setup [MSI name].msi is not found. Unable to create upgrade settings.

Ensure that the setup exists, that it is an .msi file, and that the name is correct.

-6419

An unexpected error occurred processing upgrade item %1.

Check the Knowledge Base for information about this error, or request technical support.

-6418

An unexpected error occurred while processing items to be upgraded.

Check the Knowledge Base for information about this error, or request technical support.

-6415

There was an error creating the patch package. Writing contents of log file '%1' to output window.

Check the Knowledge Base for information about this error, or request technical support.

-6414

An error occurred populating the file hash for the unversioned file %1.

Check the Knowledge Base for information about this error, or request technical support.

-6413

The patch creation process returned the error code %1.

Check the Knowledge Base for information about this error, or request technical support.

-6412

An error occurred while creating the patch package.

Check the Knowledge Base for information about this error, or request technical support.

-6411

An error occurred setting the file version for %1.

Check the Knowledge Base for information about this error, or request technical support.

-6410

An error occurred while attempting to copy the file %s to the release location.

Check the Knowledge Base for information about this error, or request technical support.

-6409

An error occurred while building the source path for file %1.

Check the Knowledge Base for information about this error, or request technical support.

-6408

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6407

An error occurred setting the PackageCode int he Updated Image.

Check the Knowledge Base for information about this error, or request technical support.

-6406

An error occurred setting the Product Version in the updated image.

Check the Knowledge Base for information about this error, or request technical support.

-6405

An error occurred while preparing the Upgraded Image.

Check the Knowledge Base for information about this error, or request technical support.

-6404

An error occurred preparing the Patch Configuration Properties file.

Check the Knowledge Base for information about this error, or request technical support.

-6403

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6402

An error occurred while preparing the release location for building.

Check the Knowledge Base for information about this error, or request technical support.

-6401

Unable to copy Original Setup file to release location.

Check the Knowledge Base for information about this error, or request technical support.

-6400

Unable to copy patch configuration properties template to release location.

Check the Knowledge Base for information about this error, or request technical support.

-6309

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6308

mscorsn.dll cannot be located on your system. You can set the path to mscorsn.dll using Tools | Options. The file is part of the Microsoft .NET Framework redistributable. %1.

Check the Knowledge Base for information about this error, or request technical support.

-6307

Unable to extract one or more files to '%1'. The file path is longer than the limit set by the operating system. Change the build location of the current release to a shorter path to resolve this issue.

Change the build location of the current release to a shorter path.

-6306

Port number specified for configuring IIS Virtual Directories is invalid.

Make sure that the TCP port number that is specified for the virtual directory in the Internet Information Services view is valid. To learn more, see Configuring the TCP Port and Site Numbers.

-6305

Could not load assembly "%1" because of : "%2".

Make sure that you are able to load the dependent file and that the assemblies are accessible according to the assembly binding rules. For more information, see "How the Runtime Locates Assemblies", available in the .NET Framework SDK help or in MSDN.

-6304

Error validating with CUB file "%1".

Ensure that the CUB file is valid.

-6303

Internal build error

Check the Knowledge Base for information about this error, or request technical support.

-6302

InstallShield could not resolve Visual Studio .NET project output "%1" from component "%2". You need to build the project in Visual Studio .NET or by using the Visual Studio .NET command line: devenv /build ConfigName [/project ProjName] [/projectconfig ConfigName] SolutionName

Build the project in Microsoft Visual Studio or by using the Visual Studio command line.

-6274

Setup.exe is not found in the Disk1 location: %1. Please make sure that the previous full build of your release was completed if you are running the Build Tables Only.

This error occurs when the setup attempts to get the stamp from Setup.exe, but Setup.exe does not exist in the Disk1 folder. This happens when you cancel a full build in the middle of the process, and then run the Build Tables Only option.

-6273

A VB Script custom action exists in the project, but the VBScriptRuntime Merge Module has not been included.

Use the Redistributables view to add the VBScriptRuntime merge module to your project.

-6271

File %1 not found. An error occurred building the MsiFileHash table record for this file. Verify that the file exists in the specified location.

Ensure that the identified file exists in the specified location.

-6270

The record %1 in the Icon table exceeds the limit of %2 characters. As a result, the build will be unable to persist the database.

Make sure that the record is at or under the limited number of characters.

-6269

An error occurred copying directory %1 to %2. Please ensure that the source directory's path is correct.

Check the source directory's path.

-6268

Internal build error

Check the Knowledge Base for information about this error, or request technical support.

-6267

An error occurred while extracting files from the cab file %1 to the location %2

Ensure that the location is accurate.

-6266

An error occurred while attempting to create and initialize the CAB extraction engine for %1

This error can occur when one or more files is not registered. Ensure that all files are registered.

-6265

An error occurred building feature '%1'. This feature has the same name (with different case) as another feature in the project. Duplicate feature names are not allowed in InstallScript MSI projects. Rename one of the features to fix this error.

Remove or rename one of the features.

-6264

A record in the %1 table is using string ID '%2' for column '%3' but this string is blank and the column is not nullable.

Provide a string for use in the column.

-6263

The number of allowed InstallScript custom actions (1000) has been exceeded. Please remove some InstallScript custom actions and rebuild the setup.

This error appears when a Basic MSI, DIM, InstallScript MSI, or Merge Module project has more than 1,000 InstallScript custom actions. Use the Custom Actions and Sequences view (or the Custom Actions view) to remove InstallScript custom actions so that your project no longer exceeds the maximum number allowed.

-6262

The Directory table contains the entry %1. This identifier is reserved. Defining it in the Directory table will yield unpredictable results at run time. Use the Direct Editor to rename this directory identifier.

Go to the Directory table in the Direct Editor and rename the directory identifier.

-6260

Internal build error

Check the Knowledge Base for information about this error, or request technical support.

-6259

Internal build error

Check the Knowledge Base for information about this error, or request technical support.

-6258

An error occurred extracting digital signature information from file "%1". Make sure the digital signature information provided in the IDE is correct.

Ensure that the digital signature information is correct. You can access the digital signature information in the Releases view or in the Release Wizard's Digital Signature panel.

-6257

The build engine has detected that PRODUCT_NAME has been defined in the string table. At run time, your setup will display this value as your Product Name instead of the Product Name values defined in the IDE.

This warning message occurs when the ID PRODUCT_NAME has been defined in the String Editor view. This string identifier overrides the Product Name values set in the General Information view or for the product configuration in the Releases view.

-6255

Internal build error

Check the Knowledge Base for information about this error, or request technical support.

-6254

An error occurred building the MsiFileHash table for File %1

Check the Knowledge Base for information about this error, or request technical support.

-6253

Internal build error

Check the Knowledge Base for information about this error, or request technical support.

-6252

Internal build error

Check the Knowledge Base for information about this error, or request technical support.

-6251

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6250

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6249

Component %1 is configured to install to the Global Assembly Cache but includes one or more subdirectories.

This error occurs when you are using a .NET Project Output that includes subdirectories. InstallShield does not currently support installing these files to the Global Assembly Cache. To avoid this error, change the directory for the component (for example, to INSTALLDIR), or statically add the files and configure them.

-6248

Could not find dependent file %1, or one of its dependencies of component %2

Use the "Build Tables & Refresh Files" option to build the release if the release location is in <ISProjectDataFolder> or <ISProjectFolder>. For more information, see "How the Run time Locates Assemblies", available in the .NET Framework SDK help or on MSDN.

-6247

The .NET Framework redistributable %1 is not found on the system. %2

Check the Knowledge Base for information about this error, or request technical support.

If you have the Visual Studio release candidate, you can copy dotnetfx.exe from Windows Component Update CD, in the dotnetframework directory, to [ProgramFilesFolder]InstallShield\2012Spring\Redist\0409\i386.

-6246

Could not add dotnetfx.exe to the built image. If you are including .NET 1.1, make sure a core language is selected.

Check the Knowledge Base for information about this error, or request technical support.

-6245

One or more of the project's components contain .NET properties that require the .NET Framework. It is recommended that the release include the .NET Framework.

Consider adding the .NET Framework redistributable to your project. If the .NET Framework is not present on the target system at run time, the installation installs it. To learn more, see Adding .NET Framework Redistributables to Projects.

-6244

One or more of the project's components contain .NET properties that require the .NET Framework. However, the .NET Framework cannot be detected. %2

Check the Knowledge Base for information about this error, or request technical support.

If you have the Visual Studio release candidate, you can copy dotnetfx.exe from Windows Component Update CD, in the dotnetframework directory, to [ProgramFilesFolder]InstallShield\2012Spring\Redist\0409\i386.

-6243

InstallUtilLib.dll cannot be located on your system. This file is required for Installer custom actions. You can set the path to InstallUtilLib.dll using Tools | Options. The file is part of the Microsoft .NET Framework redistributable. %1

Set the path to InstallUtilLib.dll by selecting Options from the Tools menu and clicking the .NET tab.

-6242

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6241

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6240

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6239

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6238

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6237

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6236

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6235

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6234

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6233

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6232

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6231

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6230

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6229

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6228

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6227

.NET scan of Component %1 failed

Check the Knowledge Base for information about this error, or request technical support.

-6226

Opening Visual Studio .NET solution

Make sure that the solution exists at the location specified. To find the solution information, navigate to the InstallShield table in the Direct Editor and find the value for ISDotNetSolution.

In addition, ensure that Visual Studio is installed on the build machine.

-6225

Resolving Visual Studio .NET project output "%1"

Make sure the project exists in the solution. To find the solution information, navigate to the InstallShield table in the Direct Editor and find the value for ISDotNetSolution. In addition, ensure that project has the specified output.

-6224

Processing merge module %1 of feature %2

Check the Knowledge Base for information about this error, or request technical support.

-6223

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6222

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6221

Could not resolve Visual Studio .NET project output "%1" from component %2

Make sure the project exists in the solution. To find the solution information, navigate to the InstallShield table in the Direct Editor and find the value for ISDotNetSolution. In addition, ensure that project has the specified output.

-6220

Dynamically acquired %1 data conflicts with static data associated with component %2. Overwriting with dynamic data.

This error occurs when manual entries made to the MsiAssembly and MsiAssemblyName tables conflict with .NET assembly properties that result from scanning. To eliminate this error, set the component's .NET Scan at Build property to None or delete the values that were manually added to the MsiAssembly and MsiAssemblyName tables.

-6219

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6218

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6217

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6216

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6215

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6214

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6213

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6212

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6211

Destination of Component %1 is GlobalAssemblyCache but key file is not a .NET assembly

Check the Knowledge Base for information about this error, or request technical support.

-6210

An error occurred building COM .NET Interop information for Component %1

InstallShield calls regasm.exe on the .NET .dll to create a .reg file. This should create a .reg file. Then, the .reg file is imported. If either of these steps fails, error -6210 occurs. Make sure that the component's key file is a .NET .dll and that the .NET assembly has "types to export".

-6209

Regasm.exe cannot be located on your system. This file is required to obtain .NET COM Interop information for Components. You can set the path to Regasm.exe using Tools | Options. The file is part of the Microsoft .NET Framework redistributable. %1

Set the path to Regasm.exe by selecting Options from the Tools menu and clicking the .NET tab.

-6208

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6207

An error occurred building Setup File %s.

Check the Knowledge Base for information about this error, or request technical support.

-6205

An error occurred building Component %1. The Component's destination directory %2 is not found in the directory table. Change the Component's destination to a valid location.

Check the Knowledge Base for information about this error, or request technical support.

-6204

An error occurred importing %1 for Component %2. Make sure the file exists in the specified location and that the file is a valid REG file.

Check the Knowledge Base for information about this error, or request technical support.

-6203

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6202

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6201

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6200

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6199

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6197

An error occurred streaming %1 into %2. Check to make sure the .msi package is not currently in use by another process.

Ensure that the .msi package is not currently being used by another process.

-6196

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6195

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6194

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6193

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6192

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6191

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6190

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6189

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6188

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6187

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6186

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6185

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6184

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6183

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6182

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6181

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6180

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6179

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6178

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6177

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6176

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6175

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6174

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6173

An error occurred renaming file %1 to %2

Make sure that you have enough free hard disk space on the drive that contains the interim folder under your product configuration (for example, \MySetups\Your Project Name-27\Product Configuration 1\Interm).

-6172

An error occurred while creating a CAB file. For incremental compressed builds, make sure your project includes at least one file or rebuild your media.

Make sure that your project includes at least one file or rebuild your media.

-6171

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6170

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6169

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6168

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6167

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6166

An error occurred updating the Word Count Summary Property of the Summary Information Stream.

Check the Knowledge Base for information about this error, or request technical support.

-6165

An error occurred exporting table %1.

Check the Knowledge Base for information about this error, or request technical support.

-6164

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6163

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6162

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6161

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6160

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6159

The data type for a column in a table in the source project is incompatible with that of the target database.

Use the Direct Editor to ensure the data type is correct in the specified column and table.

-6158

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6157

Target field in table is too small for data.

Use the Direct Editor to ensure the data can fit in the allocated table field.

-6156

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6155

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6154

Build canceled by the user.

This error occurs only when the build is terminated during the build process.

-6153

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6152

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6151

Cannot save target database.

Check the Knowledge Base for information about this error, or request technical support.

-6150

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6149

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6148

Cannot insert record in the specified table.

Check the Knowledge Base for information about this error, or request technical support.

-6147

Cannot update the specified target field in the table.

Check the Knowledge Base for information about this error, or request technical support.

-6146

Cannot create new record in the specified table.

Check the Knowledge Base for information about this error, or request technical support.

-6145

Cannot retrieve value of the specified column in the table.

Check the Knowledge Base for information about this error, or request technical support.

-6144

Cannot open database view for table %1.

Check the Knowledge Base for information about this error, or request technical support.

-6143

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6142

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6141

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6140

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6139

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6138

Error compiling Setup.rul.

Setup.rul is required for the project. Check to ensure that this file is included in the project.

-6137

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6136

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6135

The specified feature is not associated with any Setup Type.

Associate the specified feature with a Setup Type.

-6134

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6133

An error occurred updating properties specified in the current Product Configuration.

Check the properties specified in the current Product Configuration to ensure they are valid.

-6132

Error Building the Storages table.

Use the Direct Editor to verify that the data in the table is correct.

-6131

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6130

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6129

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6128

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6127

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6126

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6125

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6124

Unknown Exception.

Check the Knowledge Base for information about this error, or request technical support.

-6123

Unknown Exception.

Check the Knowledge Base for information about this error, or request technical support.

-6122

No components are included in the build.

Ensure your build contains at least one component.

-6121

Error occurred copying built merge modules to the Modules folder.

Check the Knowledge Base for information about this error, or request technical support.

-6120

The Resource Linker failed to build the specified DLL.

Check the Knowledge Base for information about this error, or request technical support.

-6119

The resource linker could not be found.

Open the Options dialog, available from the Tools menu, and set a location to a Resource linker.

-6118

The Resource compiler failed to build the specified RES file required to link the DLL.

Check the Knowledge Base for information about this error, or request technical support.

-6117

The resource compiler could not be found.

Open the Options dialog, available from the Tools menu, and set a location to a Resource compiler.

-6116

Failed to export .rc file from project: %1.

Check the Knowledge Base for information about this error, or request technical support.

-6115

Unable to retrieve version information from ISSetup.dll.

This error may occur if the ISSetup.dll file in the following location is corrupted, or if it has been removed from the build machine. This file should be in the following location:

InstallShield Program Files Folder\redist\Language Independent\i386

To resolve this error, try running a repair of InstallShield.

-6114

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6113

An error occurred during the incremental build.

Check to ensure that a previous media was built before selecting "Build Tables Only" or "Build Tables and Refresh Files" and ensure the previous media was not deleted.

-6112

Error deleting a file streamed into Setup.exe.

Check the Knowledge Base for information about this error, or request technical support.

-6111

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6110

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6109

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6108

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6107

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6106

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6105

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6104

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6103

Unable to get system settings for the specified file.

Check the file to ensure it exists in the specified location.

-6102

Error searching for dynamic files matching "%1".

Make sure the dynamic file flag specified is valid.

-6101

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6100

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6099

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6098

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6097

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6096

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6095

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6094

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6093

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6092

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6091

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6090

The scrollable text file:'%1' specified for the Control:'%2' does not exist.

Check to make sure the text file exists in the specified location %1 will contain the full path to an .rtf file. If it is empty, the ISBuildSourcePath column for control %2 is empty. For Scrollable text controls, ISBuildSourcePath in the Control table should point to a valid file.

-6089

Both the Text and ISBuildSourcePath columns for Control:'%1' contain path information, the Text column will be used.

The Control %1 cannot have entries in both ISBuildSourcePath and the Text columns of the Control table. Go to the Direct Editor and remove the unused information in either ISBuildSourcePath or Text column.

-6088

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6087

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6086

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6085

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6084

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6083

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6082

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6081

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6080

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6079

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6078

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6077

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6076

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6075

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6074

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6073

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6072

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6071

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6070

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6069

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6068

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6067

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6066

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6065

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6064

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6063

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6062

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6061

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6060

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6059

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6058

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6057

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6056

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6055

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6054

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6053

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6052

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6051

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6050

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6049

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6048

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6047

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6046

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6045

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6044

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6043

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6042

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6041

Internal build error.

This build error can occur if a project includes support for multiple languages and if the release is configured to remove unused directories from the Directory table of the .msi package.

To resolve this error:

1. In the View List under Media, click Releases.
2. In the Releases explorer, click the release that you were building when you encountered this error.
3. Click the Build tab.
4. For the Keep Unused Directories setting, select Yes.

For more information, see Build Tab for a Release.

-6040

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6039

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6038

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6037

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6036

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6035

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6034

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6033

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6032

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6031

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6030

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6029

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6028

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6027

InstallShield cannot convert the value of the ISBuildSourcePath column in the File table for the Visual Studio .NET output files. InstallShield is not running within Visual Studio .NET.

OR

InstallShield cannot convert the value of the ISBuildSourcePath column in the File table for the Visual Studio .NET output files. The opened Visual Studio .NET solution name is different from the solution name stored in the .ism project.

Run the upgrade from within Microsoft Visual Studio to avoid this warning.

OR

Open the .ism project within the same solution when creating it in InstallShield.

-6026

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6025

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6024

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6023

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6022

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6021

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6020

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6019

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6018

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6017

The build was unable to extract COM information; make sure that you are running as Administrator.

Extracting COM information in InstallShield requires administrative privileges. For more information, see Launching InstallShield with vs. Without Administrative Privileges.

-6016

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6015

Error generating short file name for file: %1.

Check the Knowledge Base for information about this error, or request technical support.

-6014

The shortcut for a component is invalid because it does not reference an icon resource.

Specify an icon file and icon index for this shortcut to resolve this issue.

-6013

The component condition for the specified component is invalid.

Use the Components view to modify the condition property of the specified component.

-6012

Failed to set codepage for language %1.

Install the codepage for the specified language.

-6011

Failed to open string table.

Check the Knowledge Base for information about this error, or request technical support.

-6010

An error occurred digitally signing media for Netscape.

Verify the digital signature information provided in the current Release to sign the Netscape media (Netscape Certificate ID, Password, and Certificate Path) is correct.

-6009

An error occurred creating the Web media for Internet Explorer.

Check the Knowledge Base for information about this error, or request technical support.

-6008

An error occurred creating the Web media for Internet Explorer.

Check the Knowledge Base for information about this error, or request technical support.

-6007

Error occurred copying user specified uncompressed support files to Disk1.

Check the Knowledge Base for information about this error, or request technical support.

-6006

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-6005

An error occurred creating the Package Definition File.

Check the Knowledge Base for information about this error, or request technical support.

-6004

An error occurred streaming the digital certificate for Msi engine(s) into setup.exe.

Check the Knowledge Base for information about this error, or request technical support.

-6003

An error occurred streaming '%1' into setup.exe.

Check the Knowledge Base for information about this error, or request technical support.

-6002

Error while attempting to run the custom build setup for objects.

Check the Knowledge Base for information about this error, or request technical support.

-6001

An Error occurred while preprocessing ISObjectProperty. Make sure that ll items have a valid IncludeInBuild tag.

Check the Knowledge Base for information about this error, or request technical support.

-6000

An Error occurred gathering information about supplemental merge modules.

Check the Knowledge Base for information about this error, or request technical support.

-5099

An error occurred creating the build report.

Check the Knowledge Base for information about this error, or request technical support.

-5098

The Directory table contains a circular reference.

Check the Knowledge Base for information about this error, or request technical support.

-5097

Could not write custom records to the _Validation table.

Check the Knowledge Base for information about this error, or request technical support.

-5096

Could not retrieve the standard table list.

Check the Knowledge Base for information about this error, or request technical support.

-5095

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5094

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5093

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5092

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5091

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5090

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5089

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5088

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5087

Stop at first error.

The user chose the "Stop build process when first error is encountered" in Tools | Options menu. An error occurred so the build was stopped.

-5086

Treat warnings as errors.

Check the Knowledge Base for information about this error, or request technical support.

-5085

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5084

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5083

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5082

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5081

Could not write to setup.ini.

Check the Knowledge Base for information about this error, or request technical support.

-5080

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5079

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5078

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5077

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5076

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5075

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5074

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5073

The binary key %1 is missing.

Open the Binary table in the Direct Editor to verify that this entry exists.

-5072

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5071

Standard DLL Function syntax error.

Make sure you specify void if your function does not return anything. Click the ellipsis button (...) in the Function Signature field of the Custom Action to validate your signature.

-5070

Standard DLL Function Name syntax error.

Click the ellipsis button (...) in the Function Signature field of the Custom Action to validate your signature.

-5069

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5068

Standard DLL Function parameters syntax error.

Click the ellipsis button (...) in the Function Signature field of the Custom Action to validate your signature

-5066

Standard DLL Function return value syntax error.

Click the ellipsis button (...) in the Function Signature field of the Custom Action to validate your signature

-5065

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5064

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5063

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5062

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5061

The specified filename already exists.

Use the component's Source Location property to prevent this warning.

-5060

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5059

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5058

Could not obtain merge module dependencies.

Check the Knowledge Base for information about this error, or request technical support.

-5057

Could not obtain merge module catalog.

Check the Knowledge Base for information about this error, or request technical support.

-5056

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5054

Could not determine the size of the file "%1".

Verify the file specified exists.

-5053

The file "%1" could not be found.

Verify the file specified exists.

-5052

Could not determine the free space on the volume %1.

Check the Knowledge Base for information about this error, or request technical support.

-5051

Could not remove the read-only attribute from the file "%1".

Check the Knowledge Base for information about this error, or request technical support.

-5050

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5049

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5048

Could not create the file "%1".

Check the Knowledge Base for information about this error, or request technical support.

-5047

Cannot create directory %1.

Check the Knowledge Base for information about this error, or request technical support.

-5046

Could not preserve previous Build Reports.

This build error occurs when a release exists, but the corresponding Report Files folder in the release folder does not exist. This scenario typically occurs if you manually delete the Report Files folder, but not the disk image folder. This scenario may also occur if you upgrade a project from an earlier version of InstallShield.

To resolve this error, click the Open Release Folder button. InstallShield opens the current release's folder. Delete all of the files within the folder. Then rebuild the release.

-5045

Could not preserve previous Build Logs.

This build error occurs when a release exists, but the corresponding Log Files folder in the release folder does not exist. This scenario typically occurs if you manually delete the Log Files folder, but not the disk image folder. This scenario may also occur if you upgrade a project from an earlier version of InstallShield.

To resolve this error, click the Open Release Folder button. InstallShield opens the current release's folder. Delete all of the files within the folder. Then rebuild the release.

-5044

Cannot delete directory %1.

Check the Knowledge Base for information about this error, or request technical support.

-5043

The volume does not exist.

Check in the Releases view to ensure the volume specified exists.

-5042

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5041

The string ID "%1" was used to specify a Component or Feature destination.

You cannot use a stringID for a destination. Find the component or feature using this string ID and change the destination using a directory identifier.

-5040

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5039

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5038

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5037

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5036

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5033

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5032

Error building ListView table.

Use the Direct Editor to verify that the data in the table is correct.

-5031

Error building ListBox table.

Use the Direct Editor to verify that the data in the table is correct.

-5030

Error building ComboBox table.

Use the Direct Editor to verify that the data in the table is correct.

-5029

Error building CheckBox table.

Use the Direct Editor to verify that the data in the table is correct.

-5028

Error building RadioButton table.

Use the Direct Editor to verify that the data in the table is correct.

-5027

Error building Control table.

Use the Direct Editor to verify that the data in the table is correct.

-5026

Error building Dialog table.

Use the Direct Editor to verify that the data in the table is correct.

-5025

Could not save package.

Check the Knowledge Base for information about this error, or request technical support.

-5024

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5023

Error building File table.

Use the Direct Editor to verify that the data in the table is correct.

-5022

Error building Feature table.

Use the Direct Editor to verify that the data in the table is correct.

-5021

Error building Component table.

Use the Direct Editor to verify that the data in the table is correct.

-5020

Error building Directory table.

Use the Direct Editor to verify that the data in the table is correct.

-5019

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5018

The logical disk does not contain any features.

Check the Knowledge Base for information about this error, or request technical support.

-5017

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5016

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5015

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5014

An error occurred building icon "%1". The specified Icon key was not found in the Icon table.

See Knowledge Base article Q107116 for information about this error.

-5013

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5012

Invalid Feature_ value for %1.

Use the Direct Editor to open the specified table and ensure data in that table is valid.

-5011

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5010

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5009

The schema Summary Stream must be 200 or later.

Check the Knowledge Base for information about this error, or request technical support.

-5008

Intel64 must be specified in the template of the Summary Stream.

Check the Knowledge Base for information about this error, or request technical support.

-5007

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5006

Could not save "%1".

Check the Knowledge Base for information about this error, or request technical support.

-5005

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5004

Could not open the project with write access.

Check to make sure the project is not already open by the IDE.

-5003

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5002

Internal build error.

Check the Knowledge Base for information about this error, or request technical support.

-5001

Could not copy setup.ini.

Check the Knowledge Base for information about this error, or request technical support.

-4701

An error occurred building the One-Click Install Web page.

Check the Knowledge Base for information about this error, or request technical support.

-4371

There were warnings compiling InstallScript.

Use the InstallScript Debugger to step through your InstallScript to identify problems.

-4370

There were errors compiling InstallScript.

Use the InstallScript Debugger to step through your InstallScript to identify problems.

-4354

The build was unable to extract COM information from a file in a component.

Ensure that the file is self-registering and verify that the self-registration process does not fail.

-4352

There is no key file for the specified component. A key file is required for dynamic COM extraction.

Specify the key file for the specified component from the Components view.

-4350

Dynamically acquired MIME text/scriptlet conflicts with static data associated with component %1. Overwriting with dynamic data.

This warning occurs when you add a COM server .dll file using the Component Wizard, which does static COM extraction, and then later change the component's COM Extract at Build setting to Yes. The dynamically extracted data conflicts with the static data in the .ism file. Ensure that the COM extraction setting is accurate.

-4349

Failed to build %1 information for dynamically extracted COM components.

Check the Knowledge Base for information about this error, or request technical support.

-4348

Failed to build %1 information for dynamically extracted COM components.

Check the Knowledge Base for information about this error, or request technical support.

-4347

Failed to build information for dynamically extracted COM components.

Check the Knowledge Base for information about this error, or request technical support.

-4346

Failed to build information for dynamically extracted COM components.

Check the Knowledge Base for information about this error, or request technical support.

-4345

Failed to build information for dynamically extracted COM components.

Check the Knowledge Base for information about this error, or request technical support.

-4344

Failed to build information for dynamically extracted COM components.

Check the Knowledge Base for information about this error, or request technical support.

-4343

Failed to build information for dynamically extracted COM components.

Check the Knowledge Base for information about this error, or request technical support.

-4340

Failed to initialize COM extraction module.

Check the Knowledge Base for information about this error, or request technical support.

-4327

Could not write string ID "%1" to the InstallScript strings file.

This error pertains to projects containing InstallScript (either an InstallScript MSI project or a Basic MSI project with InstallScript custom actions). At build time, InstallShield creates an .ini file that contains all of the string entries in the project. In the error message, "%1" represents the line number in this .ini file that fails to get written. If the line number is 0, a general failure to create or write to the .ini file occurred. This might indicate that you are out of disk space.

-4303

An unexpected error occurred while synchronizing the file key in the specified component.

Check the Knowledge Base for information about this error, or request technical support.

-4302

A conflict was encountered while synchronizing file key %1 in component %2.

Check the Knowledge Base for information about this error, or request technical support.

-4301

Could not find the .msi file for key synchronization.

Check to ensure the specified MSI file exists.

-4093

Cannot copy source %1 to target %2

Ensure that the file exists, that there is enough disk space on the target location, and that you are able to copy to the location.

-4092

Error opening MSI database %1.

Check the Knowledge Base for information about this error, or request technical support.

-4075

File not found. An error occurred merging module '%1' for feature '%2'.

Verify that the merge module exists in the merge module search path.

This error may occur if an installation project that contained an InstallScript MSI object was upgrade to InstallShield 2012 Spring, which no longer supports InstallScript MSI objects. If this is the case, remove that objects from your project through the Redistributables view. You can upgrade the InstallScript MSI object to InstallShield 2012 Spring, which will convert it to a merge module project. Then you can add that merge module to your installation project.

-4072

Error retrieving the dependencies for %1.

Check the Knowledge Base for information about this error, or request technical support.

-4006

Cannot delete file.

Ensure the specified file exists and is not set to read-only.

-3876

Ignoring invalid template %1 in the Summary Stream.

InstallShield generates this warning if the Template Summary setting contains an invalid entry. To learn about how to enter valid values, see Using the Template Summary Property.

-3851

Error building the specified table.

Use the Direct Editor to open the specified table and ensure data in that table is valid.

-3713

The function block must be in the form "Module::Function".

Change the function block to follow the form "Module::Function".

-3204

Cannot extract icon with specified index from the file specified for the icon.

Ensure the file containing the icon exists, and the index number is present in the file.

-3138

The Patch Configuration specified does not exist in the project. Please verify that the Patch Configuration exists and that the spelling and character case match.

When using the BuildPatchConfiguration method on the IPWiProject object, this error might occur.

-3114

Application path %1 does not contain destination of associated component %2.

This error occurs when an application path entry was created in the Advanced Settings section of the Components view, but no application path was specified. To correct this, set the application path entry.

Because an application path is also a registry entry, this error might occur if a registry path like the following one is created, but it is missing the path entry:

HKEY_LOCAL_MACHINE\Microsoft\Windows\CurrentVersion\App Paths

To correct this, specify a path entry.

-3028

An error occurred replacing string IDs in the specified table.

A required string ID was left blank in the specified table. Provide a string ID.

-3016

Failed to add Binary table %1 to package.

Check the Knowledge Base for information about this error, or request technical support.

-2200

Could not overwrite file.

Ensure the specified file is not read-only.

-1531

The size specified for the disk is too small for the feature.

Using the Release Wizard, change the Media Format to a larger size.

-1530

The size specified for the disk is too small for the file.

Using the Release Wizard, change the Media Format to a larger size.

-1527

No files are included in the project.

This warning occurs when you have not included any files in your project. Use the Files and Folders view to add files into your project to avoid this error.

-1505

Could not add the CAB file to the MSI package.

Check the Knowledge Base for information about this error, or request technical support.

-1501

Could not compress "%1" into "%2".

Ensure that IsCmdBld.exe is executed in the relative directory. You can do this by locating the files specified in the error message and launching IsCmdBld.exe within their directory.

-1119

The specified CUB file does not exist.

Ensure that the CUB file name is spelled correctly.

-1027

Failed signing %1.

Check the digital signature information (digital keys and password) provided for the current release.

-1024

File not found. Cannot stream the file into the Binary table.

Ensure the specified file exists.

-1015

Cannot copy source '%1' to target %2.

Check the Knowledge Base for information about this error, or request technical support.

-1014

Cannot rename a directory.

Windows Explorer or a DOS prompt may be pointing to a subfolder of the release output folder (Disk1) or to the Interm folder, locking it. Change the current directory. Close any open files in the Disk1 folder. Close Msidb.exe if it is open.

-1013

The specified file is being used by another program.

Close the application that is currently using the file and re-run the build process.

-1009

Insufficient disk space or the target drive cannot be located.

Increase disk space on the build target, or select a new target for the build. If the target drive cannot be located, select a new target, or ensure permissions are set correctly for the target drive.

-1007

Cannot copy source %1 to target %2

Ensure that the file exists, that there is enough disk space on the target location, and that you are able to copy to the location.

-1005

Could not compress %1 into %2 (where %1 is the full path to a file and %2 is the name of a .cab file).

This error could occur when you are building a compressed setup and run out of disk space or temporary space on the machine. Another reason that this error might occur is due to an internal error occurred with the CAB APIs. Contact technical support for more information.

-1001

Error opening MSI database.

Check the Knowledge Base for information about this error, or request technical support.

-1000

Invalid product configuration. Failed to create directory.

Check the Knowledge Base for information about this error, or request technical support.

See Also