more / weitere

InstallShield und AdminStudio Schulungen

Bugs Bulletin: InstallShield Developer 8.0

[ ISDev 8.02 | ISDev 8.01 | ISDev 8.00 ]

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. If InstallShield confirms the bug, please inform the webmaster so that it can be added to the Bugs Bulletin here on InstallSite.

InstallShield Developer 8.02

Version: 8.02 (English) / 8.01 (German)
Release Date: April 15, 2003 (English) / April 24, 2003 (German)
Download: Select Check for Updates from the Tools menu
Release Notes: The German SP1 includes the fixes from both English service packs 1 and 2.
Developer 8.02 English Release Notes
Developer 8.01 German Release Notes
See also: InstallShield Knowledge Base article Q106467 "Known Issues in Developer"

Closed bugs are marked FIXED in ISDev 8.02 within the ISDev 8.01 list

[ Known Bugs | Other Known Issues ]

Known Bugs in ISDev 8.02

Localized Merge Modules can't be Used in Same Setup

Description:: The Merge Module for JET 4.0 is available in English, German and Japanese. However these modules cannot stand side-by-side. If you include multiple language versions in a setup, the wrong language files may get installed.
Cause:: The German and Japanese versions are based on the English merge module, but the GUIDs haven't been changed. The Component Code for the Jet40Gate contains the component code for English Jet40Gate in the English Merge Module. All of the Custom Actions to launch the Jet setup contain the English Merge Module appended to the CA name.
Going to the Direct Editor and viewing the tables:
1. The ActionText table has the English GUID appended to each action. (This is changed when the CA is cleaned up.)
2. Component table has the English GUID associated with the Component.
3. CustomAction table has the English GUID associated with each action. (This needs to be cleaned up when fixing the CAs)
4. ISComponentExtended has the English GUID associated with it.
5. ModuleComponents has English GUID associated with it.
6. This is the one that really gets you. The ModuleInstallExecuteSequence table has the English GUID associated with the Action, the BaseAction and within the Condition.
7. ReserveCost has the English GUID associated with the Component field.
Workaround:: Fix the GUIDs in the tables listed above.
Status:: This is an issue with the modules in InstallShield's Merge Module Gallery.
Created: 2003-10-11 InstallShield tracking number:

Build Warning -6495: File Version Must Differ Within the First Three Elements of the Version String

Description:: When bulding a QuickPatch the following waring may be issued: "ISDEV : warning -6495: The version for file [1] only differs past the third version element. It must differ within the first three elements of the version string." where [1] is a placeholder that contains the name of the file whose version is causing this warning. This warning is incorrect. Files will get updated properly even if only the fourth version field is changed. The limitation to the first three fields of the version number only applies to the ProductVersion (in general information), not to the version resouces of a individual file.
Workaround:: You can safely ignore this warning.
Status:: This is a bug in ISDev 8.02. It still exists in DevStudio 9.00.
Created: 2003-09-07 InstallShield tracking number:

ISDev doesn't Integrate in Visual Studio .NET 2003

Description:: Installing Developer 8 on a machine with Visual Studio .NET 2003 doesn't active the integration of Developer in the Visual Studio IDE. This only happens if the previous version, Visual Studio .NET 2002, is not installed on the machine.
Workaround:: InstallShield Knowledge Base article Q106541 includes a tool that activeates the integration.
Status:: This problem has been reported for ISDev 8.01 and 8.02.
FIXED in DevStudio 9.00
Created: 2003-05-09 InstallShield tracking number:

String Table Search misses Summary Information

Description:: From the IDE String Table view, the "Find String ID in Project" menu item does not find string usages in the project's Summary Information.
Workaround:: None.
Status:: InstallShield has confirmed that this issue still exists in ISDev 8.02 and DevStudio 9.00.
Created: 2003-05-06 InstallShield tracking number: 1-CTP7Z

Date mangling on Build Log files and Report files

