Shop

AdminStudio
InstallShield
Advanced Installer
other products

InstallShield

InstallShield 2018
Neue Version mit Verbesserungen für IIS, XML, MSBuild, PowerShell, Suite Projekte, Prerequisites u.a.
Details hier

InstallShield und AdminStudio Schulungen

weitere Infos


 

Bugs Bulletin: InstallShield Developer 7.0

[ MSI Engine | MSMs | InstallShield 12 and newer | InstallShield 11.5 | DevStudio 9.0 | IS Dev 8.0 | IS Dev 7.0 | IPWI 2.0 | ISWI 1.x | IS Pro 7.x | IS Pro 6.x | IS Pro 5.x ]

[ ISD 7.04 | ISD 7.03 | ISD 7.02 | ISD 7.01 | ISD 7.00 ]

The problems listed on this page have been fixed in the latest maintenance release and are listed for reference.

InstallShield Developer 7.02

Version: 7.02 + Repackager patch + .NET Update
Release Date: December 15, 2001
Download: ISD 7.00 users select Update InstallShield from the Help menu. ISD 7.01 users select Check for Updates from the Tools menu. This is a patch package. The patch for repackager and the .NET Update can be obtained in the same way. These patches are not applicable to the German edition.
Release Notes: A list of enhancements, fixes and open issues is available at http://www.installshield.com/downloads/isd/isd_readme702.asp
Installation Notes: The ISD 7.02 patch is an update to ISD 7.00 and 7.01, do not uninstall the older version. After installing the patch you must re-install your language packs (from version 7.00 or 7.01).

Known Problems in ISD 7.02

Linking Error for iswi.obl

Description:
While compiling/linking a project in ISD 7.02 you may get an error message like this:
iswi.obl(MsiFuncsConv.obs) : error L8411: 'RedirectMsiRecordClearData' : no definition found for function.
Similar problems may exist for other APIs.
Workarounds:
Here is a fixed version of iswi.obl. Go to <InstallShield Developer directory>\Script\iswi, make a backup of the existing iswi.obl (it is a hidden, readonly file, so you need to enable "show hidden files" in Windows Explorer), and replace it with the content of this ZIP file.
ZIP ISD702HotFix.zip   Written by Mingbiao Fei (InstallShield Software Corp.)
File size: 64.221 bytes   Last update: 2001-12-21
Status:
This problem has been introduced with ISD 7.02. It is solved by the above mentioned hotfix.
FIXED in ISD 7.03.
Created: 2001-12-24   Last update: 2002-06-14    InstallShield tracking number: 1-70PRH

Error 1638 "Another version of this product is already installed" During Uninstall

Description:
When you try to uninstall your software using control panel you may receive error 1638: "Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel." This happens for projects generated by the VB Wizard.
Cause:
The VB Wizard doesn't generate a valid package code.
Workarounds:
Go to Summary Information Stream under General Information, select the Package Code field and press the Generate GUID button.
Status:
InstallShield has confirmed that this is a problem in ISD 7.02.
FIXED in ISD 7.03
Created: 2002-06-06   InstallShield tracking numbers: 1-7990O, 1-7CM05

Shortcuts Always Installed in All Users Profile

Description:
If your setup is executed by an Administrator, shortcuts to your application are always installed to the All Users start menu, even if he selected to install the software per-user (option "Only for me" on the CustomerInformation dialog). This happens with Basic MSI projects.
Cause:
The CustomerInformation dialog sets the ALLUSERS property to 0 if "only for me" is selected. However per documentation the property must be NULL (i.e. non-existent) to perform a per-user installation.
Workarounds:
Edit the Behaviour of the Next button on the CustomerInformation dialog to replace the 0 with {}. Emtpy curly braces {} can be used to undefine a property.
Status:
This problem has been reported for ISD 7.02.
FIXED in ISD 7.03.
Created: 2002-04-29   Last update: 2002-06-06   InstallShield tracking number: 1-7BBPM

Group Box Controls are Always Disabled

