Shop

AdminStudio
InstallShield
Advanced Installer
other products

InstallShield

30% Rabatt für Besitzer von InstallShield 2014 oder älter beim Kauf der aktuellen Version
Details auf Anfrage
InstallShield 2016
Windows 10 Kacheln anpassen, Universal Windows Platform (UWP) und Nano Server, u.a.
Details hier

InstallShield und AdminStudio Schulungen

weitere Infos


 

Bugs Bulletin

[ 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 ]

Reporting a bug to InstallShield Software Corp.: If you suspect you discovered a bug in an InstallShield product, you can submit a bug report directly to InstallShield Software Corp. using the form at http://www.installshield.com/feedback/. A support program is not needed for this. In addition please inform the webmaster so that it can be added to the Bugs Bulletin here on InstallSite. If possible please include the work order number or service request id.

InstallShield Professional 7.01

Current version: 7.01.161 (download SP1) + Hotfixes Q107893 + Q108226
Released: December 12, 2002 (hotfixes January 29 and March 14, 2003)
Documentation: release notes

Known Bugs in IS Pro 7.01

Unchanged Files are Included in Differential Media Build

Description:
File times are stored based on MSDOS time, which is adjusted for time zones and daylight savings time, rather than universal time coordinates (UTC). This can cause differential media builds to include files that have not actually changed if new build is done in different time zone or time of year than comparison media.
Workarounds:
Adjust time zone setting on build machine to simulate conditions of comparison media build.
Status:
This problem is listed in the release notes for IS Pro 7.01.
Created: 2003-01-03    InstallShield Tracking Number: 1-AMAQT

Object Dialogs don't Use Skin

Description:
Objects that display user interface do not use skin of parent setup.
Workarounds:
Do not use skin with setup containing the object, or accept the visual inconsistency.
Status:
This problem is listed in the release notes for IS Pro 7.01.
Created: 2003-01-03    InstallShield Tracking Number: 1-BLDB5

Unable to Load Project

Description:
When a project element, such as a file, has name that begins with opening bracket character, "[", project may fail to load in IDE and will not work correctly.
Workarounds:
Avoid using bracket characters in project element names.
Status:
This problem is listed in the release notes for IS Pro 7.01.
Created: 2003-01-03    InstallShield Tracking Number: 1-BDVEK

Un-Selected Objects are being Installed

Description:
Update setups that are created with Service Pack 1 or later and call ComponentSelectNew may install objects that were not installed when the application was orginally installed.
Workarounds:
Do not call ComponentSelectNew; instead call ComponentSelectItem for each new component.
Status:
This problem is listed in the release notes for IS Pro 7.01.
Created: 2003-01-03    InstallShield Tracking Number:

File not Found in Dynamic File Group

Description:
If a dynamically linked file group specifies a source folder that is on a network, a trailing backslash in the folder path causes the build location to be incorrectly determined and file to not be found.
Workarounds:
Do not use a trailing backslash in the folder path.
Status:
This problem is listed in the release notes for IS Pro 7.01.
Created: 2003-01-03    InstallShield Tracking Number: 1-BM7HF

CopyFile and XCopyFile Fail Silently with Read-Only Files

Description:
CopyFile and XCopyFile fail if the target file already exists and has the read-only flag set. According to documentation CopyFile should return COPY_ERR_TARGETREADONLY (-46) and XCopyFile should also return a negative result in this case. However both functions return 0 for success in this case, without copying the file. Also the file is logged for uninstall (i.e. is removed when you abort the setup, ignoring the read-only flag).
Note: The OnFileReadOnly event handler is not called.
Workarounds:
None.
Status:
InstallShield has confirmed that this is a bug in ISPro 7.00 and previous versions of 6.x.
Created: 2000-12-08   Last update: 2002-10-05   InstallShield Tracking Number: 1-3PYX1

ISCAB Fails in Command Line Build

Description:
Running iscab.exe with the -a option may fail. This happens if you specify only the file name, without a path, in the [File Group] section. The failure has been reported for Windows XP while the same works on Windows 2000.
Workarounds:
Include the path, like:
[File Group]
File1="mytest.txt","c:\mypath\"
Status:
InstallShield confirmed that this is a bug in IS Pro 7.00.
Created: 2002-09-06    InstallShield Tracking Number: 1-AK54F

Error -5009 When Launching Child Setup

Description:
When a setup launches a silent child setup using DoInstall with the NOWAIT option, uninstalling the parent setup fails with error -5009.
Workarounds:
Use the WAIT option in such cases.
Status:
This problem is listed in the release notes for IS Pro 7.00 and 7.01.
Created: 2002-08-14    InstallShield Tracking Number: 1-9LSUD

Problems with Child Setups in Silent Mode