Description:: There are several problems with the log files view:; a. The IDE view sort algorithm (by filename with "-" removed) is wrong.
b. The filenames themselves do not lend themselves to sorting in Windows Explorer, or from any other file-level tool, due to month-day-year date format, 12-hour time format, and lack of leading zeroes on single-digit months and days. If this was fixed, it would also fix issue a.
c. The file-system timestamps are getting reset on every build for all previous build logs and reports.
Workaround:: None.
Status:: InstallShield has confirmed that this issue still exists in ISDev 8.02 and DevStudio 9.00.
Created: 2003-05-06 InstallShield tracking number: 1-CWF06

Open Release Folder Menu Item somtimes not Working

Description:: A Release Name with comma breaks the IDE menu item Tools | Open Release Folder.
Workaround:: None.
Status:: InstallShield has confirmed that this issue still exists in ISDev 8.02 and DevStuio 9.00.
Created: 2003-05-06 InstallShield tracking number: 1-CSBGG

Refresh Problem in Registry View

Description:: There's a display refresh problem in IDE registry view. It can display two values with "key path" icons.
Workaround:: None.
Status:: InstallShield has confirmed that this issue still exists in ISDev 8.02 and DevStudio 9.00.
Created: 2003-05-06 InstallShield tracking number: 1-CSTCS

Invalid SMS Package Definition File

Description:: If your Product Name includes spaces, ISDev produces an SMS package definition file with invalid CommandLine.
Workaround:: None.
Status:: InstallShield has confirmed that this issue still exists in ISDev 8.02 and DevStudio 9.00.
Created: 2003-05-06 InstallShield tracking number: 1-CTCT0

Debug Errors in MSI Log File

Description:: After generating a log file of your installation you'll find entries like this:
The Control table has a row with the key "SetupError","WarningIcon"
Cause:: InstallShield named the icon control on the SetupError dialog "WarningIcon" instead of "ErrorIcon".
Workaround:: Change the name of the control to ErrorIcon.
Status:: InstallShield has confirmed that this issue still exists in ISDev 8.02 and DevStudio 9.00.
Created: 2003-05-06 InstallShield tracking number: 1-CZ6ZG

Build Error -6645 with .NET Assemblies

Description:: When building your project you may receive error "ISDEV : error -6645: <path to DLL> failed to load" where <path to DLL> refers to a file in the project. This happens if the DLL was built for .NET and "scan at build for .NET dependencies" is selected. But only if the file is located on the network. Copying the file to the local hard disk avoids the error.
Workaround:: Copy the :NET file to the local hard disk.
Status:: InstallShield has confirmed that this is a known issue in ISDev 8.01-8.02.
FIXED in DevStudio 9.00
Created: 2003-04-29 InstallShield tracking number: 1-D2D3U

Script Editor Capitalizes Keywords

Description:: After typing a function name like AskText the script editor automatically changes it to capital letters, e.g. ASKTEXT. This results in compile errors.
Workaround:: Right click in the script editor pane, select properties, and go to the Language/Tabs tab. Uncheck the option "Correct text case while typing language keyword."
Status:: InstallShield has confirmed that this is a known issue in ISD 7.04. It is documented in InstallShield knowledge base article Q105958. Not fixed in ISDev 8.00 - 8.02 and DevStudio 9.00.
Created: 2002-09-06 InstallShield tracking number: 1-6NSQN

Word Export Missing in Crystal Merge Modules

Description:: Crystal Reports 8 and 8.5 objects are missing Export to Word support.
Workarounds:: Add U2FWORDW.DLL to your project and install it to [WindowsFolder]\Crystal. this file can be found on the Crystal Reports 8/8.5 CD.
Status:: This problem is listed in InstallShield Knowledge Base article Q106467 for ISD 7.04. Not fixed in ISDev 8.00 - 8.02 and DevStudio 9.00.
Created: 2002-08-02 InstallShield tracking number: 1-9I0NL

Default Icon Missing from COM Extraction