Description:
Adding a group box control will create it in disabled state by default. There is no way to enable it in the dialog editor. This only applies to Standard projects.
Workarounds:
Go to the Control table in Direct Editor and look for the Group Box you created on your custom dialog. By default the Attributes column is 1. One is for visible. Add 2 to the column. Two is for Enabled. See MSI help for more information about control attribute values.
Status:
InstallShield has confirmed that this is a bug in ISD 7.00 - 7.02.
FIXED in ISD 7.03
Created: 2001-10-15   Last update: 2002-06-06   InstallShield tracking number: 1-6PHD5, 1-6L0SX

Two Radio Buttons can be Selected at the Same Time in Media Build Wizard

Description:
In certain configurations, Media Build Wizard allows users to select two radio buttons in .Net Framework dialog at the same time. To reproduce the issue, do the following:
1. Open 'Releases' view, right-click on any release for any configuration and select 'Release Wizard'.
2. Follow Release Wizard prompts and define the following setting in Release Wizard dialogs:
3. In 'Filtering Settings' dialog, use default settings.
4. In 'Setup Languages dialog', use default settings.
5. In 'Media Type' dialog, select 'Network Image'.
6. In 'Release Configuration' dialog, select 'Compress All Files' (I think this is the key setting).
7. In 'Windows Installer Service' dialog, select all check boxes.
8. In 'Windows Installer Location' dialog, select 'Extract engine from Setup.exe'.
9. In 'InstallScript Engine' dialog, select 'Extract engine from Setup.exe'.
10. In 'Digital Signature' dialog, use default settings.
11. In 'Password & Copyright' dialog, use default settings.
12. Now you get to '.Net Framework' dialog with 'Copy from source media' option selected and disabled. However, despite the fact that it is disabled other buttons are enabled, so try to click any other radio button and you will get two radio buttons selected. If you do this, there is no way to unselect the second radio button (try to go back to the previous dialog and return). You are stuck.
Workarounds:
None.
Status:
This problem has been reported for ISD 7.02.
FIXED in ISD 7.03
Created: 2002-04-15   Last update: 2002-06-06   InstallShield tracking number: 1-78WLI

Renaming Release Changes Some of the Media Build Settings

Description:
If you rename configuration or release, 'Windows Installer Location' and 'InstallScript Engine' settings will be reset to default values. To duplicate the issue, do the following:
1. Open 'Releases' view, right-click on any release for any configuration and select 'Release Wizard'.
2. Follow Release Wizard prompts and make some changes from defaults to see whether they will persist (e.g. unselect some check boxes in 'Windows Installer Service' dialog).
3. When you get to 'Windows Installer Location' dialog, the default option must be set to 'Download engine from the Web'. Change it to 'Extract engine from Setup.exe'.
4. Do the same in the next (i.e. 'InstallScript Engine') dialog.
5. Complete the operation by building the release.
6. Repeat steps 1-5 to make sure that your settings persisted (including settings defined in steps 3 and 4).
7. Now, go back to 'Releases' view, right-click on release you just built and select 'Rename' from the menu. Confirm the operation and change release name.
8. Repeat steps 1-5 using the release you just renamed. Notice that release kept all of the settings you specified before except the settings defined in steps 3 and 4, which are changed back to 'Download engine from the Web'.
Workarounds:
Check and re-set your release options after renaming a release.
Status:
This problem has been reported for ISD 7.02.
FIXED in ISD 7.03
Created: 2002-04-15   Last update: 2002-06-06   InstallShield tracking number: 1-78WLR

IDE Crashes While Searching in Direct Editor

Description:
IS Developer crashes when performing a "Find" in the "Direct Editor". This happens when the scan reaches the "ISString" table. Sometimes ISDev just exits without any warnings, and sometimes you get the following error: "The exception unknown software exception (0xc00000fd) occurred in the application at location 0x77e84887." This happens if your project has a great number of string table entries (e.g. more than 6000) while searching for a string that doesn't exist in the project.
Workarounds:
Open the MSI file in Orca and use Orca's Find function.
Status:
This problem has been reported for ISD 7.02.
FIXED in ISD 7.03
Created: 2002-04-15   Last update: 2002-06-06   InstallShield tracking number: 1-8HQBQ

