Build Errors and Warnings
InstallShield 2020 Express Edition
The table below provides troubleshooting tips for each build error and warning.
|
Error |
Description |
Troubleshooting Tips |
||||||||||||
|
-32000 |
Build canceled by the user. |
This error occurs only when the build is terminated during the build process. |
||||||||||||
|
-7347 |
InstallShield does not support signing with .spc and .pvk files. Replace the digital certificate information in your project with a .pfx certificate, or with a reference to a certificate in a certificate store. |
This error occurs if you added .spc and .pvk files to your project in an earlier version of InstallShield that included support for digitally signing with those files, and then you open your project in InstallShield 2020 Express Edition and attempt to build a release or a patch. To resolve this error, remove the .spc reference from the release or QuickPatch project. You can replace it with a .pfx certificate, or with a reference to a certificate in a certificate store. To learn more, see:
|
||||||||||||
|
-7346 |
The files in this release are being signed with a SHA-1 certificate. Windows will not trust files that were signed with SHA-1 certificates if they were signed after January 1, 2016. |
This warning occurs if your project is configured to use a SHA-1 certificate to digitally sign your release at build time. SHA-256 is favored over SHA-1, which is being deprecated because of the potential for security vulnerabilities. Thus, it is recommended that you replace any SHA-1 certificates in your InstallShield projects with SHA-256 certificates. In InstallShield, to replace a SHA-1 certificate with a SHA-256 certificate for signing your releases, use the Signing tab in the Releases view to replace the reference to the current certificate with one for a SHA-256 certificate. To learn more, 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 a certificate in a certificate store to digitally sign your release, InstallShield generates this build warning. To resolve this build warning, switch from a certificate in a certificate store to a .pfx file. If you do not need to have a digitally signed tag, you can ignore this warning. |
||||||||||||
|
-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. |
||||||||||||
|
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 exists in the media. |
|||||||||||||
|
-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:
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, which is available when you click the Express node 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:
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. |
||||||||||||
|
-7185 |
The %1 translation for string identifier %2 includes characters that are not available on code page %3. |
This error occurs if a string value that you entered for the specified language contains characters that are not available in that language’s code page. To resolve this error, use the Text and Messages view to edit the value of the string so that it uses characters from the appropriate code page. Edition:The Premier and Professional editions of InstallShield enable you to build releases that use UTF-8 encoding for the .msi database. The UTF-8 encoding supports characters from all languages simultaneously, enabling you to mix and match, for example, Japanese and German, or Russian and Polish, both in text shown to end users and in file names and registry keys. These mixed languages work correctly regardless of the current language of the target system. |
||||||||||||
|
-7184 |
The %1 column of the %2 table includes characters that are not available on code page %3: "%4" |
This error occurs if a part of your project contains characters that are not available in the code page for one or more target languages. To resolve this error, change the data that is described in the error message so that it uses characters from the appropriate code page. For example, if error message mentions the Shortcut table, consider changing the string in the Shortcuts/Folders view. Edition:The Premier and Professional editions of InstallShield enable you to build releases that use UTF-8 encoding for the .msi database. The UTF-8 encoding supports characters from all languages simultaneously, enabling you to mix and match, for example, Japanese and German, or Russian and Polish, both in text shown to end users and in file names and registry keys. These mixed languages work correctly regardless of the current language of the target system. |
||||||||||||
|
-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 InstallShield Support folder. It also may occur if the Setup.exe template is missing from the InstallShield Redist\Language Independent\i386 folder. To resolve this error, try running a repair of InstallShield. |
||||||||||||
|
-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. |
||||||||||||
|
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. |
|||||||||||||
|
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 view. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Could not create XML reading object (MSXML3.dll). Please make sure this file is registered on the system. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
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 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. |
|||||||||||||
|
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. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
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. |
|||||||||||||
|
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. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
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. |
|||||||||||||
|
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. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
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. |
|||||||||||||
|
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. |
|||||||||||||
|
Initializing the default deployment manifest. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
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. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
An error occurred while loading the primary application assembly. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
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. |
|||||||||||||
|
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. |
|||||||||||||
|
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. |
|||||||||||||
|
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. |
|||||||||||||
|
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. |
||||||||||||
|
To include J# in the build you must also include .NET 1.1. |
J# requires the .NET Framework Redistributable Package version 1.1, but it is not included in the installation. If you are sure that your end users already have the .NET Framework 1.1 on their systems, you can ignore this warning message. However, if there is a chance that they will not have the .NET Framework 1.1, 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. |
|||||||||||||
|
Internal build error. |
This error occurs if a merge module 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. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
%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.
|
|||||||||||||
|
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. |
This error occurs if either of the following is true:
To resolve this build error, do one of the following:
|
|||||||||||||
|
The feature %1 in the installation contains more than 1600 components. There is a maximum limit of 1600 components per feature. |
To resolve this error, split up the feature that is identified in the error message into subfeatures, and then reassign the feature’s files to these subfeatures. |
|||||||||||||
|
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.” |
|||||||||||||
|
Cannot move file from '%1' to '%2' |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
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. |
|||||||||||||
|
%1 failed to load. Error: %2 Error Description: %3 |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
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. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
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. |
|||||||||||||
|
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. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Could not open the reference package '%1' for key synchronization. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
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. |
|||||||||||||
|
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. |
|||||||||||||
|
An error occurred while setting the key path for component '%1'. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Could not update File.FileName for File '%1'. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
|||||||||||||
|
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:
|
|||||||||||||
|
Unable to find the .NET Compact Framework for the given platform/processor combination from <InstallShield>\Support\NetCF.ini file. |
Ensure that the .NET Compact Framework is in the correct location. |
|||||||||||||
|
Error in including .NET Compact Framework .cab files in setup. |
This error might occur for the following reasons:
|
|||||||||||||
|
Unable to copy <InstallShield>\Support\CFAppMgr.ini file to a temporary location. |
Make sure that CFAppMgr.ini file exists at InstallShield Program 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. |
|||||||||||||
|
Unable to find the .NET Compact Framework .cab file for the processor. |
Open the InstallShield Program Files Folder\Support\NetCF.ini file and configure the .NET CF selection for this processor to resolve the issue. |
|||||||||||||
|
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. |
|||||||||||||
|
%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. |
|||||||||||||
|
Error processing setup [1] for Upgrade Item [2]. This does not appear to be a valid setup. |
This error occurs when an upgrade entry exists in the Upgrade Paths view, but the earlier installation that is specified does not exist in the location indicated. This can occur if the earlier installation has been moved because it was referenced in the Upgrade Paths view or if the folder that contains the earlier installation cannot be accessed because of permissions. This error can also occur if the earlier installation referenced (Setup.exe or .msi) is not a valid Windows Installer–based installation. |
|||||||||||||
|
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 be launched during the After Setup Complete Success dialog part of the installation. Otherwise the file will not exist on the target system when Windows Installer runs the custom action. |
|||||||||||||
|
-6499 |
The Shallow folder structure setting should not be used with multi-disk releases. |
The Shallow folder structure setting can be set from the Releases property grid of the Releases view. If error -6499 appears, switch the Shallow folder structure option to "No" so it will create a regular build folder structure. |
||||||||||||
|
-6479 |
Internal build error. |
A corrupted merge module in your project causes this error. The error message has been reported with third-party merge modules that are not shipped with InstallShield or merge modules that are shipped with the beta version of Microsoft Visual Studio .NET 2003. To resolve this error message, determine the merge module causing the issue and remove it from the project. To find the merge module, remove all merge modules from your project in the Redistributables view. Then add one merge module at a time to your project, and build the release until error -6479 occurs. This is the merge module causing the error. After you determine which merge module causes the issue, contact the vendor of the merge module for more information about the module. If the merge module is a Microsoft-specific module, download the latest service pack of Visual Studio to acquire the updated merge modules. If the merge module is Visual Studio .NET-specific, make sure that it is acquired from the latest service pack of Visual Studio .NET. |
||||||||||||
|
-6478 |
FON Files must have a Font Title. Font %1 in Feature %2. |
Set the Font Title property for the file. To do this, right-click the file in the Files view, select Properties, and type a title in the Font Title field. If there is no Font Title, a run-time error occurs upon installation. |
||||||||||||
|
-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. |
||||||||||||
|
-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. If the file includes the predefined path folder VSSolutionFolder, see Using the VSSolutionFolder Path Variable with Visual Studio Solutions. |
||||||||||||
|
-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 Standard 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. |
||||||||||||
|
-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 on the Signing tab in the Releases view. |
||||||||||||
|
-6257 |
The build engine has detected that PRODUCT_NAME has been defined in your project. At run time, your installation 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 table. This string table ID overrides the Product Name values set in the General Information view. Check article Q109136, "ERRDOC: Build Error -6257, in the Knowledge Base for information on how to resolve this error. |
||||||||||||
|
-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. |
||||||||||||
|
-6248 |
Could not find dependent file %1 of feature %2 |
The missing file is required by the feature’s key file. Make sure the missing file is on the build system in the same directory as the feature’s key file. If the dependency is not required, you can turn off .NET dependency scanning for the feature. To turn off dependency scanning, set the feature’s .NET Scan at Build property to None or Properties Only. |
||||||||||||
|
-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. |
||||||||||||
|
-6245 |
One or more of the project’s features contain .NET properties that require the .NET Framework. It is recommended that the release include the .NET Framework. |
Add the .NET Framework to your project by first selecting the media type in the Releases view. When you select the media type, the build properties are displayed. In the .NET Framework Location property, select the appropriate option:
In the .NET Framework Version property, select the .NET version that you want to distribute with your installation. |
||||||||||||
|
-6244 |
One or more of the project’s features contain .NET properties that require the .NET Framework. However, the .NET Framework cannot be detected. %2 |
Download the InstallShield .NET Update from http://www.installshield.com/products/dotnet.asp. If you have the Visual Studio release candidate, you can copy dotnetfx.exe from Windows Feature Update CD, in the dotnetframework directory, to InstallShield Program Files Folder\Redist\0409\i386. |
||||||||||||
|
-6243 |
InstallUtilLib.dll cannot be located on your system. |
This file is required for Installer custom actions. You may need to re-run the setup to (re)install the Microsoft .NET Framework redistributable. You can download this file from http://www.installshield.com/products/dotnet.asp, or you can copy dotnetfx.exe from Windows Feature Update CD, in the dotnetframework directory, to InstallShield Program Files Folder\Redist\0409\i386 (if you have the Visual Studio release candidate). |
||||||||||||
|
-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 Feature %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. 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. 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 feature %2 |
Make sure the project exists in the solution. In addition, ensure that project has the specified output. |
||||||||||||
|
-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 Feature %1 is GlobalAssemblyCache but key file is not a .NET assembly |
Check the Knowledge Base for information about this error, or request technical support. |
||||||||||||
|
-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 Feature %1. The Feature’s destination directory %2 is not found in the directory table. Change the Feature’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 Feature %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 |
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
||||||||||||
|
-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. |
||||||||||||
|
-6158 |
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
||||||||||||
|
-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. |
||||||||||||
|
-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. |
||||||||||||
|
-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 features are included in the build. |
Ensure your build contains at least one feature. |
||||||||||||
|
-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. |
||||||||||||
|
-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. |
||||||||||||
|
-6116 |
Failed to export .rc file from project: %1. |
Check the Knowledge Base for information about this error, or request technical support. |
||||||||||||
|
-6115 |
Could not retrieve version of IDriver.exe from ISScript.msi. |
Check the Knowledge Base for information about this error, or request technical support. |
||||||||||||
|
-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 |
Could not find file %1. |
Check the file to ensure it exists in the specified location. If the file includes the predefined path folder VSSolutionFolder, see Adding References to Visual Studio Solutions. |
||||||||||||
|
-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. |
This build error is caused by a scrollable text control that (1) is specified for the License Agreement dialog box or the Readme dialog box and (2) is not pointing to a valid .rtf file. To resolve this error message, open the Dialogs view, expand the Dialogs node, and then select the License Agreement node. Set the License File property to \Redist\0409\Eula.rtf. Then select the Readme node. Set the Readme File property to \Redist\0409\Readme.rtf. As an alternative, you can set the License File property or the Readme File property to your own file with the proper path. As long as the builder is able to find the file in the path specified in this property, the error should not occur. |
||||||||||||
|
-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. |
Check the Knowledge Base for information about this error, or request technical support. |
||||||||||||
|
-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 |
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
||||||||||||
|
-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 feature 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 feature condition for the specified feature is invalid. |
Use the Features view to modify the condition property of the specified feature. |
||||||||||||
|
-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. |
||||||||||||
|
-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 setup 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. |
||||||||||||
|
-5072 |
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
||||||||||||
|
-5071 |
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
||||||||||||
|
-5070 |
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
||||||||||||
|
-5069 |
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
||||||||||||
|
-5068 |
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
||||||||||||
|
-5066 |
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
||||||||||||
|
-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 feature’s Source Location property to prevent this error. |
||||||||||||
|
-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 Reports folder in the release folder does not exist. This scenario typically occurs if you manually delete the Reports 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 LogFiles folder in the release folder does not exist. This scenario typically occurs if you manually delete the LogFiles 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 Feature or Feature destination. |
You cannot use a stringID for a destination. Find the 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. |
||||||||||||
|
-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. |
||||||||||||
|
-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. |
For information about this error, see article Q105625 in the Knowledge Base. |
||||||||||||
|
-5013 |
Internal build error. |
Check the Knowledge Base for information about this error, or request technical support. |
||||||||||||
|
-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 |
This 32-bit package cannot include 64-bit data. The 64-bit data may come from a merge module. |
If your project does not have at least one file, folder, or registry entry that is configured to be installed to a 64-bit location, InstallShield attempts to create a 32-bit .msi package at build time; however, a 32-bit .msi package cannot contain a 64-bit merge module that contains one or more 64-bit components. To resolve this build error, consider the following options:
To learn more, see Challenges of Supporting Both 32-Bit and 64-Bit Target Operating Systems. |
||||||||||||
|
-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. |
||||||||||||
|
-4354 |
The build was unable to extract COM information from a file in a feature. |
Ensure that the file is self-registering and verify that the self-registration process does not fail. |
||||||||||||
|
-4349 |
Failed to build %1 information for dynamically extracted COM features. |
Check the Knowledge Base for information about this error, or request technical support. |
||||||||||||
|
-4348 |
Failed to build %1 information for dynamically extracted COM features. |
Check the Knowledge Base for information about this error, or request technical support. |
||||||||||||
|
-4347 |
Failed to build information for dynamically extracted COM features. |
Check the Knowledge Base for information about this error, or request technical support. |
||||||||||||
|
-4346 |
Failed to build information for dynamically extracted COM features. |
Check the Knowledge Base for information about this error, or request technical support. |
||||||||||||
|
-4345 |
Failed to build information for dynamically extracted COM features. |
Check the Knowledge Base for information about this error, or request technical support. |
||||||||||||
|
-4344 |
Failed to build information for dynamically extracted COM features. |
Check the Knowledge Base for information about this error, or request technical support. |
||||||||||||
|
-4343 |
Failed to build information for dynamically extracted COM features. |
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. |
||||||||||||
|
-4303 |
An unexpected error occurred while synchronizing the file key in the specified feature. |
Check the Knowledge Base for information about this error, or request technical support. |
||||||||||||
|
-4302 |
A conflict was encountered while synchronizing file key %1 in feature %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. |
||||||||||||
|
-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. |
||||||||||||
|
-4072 |
Error retrieving the dependencies for %1. |
Check the Knowledge Base for information about this error, or request technical support. |
||||||||||||
|
Failed to delete all of the files in a directory |
Close any open files in the build output directory (Disk1). Close Msidb.exe if it is open. |
|||||||||||||
|
-3876 |
Ignoring invalid template %1 in the Summary Stream. |
Check the Knowledge Base for information about this error, or request technical support. |
||||||||||||
|
-3713 |
The function block must be in the form "Module::Function". |
Change the function block to follow the form "Module::Function". |
||||||||||||
|
-3114 |
Application path %1 does not contain destination of associated feature %2. |
Check the Knowledge Base for information about this error, or request technical support. 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 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. |
||||||||||||
|
-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. |
||||||||||||
|
-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. |
||||||||||||
|
Error opening MSI database |
Your MSI engine may be corrupt. You need to repair or reinstall the engine. For further information, check article Q105892 in 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. |