Description:: During COM Extraction the default icon is not extracted when the registry entry is just the file name without a path.
Workarounds:: Instead of adding the file and setting the Com Extract at Build, add the file using Component Wizard -> COM Server option. After this modify ISBuildSourcePath column of Icon table by selecting the file in Data column in Icon table in Direct Editor.
Status:: This problem is listed in InstallShield Knowledge Base article Q106467 for ISD 7.04. Not fixed in ISDev 8.00 - 8.02 and DevStudio 9.00.
Created: 2002-08-02 InstallShield tracking number: 1-9GHNC

Connection to Visual Studio .NET Project Lost

Description:: If you are using InstallShield Developer within Microsoft Visual Studio .NET, and you create a reference to a Visual Studio Project Output, and then you rename the Visual Studio project, then the InstallShield build will no longer resolve the reference.
Workarounds:: After renaming your Visual Studio project, then go to the Path Variables view in InstallShield. You will see a Path Variable whose value contains the old name of the Visual Studio project. Update the name to reflect the new value.
Status:: This problem is listed in InstallShield Knowledge Base article Q106467 for ISD 7.04. Not fixed in ISDev 8.00 - 8.02.
FIXED in DevStudio 9.00
Created: 2002-08-02 InstallShield tracking number: 1-8YZ9S

COM Registration Fails for 64-bit COM Objects in 64-bit Setup

Description:: If you define a self-registered 64-bit COM DLL installed by a 64-bit setup, the COM registration will fail with the following runtime error message: "Error 1904.Module failed to register. HRESULT . Contact your support personnel."
If you take another approach and set up ISD to extract COM information from this 64-bit DLL at build time, the following warning will be displayed: "Warning -4354: The build was unable to extract COM information from the file <path to a 64-bit DLL>."
Workarounds:: Register the DLL either directly from InstallScript by running LaunchAppAndWait(WINSYSDIR ^ "regsvr32", "/s " + strPath , WAIT), where strPath is a path to the COM DLL, or register the DLL via a batch script.
Status:: InstallShield confirmed that this is a problem in ISD 7.03 - 8.02 and DevStudio 9.00.
Created: 2002-06-13 InstallShield tracking number: 1-9G9RC

Features Appear in the Wrong Order in the Feature Tree Dialog

Description:: In a setup with multiple configurations, which include features based on release flags, some features may appear in the wrong order, i.e. not in the order they are defined in the IDE. This is not consistent between projects.
Workarounds:: None.
Status:: InstallShield has confirmed that this is a problem in ISD 7.02 - 8.02 and DevStudio 9.00.
Created: 2002-06-06 InstallShield tracking number: 1-7XTY7

File and Component Keys not Working in Registry Values

