InstallShield 2019
This table provides tips for troubleshooting errors and warnings that may occur when you upgrade a project (.ism file) created using a version of InstallShield—Windows Installer Edition to InstallShield.
|
Error or Warning Number |
Message |
Troubleshooting Tips |
|
-100 |
This error occurs if you are upgrading a project that has a registry value set as a keypath for a component. |
You cannot set a registry value as a keypath for a component. To avoid this error, remove that keypath from the component and attempt the upgrade again. |
|
-201 |
This error occurs if your project contains a component with duplicate file names in it. The upgrader keeps only one of these files and deletes the rest. |
To avoid this problem, make sure that you do not have duplicate file names within the same component. |
|
-2007 -2011 -2121 -2122 |
These errors occur if the upgrader cannot read information from the old table structure, or it cannot write information to the new table structure. |
Once the file has been upgraded, you need to navigate to the areas that failed and reinsert your settings. |
|
-6020 |
The scripting billboard is no longer supported in the Basic MSI project. This property is not being upgraded. |
To add support for this property after your project is upgraded, you can convert your project to an InstallScript MSI project and add your billboards in the Support Files/Billboards view. |
|
-6021 |
The path variable cannot contain apostrophes, which are invalid characters. The name is being changed. |
To build your project successfully, update all references to this path variable after the project is upgraded. |
|
-6022 |
Could not open the MSI file specified in a custom action. The source property is not being converted. |
To build your project successfully, enter the product code of the MSI file in the custom action’s Source property after the project is upgraded. |
|
-6023 |
The necessary code page is not installed on your system. The associated string table values are not being upgraded correctly. |
Install the appropriate code page prior to project upgrade. |
|
-6026 |
This error occurs if you have a user-defined path variable in your InstallShield—Windows Installer Edition project that is the same as a predefined path variable in InstallShield. |
To upgrade successfully, remove the user-defined path variable in the InstallShield—Windows Installer Edition project and upgrade your project to InstallShield. After upgrading, open your project in InstallShield and create a new path variable that is equivalent to the user-defined path variable. Update all references in the InstallShield project. |
|
-6031 |
The property name "sOldPropertyName" contains invalid characters. The name is being changed to "sNewPropertyName." To build your project successfully, update all references to that property name after your project is upgraded. |
After your project upgrades, change all references to the old property name to the new property name. |
See Also
Upgrading Projects Created with InstallShield—Windows Installer Edition
InstallShield 2019 Help LibraryApril 2019 |
Copyright Information | Flexera |