Error Messages When Applying a Patch

Description:
When installing a patch that you created for a Standard project you may receive the following error message when you start Update.exe: "This installation can not be run by directly launching the MSI package; you must run setup.exe." This happens if your setup is built as compressed CD-ROM image. You may also receive the following error message: "1155: FILE <patch path>\ISScript.MSI not found".
Workarounds:
Open the setup.ini file in directory [ProgramFilesFolder]\InstallShield\Developer\support and change the line
ScriptDriven=0
to
ScriptDriven=1
Then rebuild your patch.
Status:
InstallShield has confirmed that this is a problem in ISD 7.02.
FIXED in ISD 7.03
Created: 2002-02-09   Last update: 2002-06-06   InstallShield tracking number: 1-72RDQ

ARPSYSTEMCOMPONENT doesn't Prevent Entry in Add/Remove Programs Control Panel

Description:
Setting the ARPSYSTEMCOMPONENT property to 1 should prevent the application from being displayed in the Add or Remove Programs list on the Control Panel. However this doesn't work for Standard projects.
Workarounds:
After building a release a setup.ini file will be generated in the release. Modify the setup.ini file with the following additional information:
[Startup]
NoAddRemove=Y
Status:
InstallShield has confirmed that this is a problem for Standard projects in ISD 7.02. It is documented in knowledge base article Q105931.
FIXED in ISD 7.03
Created: 2002-03-16   Last update: 2002-06-06   InstallShield tracking number: 1-6XA8T

Build Error -3016: Failed to add Binary table ISSELFREG.DLL to package

Description:
While building a release you may get the following error message: "Build Error -3016: Failed to add Binary table ISSELFREG.DLL to package"
Cause:
The -3016 error is caused by including a Merge Module that has a file marked as Self-Registering in a project that has a File marked as self-registering. If both projects (the MSM and ISM) contain a Binary entry called ISSELFREG.DLL, when the build tries to merge the second instance of ISSELFREG.DLL, the build gives the 3016 error.
Workarounds:
To get around this issues you can remove the ISSELFREG.DLL from the Merge Module. Since your consuming ISM project already has this entry, everything will work fine. The problem in doing this is that if you later consume this Merge Module in a project that does not have a File marked as self registering, the Merge Module will fail.
Status:
InstallShield has confirmed that this is a problem in ISD 7.02.
FIXED in ISD 7.03
Created: 2002-03-16   Last update: 2002-06-06   InstallShield tracking number: 1-6SPUD

Product Configuration Flags not Included in ISReleaseFlags Property

Description:
ISD enables you to build different packages from one project by attaching release flags to featrues. When building a release you can specify flags to select which features will be built into the release. The flags that were selected for a release are also stored in the ISReleaseFlags property so you can conditon custom actions based on these flags. You can specify release flags on the Product Configuration level and on the Release level. Both should be combined into the ISReleasedFlags property, and this worked properly in InstallShield Windows Installer Edition. However in ISD only the flags from the Release level are stored in the propety, not those from the Product Configuration level.
Workarounds:
Specify the flags on the release level.
Status:
This problem is reproducible in ISD 7.02.
FIXED in ISD 7.03
Created: 2002-03-16   Last update: 2002-06-06   InstallShield tracking number: 1-7VH4X

Shortcut View Problems

Description:
In Shortcut view create a folder and a shorcut in that folder. Delete the shortcut. Drag the folder with the mouse to move it under another folder. When you release the mouse button the Developer IDE crashes with an "invalid page fault". Trying the same in Setup Design or Component view will not crash the IDE, but the folder can't be moved. It is also impossible to delete such a folder.
Moving a shortcut folder that contains a shorcut changes the name of the folder in the tree view to the value of its Display Name property. This happens in Setup Design or Component view but not in Shortcut view.
Workarounds:
Make sure the shortcut folder isn't empty before trying move or delete it.
Status:
This problem is reproducible in ISD 7.02.
FIXED in ISD 7.03
Created: 2002-02-26   Last update: 2002-06-06   InstallShield tracking number: 1-802H2

