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

[ ISDev 8.02 | ISDev 8.01 | ISDev 8.00 ]

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

InstallShield Developer 8.00

Version: 8.00 with Hotfix of November 4, 2002
Release Date: October 15, 2002 (English), November 26, 2002 (German)
Download: To obtain the hotfix select Check for Updates from the Tools menu or download it from knowledge base article Q107463.
Release Notes: For more information about the hotfix see knowledge base articles Q107463 and Q107195
Installation Notes: The following applies only to the German edition: If you have previously installed an evaluation version of ISDev you must uninstall it before you install the full version.

[ Known Bugs | Other Known Issues ]

Known Bugs in ISDev 8.00

##STRINGID## in IniFile View of Migrated Projects

Description:
IniFile->Keyword->Datavalue shows in ##STRINGID## when converting an MSI/MSM file to an InstallShield Developer project (.ism). Even though the IDE displays the incorrect value, the correct values are written to the MSI package when built.
Workarounds:
None.
Status:
InstallShield has listed this problem as open issue in the release notes for ISD 7.00. Not fixed in ISD 7.01 - 8.00.
FIXED in ISDev 8.01
Created: 2001-08-18   Last update: 2002-06-06   InstallShield tracking number: 1-6A5O1

Release Wizard doesn't Create Build Report

Description:
After converting a project from ISWI 2.03 to Developer 7 a build report is no longer generated listing all components and files included in a build.
Workarounds:
None.
Status:
InstallShield has confirmed that this is a problem in ISD 7.02 - 8.00.
FIXED in ISDev 8.01
Created: 2002-06-06   InstallShield tracking number: 1-8WI0I

IDT File Not Found

Description:
Exported .isv truncates paths to .idt files if the project file name contains an extra dot (for example, Release 1.2.ism). The next time you try to open that .isv, it cannot find the .idt files.
Workarounds:
Rename your project before exporting. The project name does not affect the resulting setup.
Status:
This problem is listed in InstallShield Knowledge Base article Q106467 for ISD 7.04. Not fixed in ISDev 8.00.
FIXED in ISDev 8.01
Created: 2002-08-02   InstallShield tracking number: 1-9ITO1

Cannot Get Project from Source Control

Description:
If you have a binary column in a custom table in a project then "Get Latest Version" from source control fails with an error saying it could not open the project's ism file.
Workarounds:
None.
Status:
This problem is listed in InstallShield Knowledge Base article Q106467 for ISD 7.04. Not fixed in ISDev 8.00.
FIXED in ISDev 8.01
Created: 2002-08-02   InstallShield tracking number: 1-96FRX

UNINSTALL_DISPLAYNAME cannot be Changed in Maintenance Mode

Description:
Using the UNINSTALL_DISPLAYNAME variable to modify the way an existing product name is displayed in the Add/Remove Programs list, is unsuccessful if the product is already installed (e.g. when installing a Small Update).
Workaround:
Use RegDB functions to modify the display name, using code like this:
RegDBSetDefaultRoot(HKEY_LOCAL_MACHINE);
szLocation = "Software\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\InstallShield_" + PRODUCT_GUID;
if (RegDBGetKeyValueEx(szLocation, "DisplayName", nType, szValue, nSize) = = 0) then
    RegDBSetKeyValueEx(szLocation, "DisplayName", REGDB_STRING, UNINSTALL_DISPLAYNAME, -1);
endif;
Status:
This problem has been reported for ISD 7.02 - 7.04. Not fixed in ISDev 8.00.
FIXED in ISDev 8.01
Created: 2002-08-30   InstallShield tracking number: 1-9VWM4

"Delay engine reboot" Option Enabled for MSI Version 1.2

Description:
When running through the Release Wizard, using an existing product configuration and release name, the Setup Launcher screen displays the "Delay engine reboot until after your setup installation completes" checkbox in an enabled state, even if MSI Engine 1.2 was selected during the initial creation of the release. However this option only applies to MSI 2.0.
Workaround:
Don't select the "Delay engine reboot..." checkbox if MSI Engine Version 1.2 is selected.
Status:
This problem has been reported for ISD 7.03 and 7.04. Not fixed in ISDev 8.00.
FIXED in ISDev 8.01
Created: 2002-08-30   InstallShield tracking number: 1-9K0LD

Setup Creates Empty INI File Entries

Description:
In addition to the INI file entries you specified your setup may create entries like these:
[ ]
=
Cause:
This happens if these INI file entries are located in a merge module. In this case the INI file view adds invalid rows to the IniFile table with empty Section and Key entries. This only happens in merge module projects. In regular setup projects the Ini File View works properly and doesn't create these additional rows.
Workaround:
In your merge module project go to the IniFile table in Direct Editor and remove the rows with empty entries in the Section and Key columns.
Status:
This problems is reproducible in ISD 7.04. Not fixed in ISDev 8.00.
FIXED in ISDev 8.01
Created: 2002-08-30   InstallShield tracking number: 1-7MY1Q