Description:
DoInstall with the NOWAIT option does not work predictably when there is no user interaction in both setups.
Workarounds:
Use the WAIT option in such cases.
Status:
This problem is listed in the release notes for IS Pro 7.00 and 7.01.
Created: 2002-08-14    InstallShield Tracking Number:

IDE Crash when Media Build is Cancelled

Description:
IDE crashes when canceling a differential media build.
Workarounds:
Do not cancel the build when a differential media is being built.
Status:
This problem is listed in the release notes for IS Pro 7.00 and 7.01.
Created: 2002-08-14    InstallShield Tracking Number: 1-A65ET

InstallShield Professional 7.00

The problems listed below have been fixed in the latest maintenance release and are listed for reference. Any bugs that also exist in later versions are listed there.

Version: 7.00.332 (with Hotfix of 2002-10-02)
Released: August 14, 2002, October 2, 2002 (hotfix)
Release Notes: http://www.installshield.com/downloads/isp/isp_readme70.asp
Installation Notes: Professional 7 can co-exist with previous versions on the same machine.
Download Hotfix: Select Check for Updates from the Online menu.

Known Bugs in IS Pro 7.00

Progress Dialog Displayed Late

Description:
After clicking Install on the SdStartCopy dialog (or whatever the last dialog in your wizard sequence is) there may be several seconds delay before the progress bar dialog comes up. This happens on Windows Me and XP.
Cause:
At this time, the CreateInstallationInfo function is being executed. On operating systems that support System Restore, a new rerstore point will be created which takes some time.
Workarounds:
Move the CreateInstallationInfo call from OnShowUI to OnMoveData, after the call to StatusUpdate. This will way the progress dialog will be displayed (with a value of 0%) while the restore point is being created.
Alternatively you can prevent the creation of a restore point by placing
  bIfxPCHOn = FALSE;
in your OnBegin event handler.
Status:
InstallShield has confirmed this behaviour in IS Pro 7.00.
FIXED in version 7.01.
Manual adjustment of script code may be required in existing projects. See the release notes for details.
Created: 2002-09-12   Last updated: 2003-01-03   InstallShield Tracking Number: 1-ASGWU

Windows XP Themes not Supported

Description:
Linking to Windows XP's version of Comctl32.dll using a manifest is not supported in this release.
Workarounds:
None.
Status:
This problem is listed in the release notes for IS Pro 7.00.
FIXED in version 7.01.
Created: 2002-08-14    Last updated: 2003-01-03   InstallShield Tracking Number: 1-9SUKP

Browse Button Incorrectly Placed in SdSetupType2 Dialog

Description:
The Browse button in SdSetupType2 dialog box appears incorrectly positioned when used with the Slate and Olive skins.
Workarounds:
Do not use this function in conjunction with these skins.
Status:
This problem is listed in the release notes for IS Pro 7.00.
FIXED in version 7.01.
Created: 2002-08-14    Last updated: 2003-01-03   InstallShield Tracking Number: 1-A5U29

Error 129: "Media too small" with Skins

Description:
Skins cannot be used with multi-disk setups. When attempting to build a multi-disk setup that uses skins you will receive the following error: "Error 129: Media too small. Could not fit 'setup.skin' on disk 1". The build will then abort.
Workarounds:
Do not use skins with multi-disk setups.
Status:
This problem is listed in the release notes for IS Pro 7.00.
FIXED in version 7.01.
Created: 2002-08-14    Last updated: 2003-01-03   InstallShield Tracking Number: 1-A7IXX

Installation Stops with Error -5005 : 0x8007000d

Description:
During initialization your setup may stop with error -5005 : 0x8007000d, referencing KernelMedia.cpp and SetupDLL.cpp. This happens if a sub folder in your Disk1 directory includes a file with .hdr extension. Essentially this prevents you from placing sub installations in a folder beneath the main setup.
Workarounds:
Put your main setup in a folder (not the root of your CD) and place the sub install in a folder at the same level. Or add another folder level between your main setup and the sub setup (i.e. put it in a sub-sub-folder)
Status:
This problem is reproducible with ISPro 7.00.
FIXED in version 7.01.
Created: 2002-10-05   Last updated: 2003-01-03   InstallShield Tracking Number: 1-AXSRX

SdBitmap Dialog not Displayed Properly with MonoChrome Skin

Description:
MonoChrome skin design is not compatible with SdBitmap dialog.
Workarounds:
Do not use MonoChrome skin if you setup uses the SdBitmap dialog.
Status:
This problem is listed in the release notes for IS Pro 7.00.
FIXED in version 7.01.
Created: 2002-08-14    Last updated: 2003-01-03   InstallShield Tracking Number: 1-B2QL3

Cancelling Setup Leaves Install in Undefined State