Description:: In MSI the Formatted data type accepts values in the form [#somefile.exe] which will resolve to the full path of the file identified by the file key #somefile.exe. However such entries don't work if entered in the registry view of ISD. They worked properly in IPWI 2, so this may cause an upgraded project to fail.
The same problem exists for entries in the form [!filekey] and [$componentkey].
Cause:: The Developer IDE escapes the square brackets, so [!filekey] becomes [\[]!filekey[\]] in the registry table.
Workarounds:: Use Direct Editor to adjust the entry in the registry table.
Status:: For file keys in the format [#somefile] InstallShield has confirmed that this is a bug in ISD 7.00 and it was FIXED in ISD 7.02.
For [!filekey] and [$componentkey] the problem still exists in ISD 7.02 - 8.02 and DevStudio 9.00.
Created: 2001-09-15 Last update: 2002-04-29 InstallShield tracking numbesr: 1-6SPUK (for [#somefile.exe]), 1-9G9P3 (for [$componentkey] and [!filekey])

Custom Action Properties Unavailable if Target Field Contains Apostrophe

Description:: If you enter text that includes an apostrophe in the Target field of a custom action, the action's properties disappear from the IDE. To reproduce the issue, do the following:
1. Go to the Custom Actions view and create a new action
2. Enter some text in the Target field that includes an apostrophe, e.g. "Stefan's Test"
3. Select some other view, then return to your custom action
The properties of the action will no longer be displayed in the rightmost pane, and you can't open the context menu for your action.
Workarounds:: Don't use an apostrophe in the Target field of a custom action. If you already did, go to the CustomAction table in Direct Editor and remove the apostrophe.
Status:: InstallShield confirmed that this is a problem in ISD 7.02 - 8.02 and DevStudio 9.00.
Created: 2002-04-29 InstallShield tracking number: 1-9G9PH

Unwanted Feature is Selected by Default During Initial Installation

Description:: In a setup with multiple configurations, which include features based on release flags, some features, which must be unselected in the feature selection dialog by default, become selected. This is not consistent between projects.
Workarounds:: None.
Status:: InstallShield has confirmed that this is a problem in ISD 7.02 - 8.02 and DevStudio 9.00.
Created: 2002-04-15 Last update: 2002-06-06 InstallShield tracking number: 1-7T25A

Precompiler Directive #elifdef not Working

Description:: Code blocks following #elifdef conditions never get executed. Under certain conditions, compiler generates "error C8059: 'elifdef' : unrecognized
preprocessor command". To simulate the problem, create a standard project and add the following blocks of code to setup.rul file:
...
// #define ZERO 1
#define ONE 1
...
function OnFirstUIBefore()
...
begin
#ifdef ZERO
MessageBox("#ifdef ZERO", MB_OK);
#elifdef ONE
MessageBox("#elifdef ONE", MB_OK);
#else
MessageBox("#else", MB_OK);
#endif
abort;
...
end;
When executed, this code should display a message box with "#elifdef ONE", but it shows "#else" instead. If you uncomment '#define ZERO 1' statement, compiler may generate error C8059 (this is not always consistent and may depend on the code layout in setup.rul file).
Workarounds:: Use #elif or #ifndef instead of #elifdef.
Status:: InstallShield has confirmed that this is a problem in ISD 7.02 - 8.02 and DevStudio 9.00.
Created: 2002-04-15 Last update: 2002-06-06 InstallShield tracking number: 1-78TUE

SHELL_OBJECT_FOLDER can't be Used to Specify Shortcut Folder

Description:: According to the documentation for Standard projects you can use the InstallScript variable SHELL_OBJECT_FOLDER to specify in which folder (program group) your shortcuts should be placed. This doesn't work. Entering SHELL_OBJECT_FOLDER in the Display Name property for a program folder in shortcuts view creates a string table entry with value "SHELL_~1|SHELL_OBJECT_FOLDER" instead.
Workarounds:: Use all capital letters for the folder name (directory identifier).
Status:: InstallShield has confirmed that this is a problem in ISD 7.02 - 8.02 and DevStudio 9.00.
Created: 2002-02-26 Last update: 2002-06-06 InstallShield tracking number: 1-802HL

IsRegSpy Error During COM Extraction

Description:: While adding a OCX using the Component Wizard you may get the following error during the COM Information Extraction process: "The instruction at 0x00409e6d referenced memory at 0x00000004. The memory could not be read. Click OK to terminate the program." and the program identified by this error message is IsRegSpy.exe. The same can happen while building the release if you selected the option to extract self registration information during the build.
Cause:: This error message is caused by a problem with the new COM extraction mechanism in ISD 7.02.
Workarounds:: This zip file includes a fixed version of IsRegSpy. Copy the two included file to the System folder in your InstallShield Developer program directory.
IsRegSpyFix.zip Written by Mingbiao Fei (InstallShield Software Corp.)
File size: 102.040 bytes Last update: 2002-02-02
Alternatively you can switch back to the old (pre 7.02) COM extraction method by setting the following registry entry to string value "y":
HKEY_CURRENT_USER\Software\InstallShield\Developer\7.0\UseOldComExtraction
Status:: InstallShield has confirmed that this is a problem in ISD 7.02 - 8.02 and DevStudio 9.00.
Created: 2002-01-22 Last update: 2002-06-14 InstallShield tracking number: 1-78UD1

Major Upgrade Patch Fails for Standard Projects

Description:: You cannot install a major upgrade to a Standard project as a patch. If you try you will receive error 1628. A major upgrade as full release instead of patch should work. Basic MSI projects are not affected by this problem.
Cause:: There's a bug in patch wizard that it always passes the new product guid to the InstallScript engine, so the engine can't find the product on the machine, of course.
Workarounds:: Release your major upgarde as full product instead of a patch or use a Basic MSI project.
Status:: This problem has been reported for ISD 7.02. InstallShield is unaware of anyone who has gotten it to work for Basic MSI either. If you have a working major upgrade patch (created with any tool) please contact the webmaster.
Created: 2002-01-04 Last update: 2002-06-06

Graphics not Visible in Dialog Editor for Standard Projects

Description:: Cannot see bitmaps on predefined dialogs in Standard projects. The bitmaps are displayed properly during runtime. Note that Standard Projects only support BMP and ICO files, no other graphic formats.
Workarounds:: None.
Status:: InstallShield has listed this problem as open issue in the release notes for ISD 7.0. Not fixed in ISD 7.01 - 8.02 and DevStudio 9.00.
Created: 2001-08-18 Last update: 2002-06-06 InstallShield tracking number: 1-6A3R2

Components not Deleted in Project Wizard

Description:: Create a new standard project using the project wizard. In the 'Application Files' page, add some files to a feature. Then remove these files. Complete the new project wizard. In the File View of the new project, note that components for the files which were added/removed exist, however no files are associated with them (ensure that show components is enabled).
Workarounds:: Manually delete these components from the project after the wizard is completed.
Status:: InstallShield has confirmed that this is an issue in ISD 7.00 - 8.02.
FIXED in DevStudio 9.00
Created: 2001-09-29 Last update: 2002-06-06 InstallShield tracking number: 1-6A3QL

PathAdd Sometimes Fails to Add Path

Description:: PathAdd doesn't add a path to the path buffer if a similar entry already exists that is only different in the "extension" of the path. Code sample:
nResult = PathAdd("c:\\dir.1\\test", "", FULL, AFTER);
nResult = PathAdd("c:\\dir.2\\test", "", FULL, AFTER);
The resulting path is just "c:\dir.1\test".
Workarounds:: Use the path function replacements in this package.
Status:: InstallShield confirmed that this is a problem in ISD 7.03 - 8.02 and DevStudio 9.00. It is also reproducible in ISD 7.00 and in InstallShield Professional Standard Edition 6.x. InstallShield has accepted this as a bug in IS 6.30 and 6.31. The function worked properly in IS 5.53.
Created: 2001-09-15 Last update: 2002-06-06 InstallShield Tracking Number: 1-6JJL1 (1-6L1KD for IS 6.3)

Adminstrative Installation of Standard Project is Incomplete

Description:: Running an administrative installation of a Standard project will copy the msi file and the application files, but not setup.exe and setup.ini, which are required for standard projects.
Workarounds:: Use CopyFile to copy the missing files to the admin install location, or use a Basic MSI project.
Status:: InstallShield has confirmed that this is a bug in ISD 7.00 - 8.02 and DevStudio 9.00.
Created: 2001-08-30 Last update: 2002-06-06 InstallShield tracking number: 1-6JAXG

IDE Appears to Hang While Upgrading IPWI 2.x Project

Description:: The Installation Development Environment (IDE) appears to hang at the UIText table when trying to upgrade a 2.03 project if the project is created after installing language packs.
Cause:: This happens as the upgrade code is upgrading all the strings (in all languages) to the Developer 7.0 project format.
Workarounds:: Wait until the upgrade is finished.
Status:: InstallShield has listed this problem as open issue in the release notes for ISD 7.00. Not fixed in 7.01 - 8.02 and DevStudio 9.00.
Created: 2001-08-18 Last update: 2002-06-06 InstallShield tracking number: 1-68IWC

One-Click Installs cannot be Launched from the IDE

Description:: One-Click Install setups cannot be run from the IDE.
Cause:: One-Click Install Setups must be located on the URL specified in the release settings in order for the install to work. Therefore, they cannot be run from their default release location under MySetups.
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.02 and DevStudio 9.00.
Created: 2001-08-18 Last update: 2002-06-06 InstallShield tracking number: 1-67L1K

Setup Hangs in FeatureTransferData Call

Description:: Calling FeatureTransferData an extra time on the same media causes the install to hang.
Cause:: FeatureTransferData is already called by the runtime code. The functionality to call it more than once will be available in a future release.
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.02 and DevStudio 9.00.
Created: 2001-08-18 Last update: 2002-06-06 InstallShield tracking number: 1-69VHY

INSTALLDIR can't be Modified in Merge Module Projects

Description:: Not able to modify INSTALLDIR in Merge Module properties in a Merge Module project. INSTALLDIR cannot reference itself.
Workarounds:: For example, if INSTALLDIR is currently [ProgramFilesFolder]mydir, and you want to change it to be in mydir\subdir instead, do not set the value of INSTALLDIR to be:
[INSTALLDIR]subdir
instead, set it to:
[ProgramFilesFolder]mydir\subdir
Status:: InstallShield has listed this problem as open issue in the release notes for ISD 7.00. Not fixed in ISD 7.01 - 8.02 and DevStudio 9.00.
Created: 2001-08-18 Last update: 2002-06-06 InstallShield tracking number: 1-69A7A

Custom Uninstall DLL not Migrated from IS5 Projects

Description:: InstallShield 5 projects with custom uninstall DLLs are not migrated correctly.
Workarounds:: Convert the program…endprogram block in InstallScript to an event-based setup. This will allow for custom code (in InstallScript or in a DLL) to be called during uninstall by authoring it in the Maintenance events.
Status:: InstallShield has listed this problem as open issue in the release notes for ISD 7.00. Not fixed in ISD 7.01 - 8.02.
FIXED in DevStudio 9.00
Created: 2001-08-18 Last update: 2002-06-06 InstallShield tracking number: 1-67TF7

Component Wizards Asks for Version Independent ProgId

Description:: Component Wizard | COM Server option | Classes panel should not require a Version Independent ProgId.
Workarounds:: Enter a Version Independent ProgId and then delete it from under the component's Advanced Settings | COM Registration node.
Status:: InstallShield has listed this problem as open issue in the release notes for ISD 7.00. Not fixed in ISD 7.01 - 8.02 and DevStudio 9.00.
Created: 2001-08-18 Last update: 2002-06-06 InstallShield tracking number: 1-6AT7W

DirectX and MSDE Objects don't Work in Releases with Compressed Media

Description:: Compressed Setup of DirectX 8 and MSDE object won't install.
Workarounds:: Build uncompressed releases when including DirectX 8 or MSDE object and use PackageForTheWeb to package the setup into a single EXE.
Status:: InstallShield has listed this problem as open issue in the release notes for ISD 7.00. Not fixed in ISD 7.01 - 8.02 and DevStudio 9.00.
Created: 2001-08-18 Last update: 2002-06-06 InstallShield tracking number: 1-6CFGR

Dialog Box When Double-Clicking an Advertised Shortcut

Description:: Activating an advertised shortcut that was created using a Standard setup results in a message box displayed before the installation completes.
Workarounds:: To prevent this message from being displayed, remove the code in the OnMsiSilentInstall event. This event is under the category Miscellaneous in the Script Editor combo box.
Status:: InstallShield has listed this problem as open issue in the release notes for ISD 7.00. Not fixed in ISD 7.01 - 8.02 and DevStudio 9.00.
Created: 2001-08-18 Last update: Last update: 2002-06-06 InstallShield tracking number: 1-69O0O