Error 1334 "The file ... cannot be installed because the file cannot be found in cabinet file"

Description:
Running your setup may result in error 1334 "The file '[2]' cannot be installed because the file cannot be found in cabinet file '[3]'. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package." This can happen in some cases when all of the following conditions are true for your project:
- your setup includes two or more files with the same file name
- these files are being referenced using dynamic file linking
- when creating the release you specified a Previous Package for patch optimization
The file name mentioned in the error message would be such a duplicate file, appended with a number.
This looks like the patch optimization process incorrectly matches file names for dynamically linked files.
Workaround:
In the Direct Editor, in the File table, modify the File.File value to avoid a clash between the statically linked file and the dynamically linked file, as detailed in this article.
Alternative workarounds:
Remove the Previous Package entry from the release settings. Note that this will reult in larger patch packages (msp).
Avoid dynamic linking.
Status:

InstallShield has confirmed that this is a bug in ISDev 7.04 and ISDev 8.00.
FIXED in ISDev 8.01

Created: 2002-10-05   Last update: 2002-10-11   InstallShield tracking number: 1-ADGW5

Warning -6248 in .NET Dependency Scan

Description:
.NET Dependency Scan-at-Build Results in Warning: -6248.
Workarounds:
Please refer to Knowledge Base article Q106524, PRB: .NET Dependency Scan-at-Build Results in Warning: -6248 for a possible workaround.
Status:
This problem is listed in InstallShield Knowledge Base article Q106467 for ISD 7.04. Not fixed in ISDev 8.00.
FIXED in ISDev 8.01
Created: 2002-08-02   InstallShield tracking number: 1-9U2U5

ICE03 Validation Errors / Tables not Filtered with Language or Release Flags

Description:
Create a setup with language specific components and add entries to the Duplicate File table that are associated with these components. Build a release filtering out all but one language. The components for the other languages are not built into the resulting MSI file, as expected. However the Duplicate File table entries associated with the not included components exist in the MSI file. This results in ICE03 errors "Not A Valid Foreign Key" when validating the MSI file, but not in runtime errors. The same problems exists with release flags to filter features, and tables like ISRequiredFeature, ISSetupTypeFeatures, Condition, DuplicateFile, Environment, and ReserveCost.
Workarounds:
Here is a VB Script to post process the MSI file. It will delete entries from the Duplicate File table where the referenced file doesn't exist in the package.
ZIP FilterDuplicateFilesTable.zip   Written by Adrian Accinelli
File size: 821 bytes   Last update: 2001-09-29
Status:
InstallShield has confirmed that this is a problem in ISD 7.00 - 8.00.
Improved in ISD 7.01 - the following tables are filtered: Class,  Condition, CreateFolder, DuplicateFile, Environment, Extension, Feature, File, ISFeatureExtended, ODBCDataSource, ODBCDriver, ODBCTranslator, ProgID, PublishComponent, Registry, RemoveFile, ReserveCost, ISComponentExtended, Shortcut, Typelib.
FIXED in ISDev 8.01: The following tables are now also filtered: ISRequiredFeature, ISSetupTypeFeatures.
Created: 2001-09-29    Last update: 2002-06-06   InstallShield tracking numbers: 1-6L0T6, 1-6Q3ID, 1-6H0FJ, 1-6API1

Merge Modules in Sub-Features Can't be Deleted with Automation

Description:
ISWiProject.DeleteMergeModule does not remove a merge module from subfeature.
Workarounds:
Use ISWiFeature.RemoveMergeModule, which will remove a merge module from a subfeature.
Status:
InstallShield has listed this problem as open issue in the release notes for ISD 7.00. Not fixed in 7.01- 8.00.
FIXED in ISDev 8.01
Created: 2001-08-18   Last update: 2002-06-06   InstallShield tracking number: 1-6AJ65

[ Known Bugs | Other Known Issues ]

Other Known Issues in ISDev 8.00

Setup Hangs During MSI API Call

Description:
In a Basic MSI project when calling certain MSI API functions (like MsiSetTargetPath or MsiSetFeatureState) in a InstallScript custom action that is launched via DoAction from a dialog button you setup will wait indefinitely. It will not display an error message or crash, it will just not do anything anymore until you end it in task manager.
Cause:
This happens because of an apparent design decision in MSI. When DoAction is called, it appears that MSI does not process Windows messages. InstallScript uses COM to call MsiSetTarget, and thus relies on the Windows message queue. Hence the deadlock occurs, which does not occur in a C++ custom action that does not use COM.
Workaround:
Do not to call these MSI APIs from InstallScript if they are fired from DoAction from a dialog button. Insert the custom action into the sequence or use a DLL instead of InstallScript. (You can even create a custom action of type Standard DLL to call the function in msi.dll directly). Or convert your project to a Standard project and call the function from an event handler in your script.
Status:
InstallShield confirmed that this is a problem in all versions of InstallShield Developer and in ISWI since version 1.52.
Created: 2002-09-06   InstallShield tracking number:

INSTALLDIR Reverts Back to the Default Directory

Description:
If a path is entered during an installation, MSI verifies the path to determine that the installer has write access. If the path does not have write access, INSTALLDIR is changed to the default path directory for INSTALLDIR (which by default is Program Files\Your Company Name\Your Product Name). This action occurs whether or not you have components set to write to the path in question and it does so without any type of warning. As a result, if you need to have the user enter in a path (e.g. to locate files on a server), if the user does not have write access to that path, INSTALLDIR will be changed.
Workaround:
For a standard project, use InstallShield script and save the value of the field entered in a variable other than INSTALLDIR. Use this new variable when referring to the install directory.
Status:
This problem has been reported for ISD 7.02 - 7.04. A feature request has been submitted.
Created: 2002-08-30   InstallShield tracking number: 1-A3JHZ

GetLine Returns End-of-Line Error Unexpected

Description:
GetLine description claims that "when GetLine has read all the lines in a file, it returns an end-of-file error." However, it fails to mention that if the last line of the file does not end with the new line character, GetLine will also return end-of-file error when it reads this line. So the following example will never process the last line of the file if this line does not have a CR-LF at the end:
  while (GetLine (nFileHandle, svLine) = 0)
    ListAddString (listID, svLine, AFTER);
  endwhile;
Workarounds:
Handle the EOF condition properly or use ListReadFromFile instead.
Status:
InstallShield stated that this is by design.
Created: 2002-07-09   InstallShield tracking number: n/a

64-bit Setup Cannot Create 64-bit COM Objects

Description:
If you try to create a valid 64-bit COM object by calling CreateObject function from InstallScript compiled for a 64-bit platform, the operation will fail (i.e. IsObject function will return FALSE).
Cause:
InstallScript is running as a 32 bit process. Calling a 64 bit process from a 32 bit process can fail.
Workarounds:
Use VBScript instead of InstallScript. VBScript runs as 64 bit process.
Status:
InstallShield is aware of this problem. They are considering to make InstallScript a 64 bit processin a future release.
Created: 2002-06-13   InstallShield tracking number: 1-9G9R4

Error 0x80070725: Incompatible version of the RPC stub

Description:
When launching setup you may receive the message "Unhandled Exception Error: 0x80070725 Description: Incompatible version of the RPC stub. Setup will now terminate."
Cause:
An incompatible version of one or more OLE files have been installed on the failing machine.
Workarounds:
Use the fix specified in Microsoft knowledge base article Q321915.
Status:
This is problem is caused by a damage in the operating system.
Created: 2002-06-06    InstallShield tracking number: n/a

Problems with Network Image or Web Media Types

Description:
If you build setup media as Single Executable for Network Image or Web media type (specifying not to cache installation on local machine in the Local Machine dialog for Web media type), setup running in maintenance mode will fail with error: "Setup could not find a file on the specified path or disk. Please check that the proper disk is inserted or specify a new path. Unable to locate file <PATH TO MSI FILE>." This error occurs despite the fact that referenced MSI file exists in the specified location. Since there is no option to "specify a new path", if you click Retry button the following error will be displayed: "Error 1706.No valid source could be found for product <PRODUCT NAME>. The Windows Installer cannot continue." Then your setup aborts. This error occurs only when files must be copied (e.g. when running setup in Repair mode).
Workarounds:
When using Web media type, specify to cache installation on local machine in the Local Machine dialog. This is not a good workaround because the customers may be annoyed by the prompts to overwrite cached MSI file when running setup in maintenance mode. Another option is not to use Network Image or Web media type, but use CD-ROM media type instead.
Status:
This problem is inherent to the media types specified above.
Created: 2002-04-15   InstallShield tracking number: n/a

Wrong Feature States in Standard Project

Description:
Install a setup that was created from a Standard project. Afterwards call the Windows Installer API function MsiConfigureFeature (e.g. from a C++ program like the installed application itself) to uninstall a previously installed feature. The feature will properly removed. However if you run setup in maintenance mode, the removed feature is still listed as installed.
Cause:
With a standard project, the information about what was installed is stored in other locations than Windows Installer stores its feature states.
Workarounds:
Use the MsiGetFeatureState function in the maintenance script for your install and set the selected state manually from there.
Status:
This problem has been reported for ISD 7.01 - 7.02. InstallShield stated that this is by design.
Created: 2002-01-04    InstallShield tracking number: n/a

Graphics not Visible in Dialog Editor for Basic MSI Projects