Improper Link to ReadMe File in Add/Remove Programs

Description:
In the General Information view of the Developer IDE there's a section for the information that will be displayed in the Add/Remove Programs control panel on the target computer. One of the settings is the name of your readme file. However when the program is installed this link won't work.
Cause:
A custom action named SetARPReadme is used to store the name of your readme file in the ARPREADME property that Windows Installer uses to set up this link. However in this custom action of type 51 the source and target field have been swapped.
Workarounds:
Go to the SetARPReadme custom action under Advanced Views -> Sequences/Actions. Move the value in the Source filed (the name of your readme file) to the target field, and the value from the target field (ARPREADME) to the source field.
Status:
InstallShield has confirmed that this is a problem in ISD 7.02.
FIXED in ISD 7.03
Created: 2002-02-14   Last update: 2002-06-06   InstallShield tracking number: 1-7MPY2

CmdLine Entry in Setup.ini not Working

Description:
Setup.ini has an entry of the form CmdLine= where you can specify command line parameters that should be passed to the setup. However in ISD 7.02 this is not working, the CmdLine entry is ignored. This only affects Standard projects.
Workarounds:
Pass the parameters on the command line when you invoke setup.exe. You can also do this by creating a shortcut to setup.exe and adjusting its command line property accordingly.
Status:
InstallShield has confirmed that this is a problem in ISD 7.02.
FIXED in ISD 7.03
Created: 2002-02-02   Last update: 2002-06-06   InstallShield tracking number: 1-73J2P

Registering File Types not Working in Merge Modules

Description:
You can't associate a file extension with an application in a merge module project because ISD appends the module id to the extension. To reproduce create a component in a merge module and create a file extension (.XYZ) under the advanced setting of the component. Merge the module into a project. The project will now register a file extension on the target consisting of .XYZ.{GUID} rather than just .XYZ.
Workarounds:
None.
Status:
InstallShield has confirmed that this is a bug in ISD 7.00 - 7.02.
FIXED in ISD 7.03
Created: 2001-09-15   Last update: 2002-06-06   InstallShield tracking number: 1-6LLV6

Minor Update Fails for Standard Projects as Full Install

Description:
If you try to create a minor update for a Standard project by changing the package code (which is a Windows Installer requirement), you'll receive the error message "A previous version of this product is already installed..." when you try to install the update. You get this error regardless of the REINSTALLMODE, REINSTALL and ADDLOCAL property settings. This only happens if you deliver the minor update as full install package, not as patch. Basic MSI projects are not affected by this problem.
Workarounds:
Create the minor update as a patch, or use a Basic MSI project.
Status:
InstallShield has confirmed that this is a problem in ISD 7.02.
FIXED in ISD 7.03
Created: 2002-01-04   Last update: 2002-06-06     InstallShield tracking number: 1-6UBGA

FeatureSetData Fails with Result -126

Description:
Calling FeatureSetData returns a result code of -126 which is not documented.
Workarounds:
None.
Status:
InstallShield has confirmed that this is a problem in ISD 7.02.
FIXED in ISD 7.03
Created: 2002-01-04    Last update: 2002-06-06   InstallShield tracking number: 1-784LA

Fatal Error 0 while Compiling the Script

Description:
You may get Fatal Error 0 in the during the compilation of the InstallScript. This happens if the MSI file is locked.
Workarounds:
Make sure the MSI file isn't locked (e.g. opened in Orca)
Status:
InstallShield has confirmed that this is a problem in ISD 7.00, 7.01, and 7.02.
FIXED in ISD 7.03
Created: 2001-08-30   Last update: 2002-06-06   InstallShield tracking number: 1-6JAX1

Runtime Error 1706 when Running Standard Project Setup in Maintenance Mode