Description:
After cancelling a previous install attempt, your setup always launches in maintenance mode, but with nothing installed. You are unable to uninstall. The TARGETDIR is erroneously set to the Windows directory. This happens after you cancel a setup in an early stage.
Cause:
Normally, when the installer is run and the directory does not exist then the installer runs in first time mode and if the user cancels neither the directory nor the file is created.  Normally, when the directory and the file both exist the installer runs in maintenance mode and if the user cancels the setting in setup.ilg are left unchanged.
What seems to happen to a user is that she installs the package, later the setup.ilg file is lost for some reason: perhaps it is moved by an accidental gesture in Windows Explorer, perhaps Scandisk loses it while repairing disk damage or whatever. The next time that the user runs the installer, either the original or from add/remove programs, it unexpectedly runs in first time mode. The user has doubts and so she cancels. This will leave an unusable setup.ilg on the machine, causing the described symptoms.
Steps to reproduce:
1. Install an application
2. Delete all of the files from its C:\Program Files\InstallShield Installation Information\{...GUID...} directory.
3. Run the installer again and press Cancel to the Welcome wizard dialog.
4. Run the installer again, you are now in maintenance mode with nothing installed and a faulty target directory.
Workarounds:
Delete the file C:\Program Files\InstallShield Installation Information\{...GUID...}\setup.ilg. For this you must first make the hidden directory C:\Program Files\InstallShield Installation Information visible.
Status:
InstallShield has confirmed that this is a bug in IS 6.22, 6.31 and 7.00.
FIXED in version 7.01.
Created: 2001-04-07   Last update: 2003-01-03   InstallShield Tracking Number: 1-53DNB

Only First Instance Listed in Control Panel

Description:
After installing several instances of a multi instance enabled package, you may find that only the first instance is listed in the Add/Remove Programs control panel.
Cause:
By default Pro 7 appends the destination path to the uninstall display name for the second and subsequent instances. On Windows 98 there's a 63 characters limit for this string. If your display name with path is longer than 63 characters (which is not unusual) it will be added to the uninstall registry entry, but control panel doesn't list the entry.
Workarounds:
In the OnMoveData event handler modify the code that creates the uninstall entry for the new instance which by default looks like this:
RegDBSetItem( REGDB_UNINSTALL_NAME, szUninstallName + " (" + szInstallPath + ")" );
(problematic part highlighted in bold)
Status:
InstallShield is considering to fix this scenario in the default implementation.
FIXED in version 7.01.
Created: 2002-10-05    Last update: 2003-01-03   InstallShield Tracking Number: 1-B2QL7

.NET Framework Object includes Update Service

Description:
Adding the .NET Framework object to your setup also adds the InstallShield Update Service, even if you didn't select to update enable your setup.
Workarounds:
None.
Status:
This problem has been reported for IS Pro 7.00.
FIXED in version 7.01.
Created: 2002-09-06    Last update: 2003-01-03   InstallShield Tracking Number: 1-AONK4

Build Variables not Resolved Properly

Description:
Build variables that end with a backslash, cause problems with resolving paths.
Workarounds:
Ensure that build variables that end with a backslash are changed so that they end with two backslashes.
Status:
This problem is listed in the release notes for IS Pro 7.00.
FIXED in version 7.01.
Created: 2002-08-14    Last update: 2003-01-03   InstallShield Tracking Number: 1-A5HVD

SYSINFO.nSuites Returns Unexpected Result

Description:
Testing the value of SYSINFO.nSuites in an equal condition like this will not give the expected result:
  if ( SYSINFO.nSuites = ISOS_ST_XP_PRO ) then
Cause:
SYSINFO.nSuites includes a combination of bit flags that apply to the current operating system. On Windows XP Pro it has a value of ISOS_ST_XP_PRO + ISOS_ST_WORKSTATION.
Workarounds:
Use the & operator to test if a specific flag is set in SYSINFO.nSuites, like this:
  if ( SYSINFO.nSuites & ISOS_ST_XP_PRO ) then
Status:
This is a documentation issue in IS Pro 7.00.
FIXED in version 7.01.
Created: 2002-09-12    Last update: 2003-01-03   InstallShield Tracking Number: 1-B2QKR

Other Known Issues in IS Pro 7.00

Use DLL Fails in Migrated Project

Description:
If the specified DLL name does not have an extension, the DLL will fail to load. Previoues versions of Professional automatically appended ".dll" if the extension was missing.
Workarounds:
Specify the DLL extension when making the call.
Status:
This problem is listed in the release notes for IS Pro 7.00.
FIXED in version 7.01.
Created: 2002-08-14    Last update: 2003-01-03   InstallShield Tracking Number: 1-A5HVR

Pro 6.31 Objects not Working in Pro 7

Description:
Objects created with version 6.31 cannot be used on systems that have only InstallShield Professional 7.
Workarounds:
Ensure that 6.31 is installed on the system.
Status:
This problem is listed in the release notes for IS Pro 7.00.
FIXED in version 7.01.
Created: 2002-08-14    Last update: 2003-01-03   InstallShield Tracking Number: 1-A4Z9X

 

 

 

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