Description:
Some graphics on dialogs may not be displayed in the dialog editor. The graphics are displayed properly during runtime. This happens for graphics in JPG format.
Cause:
The Dialog Editor can only display graphics in BMP and ICO format. JPEGs are supported at runtime, but not in the dialog editor.
Workarounds:
None.
Status:
InstallShield has confirmed that this is a limitation in ISD 7.00 - 8.00. A feature request has been submitted.
Created: 2001-09-29   Last update: 2001-12-19   InstallShield tracking number: 1-6TBKA

Setup tries to Install MDAC even if the same Version is Already Installed

Description:
When running a setup that includes the MDAC 2.5 merge module the MDAC installation will be triggered even if MDAC 2.52 is already installed on the machine.
Cause:
The merge module installs MDAC only if the version installed is less than or equal to 2.52. The reason to reinstall even on machines that have MDAC 2.52  is because there is a possibility that all necessary files are not on that computer. If a machine has 2.52 installed, but does not have a file critical to your install, your program will not function properly. This way you are guaranteed that all MDAC files are there.
Workarounds:
You can create a property named ISINSTALL_MDAC_BYVERSION and set it's value to "Yes". This will install MDAC 2.52 on the target machine if the version of MDAC is strictly less than 2.52.
Status:
This is by design.
Created: 2001-09-15   InstallShield tracking number: n/a

Internet Explorer 4.01 SP2 Required for Setups that includes MDAC Merge Module

Description:
When running a setup that includes the MDAC 2.5 merge module you may receive an error message that Internet Explorer 4.01 SP2 or above is required. However Microsoft only lists IE 3.01 as a requirement for MDAC 2.5.
Cause:
While testing the merge module InstallShield noticed that installing MDAC on a lower version of Internet Explorer would put the system through an infinite reboot.
Workarounds:
You can bypass the IE version check by creating a property named ISINSTALL_MDAC_SKIP and setting it's value to "Yes". This will install MDAC on any machine without any version checking. You could write a Custom Action that does your version checking and then sets/creates this property. This way you can install it on any machine you like to.
Status:
This is by design.
Created: 2001-09-15   InstallShield tracking number: n/a

Error 1918 while Installing ODBC Resources on Windows Me

Description:
When you try to install ODBC Resources on a clean Windows Me machine (which has MDAC 2.5 built in) you may receive a message like this: "Error 1918.Error ODBC driver Microsoft Access Driver (*.mdb). ODBC error 13. Could not load the setup or translator library. Verify that the file Microsoft Access Driver (*.mdb) exists and that you can access it.". This problem has been reported for Standard projects.
Workarounds:
Modify the OnError event handler as shown below:
function OnError(szMessage, nButtons_Icons)
begin
    if ((StrFind(szMessage, " 1918.") >= 0) && SYSINFO.WIN9X.bWinMe) then
        Sleep(200);    // 200ms delay.
        return IDRETRY;
    else
        return MessageBox(szMessage, nButtons_Icons);
    endif;
end;
This will retry to create the ODBC resource until it succeeds. You may want to limit the number of retries to avoid an endless loop. There s a report that it took up to 18 retries before it succeeded.
Thanks to Magnus Persson for the workaround.
Status:
This appears to be an operating system issue.
Created: 2001-09-15   InstallShield tracking number: n/a

IDE Appears to Hang in File View

Description:
When you open the file view in the IDE, ISD may seem to stop responding ("hang").
Cause:
The files may take a long time to load (appear to be hanging) if the top left view (System Directory Tree) points to any folder that contains a shortcut to a file that does not exist on your system. Windows attempts to looks for these files, cause a long delay in the file's view. If you have a shortcut with a missing target on our desktop, the whole view will take a long time to load since this is the default folder of the view.
Workarounds:
Remove the shortcut with missing target. If the target is on a network share, log in to the network.
Status:
This is a problem with the configuration of the development machine.
Created: 2001-08-30   InstallShield tracking number: 1-6JAXL

Digital Signature Fails on Windows 98

Description:
Error when trying to digitally sign on Windows 98 IE 4.01 SP2.
Cause:
The version of cryptui.dll on Windows 98 with IE 4.01 SP2 is lower than 5.131, which is required for digitally signing the media.
Workarounds:
Install the latest version of Microsoft Internet Explorer to update cryptui.dll.
Status:
This is a problem with the configuration of the development machine.
Created: 2001-08-18   Last update: 2001-12-19   InstallShield tracking number: 1-69JX7

Combo Boxes in InstallScript Editor Sometimes not Working

Description:
Cannot add script code into new script files (not Setup.rul) using Combo box entries.
Workarounds:
None.
Status:
This is by design. The functions added using the combo will go to setup.rul and not to any other script file.
Created: 2001-08-18   Last update: 2001-12-19   InstallShield tracking number: 1-68I6V
 

 

 

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