Description:
When running a setup created from a Standard Project and selecting Modify to add another feature, you get runtime error 1706 "No valid source could be found for product [ProductName]."
Cause:
The original installation source (e.g. CD-ROM) is required to install the additional files. However setup fails to display a dialog asking the user to insert the CD.
Workarounds:
Call EnterDisk in OnMaintUIBefore. Or create a self extracting exe release using PackageForTheWeb and select to leave the setup files on the user's hard disk - thus the source files will always be available. If you already shipped your setup you can tell users to insert the CD before they launch setup from the Add/Remove Programs control panel.
Status:
InstallShield has confirmed that this is a bug in ISD 7.00, 7.01, and 7.02.
FIXED in ISD 7.03
Created: 2001-10-22   Last update: 2002-06-06   InstallShield tracking number: 1-6RLGC

Initialization Dialog Shows Wrong Product Name

Description:
When launching your installation with setup.exe the "Preparing to Install" dialog will always show the product name you entered in the General Information section of the IDE, even if you specified a different product name in the release settings. All other dialogs use the correct product name.
Cause:
The product name for the initialization dialog is taken from setup.ini. ISD7 always writes the product name from the Product Properties section to the setup.ini file. It ignores any alternate product name specified for the release.
Workarounds:
Open setup.ini and adjust the Product= entry in the [Startup] section of building the release.
Status:
InstallShield has confirmed that this is a bug in ISD 7.00 - 7.02.
FIXED in ISD 7.03
Created: 2001-10-15   Last update: 2002-06-06   InstallShield tracking number: 1-6NBYS

Runtime Error 2318 if Subdirectory "Database" is Used

Description:
Error message "Internal Error 2318. C:\WINDOWS\TEMP" is displayed at runtime. The path in the error message is the TEMP directory. This happens if one of your components has a destination directory of [INSTALLDIR]\Database. The error message is displayed before the InstallWelcome dialog in Basic MSI projects, or during installation progress in Standard projects.
Cause:
ISD creates an entry in the Directory table, called "DATABASE". The presence of this entry is enough to trigger the error. It appears that this is a reserved word, but not taken into account. Here are some other resevered words to watch out for:
CLEANUPUNINSTALLROLLBACK
CLIENTPROCESSID
CLIENTUILEVEL
CURRENTDIRECTORY
DATABASE
SUPPORTDIR
ISSETUP_UISEQUENCE_PROCESSED
ISSETUPDRIVEN
ISSETUPFILESCOMPLETED
ISStartupEvent
OriginalDatabase
PackageCode
PackagecodeChanging
SourcedirProduct
VersionMsi
Workarounds:
Renaming the entry using the Direct Editor to something else fixes the problem - you don't need to change the directory itself, just the table key.
Status:
InstallShield has confirmed that this is a bug in ISD 7.00 - 7.02.
FIXED in ISD 7.03
Created: 2001-08-30    Last update: 2002-06-06   InstallShield tracking number: 1-6JAXQ

Build Errors -1007 and -5054 for Standard Projects that have a Language Dependent Splash Screen

Description:
When building a standard project you may get error messages like the following:
** Error: -1007: Cannot copy source D:\temp\setup.bmp to target D:\MySetups\standard\Product Configuration 1\Release 1\DiskImages\DISK1\409 - English (United States)\setup.bmp
** Error: -5054: Could not determine the size of the file "D:\MySetups\standard\Product Configuration 1\Release 1\DiskImages\DISK1\409 - English (United States)\setup.bmp"
This happens if all of the following criteria are true:
- A splash screen (setup.bmp) is inserted into one of the non-language independent nodes in the Setup Files/Billboards view
- Your build type is CD-ROM
- You specified to compress all your files in your release
Workarounds:
Build the release with the files uncompressed, or if the files must be compressed, create a network image instead of a CD-ROM build.
Status:
InstallShield has confirmed that this is a bug in ISD 7.00 - 7.02.
FIXED in ISD 7.03
Created: 2001-09-29   Last update: 2002-06-06   InstallShield tracking number: 1-6L44D

Language Independent Splash Screen not Displayed in Standard Project

Description:
The splash screen you specified under the Language Independent node of the Setup Files/Billboards view may not be displayed. This happens if you created a CD-ROM release and specified that all the files should be compressed. No build errors occur.
Workarounds:
Build the release with the files uncompressed, or if the files must be compressed, create a network image instead of a CD-ROM build.
Status:
InstallShield has confirmed that this is a bug in ISD 7.00 - 7.02.
FIXED in ISD 7.03
Created: 2001-09-29   Last update: 2002-06-06   InstallShield tracking number: 1-6JD31

Enabled property for Group Boxes Missing in Dialog Editor

Description:
In the property sheet for GroupBox controls there is no Enabled property. Consequently, the group box may be grayed in the resulting setup since the Attributes field of the Control table is sometimes set to 1.
Workarounds:
Set the Attributes value in Direct Editor.
Status:
InstallShield has confirmed that this is a bug in ISD 7.00 - 7.02.
FIXED in ISD 7.03
Created: 2001-09-15   Last update: 2002-06-06   InstallShield tracking number: 1-6L0SX

Path Variables Created Incorrectly

Description:
The Path Variable Dialog sometimes tries to base a new path on an existing path variable, when in reality it should create a new path variable for it. To reproduce: First add files from a directory called "C:\Program Files\Components\ActiveReports" and have IS to automatically create a path variable <Path Variable X>. Then add files from a directory called "C:\Program Files\Components\ActiveReports Pro". The location for the second set of files will be set to "<Path Variable X> Pro" (without quotes).
Workarounds:
On the Path Variables tab of the Options dialog (menu Tools - Options) select the third option "Always display the Path Variable Recommendation dialog". When adding the second set of files the path variable dialog will be displayed. On this dialog select the "Create a New Path Variable" option.
Status:
InstallShield has confirmed that this is a bug in ISD 7.00 - 7.02.
FIXED in ISD 7.03
Created: 2001-09-15   Last update: 2002-06-06   InstallShield tracking number: 1-6KVED

SdFeatureDialog2 Shows Wrong Feature Sizes

Description:
In SdFeatureDialog2 features may be displayed with a wrong size.
Workarounds:
Use the SdFeatureTree dialog instead.
Status:
InstallShield has confirmed that this is a bug in ISD 7.00 - 7.02.
FIXED in ISD 7.03
Created: 2001-08-30   Last update: 2002-06-06   InstallShield tracking number: 1-6J89S

String Table Entries cannot Contain Line Break

Description:
If you include a line break in the text you store in a string table entry, it will be displayed as garbage character at runtime.
Workarounds:
Create two string table entries and concatenate them by inserting a line break. Sample:
@STRING1 + "\n" + @STRING2
Status:
InstallShield has confirmed that this is a bug in ISD 7.00 - 7.02.
FIXED in ISD 7.03
Created: 2001-08-30   Last update: 2002-06-06   InstallShield tracking number: 1-6J89X

Setup with MDAC Merge Module Randomly Launches other Setup Program

Description:
While running the setup, another install program may be launched. This happens if another installer has left behind its setup.exe in the TEMP directory.
Cause:
The mdac.msm extracts mdac_typ.exe to the temp directory, and launches it with the command line parameters /q /c:"setup /qn1". Note that it's using "setup" not "setup.exe". A file called setup without .exe doesn't exist, and this seems to trigger a search algorithm in mdac_typ.exe, and it launches the first setup.exe it can find that resides in the same directory as mdac_typ.exe.
Workarounds:
Include and run mdac_typ.exe from a custom action with the proper command line parameters.
Status:
This problem is reproducible with the MDAC 2.5 SP1 and MDAC 2.6 merge modules in ISD 7.00 - 7.02 and IPWI 2.03. InstallShield has accepted this as bug in ISD 7.00 - 7.02.
FIXED in ISD 7.03
Created: 2001-08-30   Last update: 2002-06-06   InstallShield tracking number: 1-6JB2I
 

 

 

English News Discussions Windows Installer Related Tools More Help InstallScript About InstallSite Shop Site Search
deutsch Neuigkeiten Diskussionsgruppen Windows Installer MSI FAQ Artikel     Shop Suche

Copyright © by InstallSite Stefan Krueger. All rights reserved. Legal information.
GERMAN Impressum,Datenschutzerklärung, Haftungsausschluss
By using this site you agree to the license agreement. Webmaster contact