Shop more / weitere 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.01

Version: 7.01
Release Date: October 30, 2001
Download: Select "Check for Updates" from the Help menu or download from http://support.installshield.com/updates/updates.asp. This is a 25 MB patch package. It is not applicable to the German edition that is already at version 7.01.
Release Notes: A list of enhancements, fixes and open issues is available at http://www.installshield.com/downloads/isd/release_notes/dev7.01.asp

Known Problems in ISD 7.01

OnUninstall() Causes Compile Error

Description:

Adding the OnUninstall( ) event handler to the script results in a compile error.

Workarounds:

Removing this line from the script will result in proper compilation of the script.

Status:

InstallShield has listed this problem as open issue in the release notes for ISD 7.0.
FIXED in ISD 7.02.

Created: 2001-08-18   Last update: 2002-01-22   InstallShield tracking number: 1-68HK9

Build Errors in Standard Projects with Languages Other than English

Description:

Under some circumstances, build errors may occur in Standard projects when Developer is installed with languages other than English.

Workarounds:

Select Reset Custom Actions from the Project menu and then rebuild your project.

Status:

InstallShield has listed this problem as open issue in the release notes for ISD 7.0.
FIXED in ISD 7.02.

Created: 2001-08-18   Last update: 2002-01-22   InstallShield tracking number: 1-6C8IO

ExistsDisk Fails if Drive Specification Includes Colon

Description:

ExistsDisk function fails when the drive letter is followed by colon.

Workarounds:

Do not use the colon when specifying a drive letter.

Status:

InstallShield has listed this problem as open issue in the release notes for ISD 7.0.
FIXED in ISD 7.02.

Created: 2001-08-18   Last update: 2002-01-22   InstallShield tracking number: 1-68IHU

Dialog Export not Working

Description:

If you right click on the language sub node of a dialog (e.g. SdFeatureDialog2/English) and select "Export to Dialog File", the dialog will not exported.

Workarounds:

Right click on the dialog name instead of the language sub node (e.g. SdFeatureDialog2) and select "Export to Dialog File".

Status:

InstallShield has confirmed that this is a bug in ISD 7.00.
FIXED in ISD 7.02.

Created: 2001-09-15   Last update: 2002-01-22   InstallShield tracking number: 1-6R7KX

Error 1911 "Could not Register Type Library"

Description:

Error 1911 "Could not register type library for file [2]. Contact your support personnel." during installation of one or more components on the target system. All dependencies are installed correctly, and the components that raise the 1911 error register properly when you use regsvr32 (dll/ocx) or the /regserver command-line switch (EXE). The components are set up correctly in Installshield.
The components that cause the error message are configured to use "extract at build" for their COM registration information. The problem only seems to occur after binary compatibility has been broken (as it often is, during development), and when you are using the same machine for compilation of the application object files and creation of the install set..

Cause:

The "extract at build" functionality appears to be using the registry information for the wrong (old) versions, and is using the wrong interface identifier information/registry information. This is what generates the 1911 error.
Note: Error 1911 can also be caused by missing dependencies, locale-specific components, corrupted object files, and several other causes. It is a bit of a catch-all message for COM registration problems.

Workarounds:

To avoid the problem unregister the components before you build the new version that is not binary compatible. If you already have outdated information in the registry of your development machine, run RegClean from Microsoft or a similar tool to remove the incorrect registry entries. Alternatively, create the install set from a machine with a fresh OS installation. RegClean can be downloaded from these locations: ftp://ftp.uakom.sk/pub/mirrors/sac/utilmisc/regcln41.exe or ftp://ftp.cs.tu-berlin.de/pub/msdos/mirrors/stuba/pc/utilmisc/regcln41.exe

Status:

This problem das been reported for ISD 7.00 as well as for ISWI 1.x and IPWI 2.x.
FIXED in ISD 7.02.

Created: 2001-09-15   Last update: 2002-01-22   InstallShield tracking number: 1-5TF0Q

Build Error "Missing binary entry"

Description:

While building a project you may receive errors like these:
** Error: Missing binary entry _ISRES1046.DLL  To repair the scripting architecture, select the "Reset InstallShield Custom Actions" option on the Project menu.
** Error: Missing binary entry String1046.txt  To repair the scripting architecture, select the "Reset InstallShield Custom Actions" option on the Project menu..

Workarounds:

Selecting the menu option will fix the problem without any side effects.

Status:

InstallShield has confirmed that this is a bug in ISD 7.00.
FIXED in 7.02.

Created: 2001-09-15   Last update: 2002-01-22   InstallShield tracking number: 1-6SPV4

ReserveCost Table Ignored in Standard Projects

Description:

You can add entries to the ReserveCost table to increase the displayed size of a component. However this only works in Basic MSI projects. In Standard projects the ReserveCost table is not taken into account.

Workarounds:

Use a Basic MSI project.

Status:

InstallShield has confirmed that this is a bug in ISD 7.00 - 7.01.
FIXED in ISD 7.02

Created: 2001-08-30   Last update: 2002-01-04   InstallShield tracking number: 1-6JAXB

Installation Fails After Updating vom ISD 7.00 to 7.01

Description:

After you updated InstallShield Developer from version 7.00 to 7.01 by installing the first maintenance pack, the setups you create may fail with error 1628: "Failed to complete installation." In the log file you find the message "This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service."

Cause:

Setups created with ISD 7.01 require MSI 2.0. However but the MsiVersion specified in setup.ini is still 1.2, so MSI 2.0 won't get installed on systems that already have MSI 1.2.

Workarounds:

Go to registry entry HKEY_LOCAL_MACHINE\Software\InstallShield\Devloper\7.0 and change the string entry named "Msi Version" to "2.0.2600.0".

Status:

InstallShield has confirmed that this is a bug in the first release of the patch that updates ISD from version 7.00 to 7.01. The full release version of 7.01 is not affected by this problem.
FIXED: The ISD 7.01 patch has been corrected..

Created: 2001-11-06   Last update: 2001-12-19

Setup Doesn't Reboot After Updating the MSI Engine

Description:

If you selected to delay the MSI engine reboot your setup should request a reboot at the end of the installation if it updated the MSI engine to version 2.0. This works if you created the project with ISD 7.01. However if you created the project with ISD 7.00 or any previous tool and later updated it to ISD 7.01 your setup will not request this required reboot.

Workarounds:

At the end of the InstallExecute sequnce insert the ScheduleReboot standard action with a condition of ISSCHEDULEREBOOT.

Status:

InstallShield has listed this as an known issue in the release notes for ISD 7.01.
FIXED in ISD 7.02.

Created: 2001-11-06   Last update: 2001-12-19   InstallShield tracking number: 1-6WTYV

Wrong Icon in Caption of Custom Dialogs

Description:

Your custom dialogs may display the default Windows icon instead of the installer icon in the upper left corner. This only applies to Standard projects.

Cause:

In order to display the correct icon the following style bits must be selected for the dialog:
WS_POPUP
DS_SETFONT
DS_MODALFRAME
The dialog editor erroneously adds DS_SYSMODAL.

Workarounds:

Go into the Dialog table in the Direct editor. There you will find a column named "ISWindowStyle". This is where the Window Style from the Dialog editor is stored, and later used to build the .rc file. This number should be -2134376256.

Status:

InstallShield has confirmed that this is a bug in ISD 7.00.
FIXED in ISD 7.02.

Created: 2001-10-15   Last update: 2001-12-19   InstallShield tracking number: 1-6YCNO

Patch Wizard doesn't Create MSP File

Description:

When running the Patch Wizard it may appear to have completed successfully, but it doesn't create a MSP file. This happens if the new version of the MSI file was built with ISD7, but the old version was created with a previous tool, like IPWI 2.03. Using Microsoft's msimsp.exe to create the patch result in error 0xC00E5173.
Note: MSP files can only be created from Basic MSI project. Standard projects always use Update.exe instead. This is by design.

Cause:

ISD7 is built to support MSI 2.0 technology. Unfortunately the schema (msi) between 1.2 and 2.0 changed: the Version column in the TypeLib table changed from Short to Long integer, so the built msi schema changes as well.

Workarounds:

Export the TypeLib table in the old msi, change the Version column data type to I4 (from I2), delete the Typelib table, and then import the edited idt file.

Status:

This problem has been reported in the newsgroups for ISD 7.00.
FIXED in ISD 7.02.

Created: 2001-09-29   Last update: 2001-12-19   InstallShield tracking number: 1-6SPTW

Error 91 During Import of IS 5 Project

Description:

While converting a project that was originally created with InstallShield professional 5 you may get an error message like this:
** Error 91: Object variable or With block variable not set
    > IsIsmMigrate.CIsProMigrate.MigrateMediaItem
    > IsIsmMigrate.CIsProMigrate.MigrateMedia

Workarounds:

Delete the Media folder.

Status:

This problem has been reported in the newsgroups for ISD 7.00.
FIXED in ISD 7.02.

Created: 2001-09-15   Last update: 2001-12-19   InstallShield tracking number: 1-6QGS5

VerFindFileVersion fails in Basic MSI Project

Description:

Calling VerFindFileVersion in a Basic MSI project will always return -1.

Cause:

Internally the TARGETDIR variable isn't set.

Workarounds:

Set TARGETDIR before calling VerFindFileVersion. Don't use INSTALLDIR instead. You must use the system variable TARGETDIR, even though TARGETDIR will not have the color of other system variables or keywords. Samle code:

function MyFunction(hMSI)
    int    nReturn, nBuf;
    string szFileName, svPath, svVersionNumber, szPathBuf[MAX_PATH];
begin
    nBuf = MAX_PATH;
    MsiGetTargetPath(hMSI, "INSTALLDIR", szPathBuf, nBuf);
    TARGETDIR = szPathBuf;
    szFileName = "Notepad.exe";
    nReturn = VerFindFileVersion(szFileName, svPath, svVersionNumber);
    SprintfBox(INFORMATION , "Version", "%d\n%s\n%s", nReturn, svPath,
               svVersionNumber, 0);
end;

Status:

InstallShield has confirmed that this is a bug in ISD 7.00.
FIXED in ISD 7.02.

Created: 2001-09-15   Last update: 2001-12-19   InstallShield tracking number: 1-6IZKN

File Transfer Fails in Child Setup Launched with DoInstall

Description:

A child setup launched with DoInstall after a parent setup finishes file transfer fails during its file transfer.

Workarounds:

Call DoInstall before the Move data event in the script.

Status:

InstallShield has listed this problem as open issue in the release notes for ISD 7.0.
FIXED in ISD 7.02.

Created: 2001-08-18   Last update: 2001-12-19   InstallShield tracking number: 1-6ATCT

ODBC Drivers not Migrated when Importing IS6 Project

Description:

When migrating an InstallShield Professional project to InstallShield Developer, the ODBC drivers for SQL Server, Oracle, and Access do not migrate.

Workarounds:

Uncheck the ODBC drivers before migration and re-add them to your Developer project within the IDE.

Status:

InstallShield has listed this problem as open issue in the release notes for ISD 7.00.
FIXED in ISD 7.02.

Created: 2001-08-18   Last update: 2001-12-19   InstallShield tracking number: 1-6CLBP

Shortcuts with Absolute Path not Migrated Properly

Description:

A shortcut target property that has an absolute path will fail to install upon migration. This is because the value in the shortcut target property in the migrated project will be of the format PROPERTY1.

Workarounds:

Enclose this value in square braces [] (for example: [PROPERTY1]).

Status:

InstallShield has listed this problem as open issue in the release notes for ISD 7.00.
FIXED in ISD 7.02.

Created: 2001-08-18   Last update: 2001-12-19   InstallShield tracking number: 1-6ANAC

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

InstallShield Developer 7.00

Version: 7.00
Release Date: August 8, 2001
Release Notes: A list of fixed bugs and open issues can be found at http://www.installshield.com/downloads/isd/release_notes.asp

Known Problems in ISD 7.00

Sequences/Action View in IDE is Blank

Description:

The Sequences/Actions view in the IDE sometimes doesn't display anything. This happens if Internet Explorer 6.0 is installed on your development machine.

Workarounds:

An updated DLL that fixes this incompatibility with IE6 is available upon request from InstallShield support (Mike Marino). Another option is to close the project (not the IDE) an re-open it.

Status:

InstallShield has confirmed that this is a bug in ISD 7.00.
FIXED in ISD 7.01.

Created: 2001-09-29   Last update: 2001-12-19   InstallShield tracking number: 1-6QYAQ

IDE Tries to Establish Internet Connection

Description:

When launching the IDE your computer may try to dial up an internet connection.

Cause:

The IDE tries to update the InstallShield Today page. However, if a live connection is not present, it should not be dialing to an ISP.

Workarounds:

Rename agent.exe in the updates directory, and replace it with an empty file called agent.exe. This will disable the automatic update functionality.

Status:

InstallShield has confirmed that this is a problem in ISD 7.0.
FIXED in ISD 7.01.

Created: 2001-08-18    Last update: 2001-10-25   InstallShield tracking number: 1-6JB2X

Wrong SUPPORTDIR in Basic MSI Projects

Description:

File you add to the Setup Files pane should be extracted to SUPPORTDIR during setup initializaton. However SUPPORTDIR points to a directory like C:\documents and settings\administrator\temp\{...some GUID...} while the files are extacted to a similar directory but with a different GUID in the end. This only happens with Basic MSI projects. Standard projects are not affected.

Workarounds:

None.

Status:

InstallShield has confirmed that this is a bug in ISD 7.00.
FIXED in ISD 7.01

Created: 2001-10-22    Last update: 2001-10-25    InstallShield tracking number: 1-6UZA5

Memory Leaks in IDE

Description:

There are various reports about memory leaks in the ISD7 IDE:
When navigating between different components in the Setup Design view, each time you select a component, the system will freeze (CPU usage 100%) for a while and the RAM usage will increase by approx. 1Mb. The time it freezes also increases the longer the system is used.
In a merge module project, the mouse_over event of the right most pane in the IDE has an 8K memory leak. To reproduce start or open a merge module project. Place the mouse over the right most pane, the default startup page in this pane is the Organize Your Setup pane. Watch the memory usage climb 8K at a time through Windows Task Manager.

Workarounds:

None.

Status:

InstallShield has confirmed that this is a bug in ISD 7.00.
FIXED in ISD 7.01.

Created: 2001-09-15    Last update: 2001-10-22    InstallShield tracking number: 1-6KU0H

ICE03 Error for ISSetupFile Table in Standard Project

Description:

Validating a Standard project gives the following message: "ICE03 Error Table: ISSetupFile Column: ISSetupFile Missing specifications in _Validation Table (or Old Database)".

Workarounds:

None.

Status:

InstallShield confirmed that this is a bug in ISD 7.00.
FIXED in ISD 7.01.

Created: 2001-10-22   InstallShield tracking number: 1-6OAP3

Runtime Error 1714 During Major Upgrade with Standard Project

Description:

When applying a major upgrade using the Standard project type, you may receive error 1714 "The older version of [ProductName] cannot be removed. Contact your technical support group. System Error 1605." It doesn't matter whether the old version was a Basic MSI or Standard project, but it only happens if the new version is a Standard project. Basic MSI projects are not affected.
This error is only displayed with MSI engine version 1.2. Error 1714 was not available in earlier versions, and MSI 2.0 is not affected by the problem.

Cause:

FindRelatedProduct standard action is scheduled in both InstallUISequence and InstallExecuteSequence. In a Basic MSI project this is not a problem, the second instances is automatically skipped. However in a Standard project FindRelatedProduct is executed twice. As a result the product code of the old product is added twice to the action property, and the MSI engine tries to remove the old product twice. This obviously fails for the second try. MSI 2.0 detects this situation and ignores the duplicate entry, as indicated by the log entry "Ignore the failure, product already removed".

Workarounds:

Go to Sequences view, expand the Execute sequence, and select the FindRelatedProducts action. In the properties sheet (upper-right), add the following value to the Condition property:
  Not ISSETUPDRIVEN
Also insert the following custom action after the RemoveExistingProducts action to get rid of the obsolete uninstall entry:
function RemoveOldProductsRegKey(hMSI)
    STRING szOldProducts, svDest, szSubKey;
    NUMBER nResult, nSize, nEndPos;
begin
    nSize = 128;
    nResult = MsiGetProperty(ISMSI_HANDLE, "OLDPRODUCTS", szOldProducts, nSize);
    nEndPos = StrFind(szOldProducts, ";");
    CopyBytes(svDest, 0, szOldProducts, 0, nEndPos);
    RegDBSetDefaultRoot(HKEY_LOCAL_MACHINE);
    szSubKey = "Software\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\InstallShield_" + svDest;
    nResult = RegDBKeyExist(szSubKey);
    if ( nResult = 1 ) then
        RegDBDeleteKey(szSubKey);
    endif;
end;
Written by Simon McMullon

Status:

InstallShield has confirmed that this is a bug in ISD 7.00.
FIXED in ISD 7.01.

Created: 2001-09-29    Last update: 2001-10-22    InstallShield tracking number: 1-68F9Q

Cannot Retrieve CustomActionData from a Deferred Custom Action

Description:

To retrieve properties from a custom action with deferred executaion you must use the CustomActionData workaround documented by Microsoft. However if your custom action is written in InstallScript this method doesn't work.

Cause:

In ISD 7 InstallScript custom actions run in a separate process (IDriver.exe). This makes the CustomActionData workaround obsolete. Instead you can directly access properties even from deferred execution custom actions.

Workarounds:

For data you want to pass from one InstallScript action to another, use global variables in your script.

Status:

This is by design. You can get the property even in a deferred CA without the CustomActionData workaround.
FIXED in ISD 7.01.

Created: 2001-08-18   Last update: 2001-10-22    InstallShield tracking numbers: 1-6EBM6, 1-6JB32

Do(EXIT) and abort Don't Work in Feature Events

Description:

Do(Exit) and abort do not work properly in Feature events.

Workarounds:

Do not call these functions in feature events. They work when called from any of the global events.

Status:

InstallShield has listed this problem as open issue in the release notes for ISD 7.0.
FIXED in ISD 7.01.

Created: 2001-08-18   Last update: 2001-10-22    InstallShield tracking number: 1-6B206

Importing and Exporting Binary Registry Entires Corrupts Data / Runtime Error 1406

Description:

Both importing and exporting a binary registry entry (hex data) from and to a .reg file do not work correctly. When importing, ISD7 adds a space between bytes, which results in Error 1406 "Could not write value [2] to key [3]. Verify that you have sufficient access to that key, or contact your support personnel. " when trying to install those particular registry keys. In addition, when exporting, ISD7 prefixes the entry data with the "#x" identifier in the .reg file. Example:
"KeyValue"=hex:#x[byte1][byte2][byte3].....
In other cases it does not prefix exported entries with #x but instead writes wrong values.

Workarounds:

Go to the Registry view and remove the obsolete blanks from the binary value.

Status:

InstallShield confirmed that this is a bug in ISD 7.00.
FIXED in ISD 7.01.

Created: 2001-08-30   Last update: 2001-10-22    InstallShield tracking numbers: 1-6GP9I, 1-6GP9Q, 1-6JB2D

IDE Freezes in Component Wizard

Description:

Using the component wizard to create a new component, after selecting the file for the new component, the IDE may sometimes stop responding.

Workarounds:

A set of three updated DLLs that fixes this problem is available upon request from InstallShield support (Mike Marino).

Status:

InstallShield has confirmed that this is a bug in ISD 7.00.
FIXED in ISD 7.01.

Created: 2001-09-15   Last update: 2001-10-22    InstallShield tracking number: 1-6PJRF

File Extension can't be Deleted from Components Advanced Settings

Description:

In order to associate an extension with your application, you add a file type entry in the Advanced Settings of your component, under File Types -> Extensions. However you canot delete such an extension entry.

Workarounds:

Go to the Direct Editor and delete the extension from the Extension table and delete the associated verb from the verb table.

Status:

InstallShield has confirmed that this is a bug in ISD 7.00.
FIXED in ISD 7.01.

Created: 2001-08-30   Last update: 2001-10-22    InstallShield tracking numbers: 1-6D0RU, 1-6JAWW

MSDE 2000 Merge Modules (Microsoft SQL Server 2000 Desktop Engine) not Merged Properly

Description:

ISD7 does not properly merge the MSDE 2000 Merge Modules (Microsoft SQL Server 2000 Desktop Engine).

Workarounds:

An updated iswibuild.dll is available from InstallShield knowledge base article Q105517.

Status:

InstallShield has confirmed that this is a bug in ISD 7.00.
FIXED in ISD 7.01.

Created: 2001-09-29   Last update: 2001-10-22    InstallShield tracking number: 1-6SPTE

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

Description:

When you build a release you may get the message "Fatal Error: -3016: Failed to add Binary table ISSELFREG.DLL to package". This happens if your project includes files that are marked as self registering and also includes the "InstallShield Merge Module for OLE DB 2.1" (OLEDB21.msm).

Cause:

The Merge Module and your project both contain a Binary Entry with the ID ISSELFREG.DLL.

Workarounds:

An updated OLEDB21 merge module is available upon request from InstallShield support (Mike Marino)..

Status:

InstallShield has confirmed that this is a bug in ISD 7.00.
FIXED in ISD 7.01.

Created: 2001-09-15   Last update: 2001-10-22    InstallShield tracking number: 1-6SPUD

Incorrect Date and Time Information in the Summary Information Stream

Description:

When you examine the MSI file generated by ISD you may notice that the following incorrect date and time information is stored in the Summary Information stream (all times GMT):
  Created: 4/14/99 7:00:00 AM
  Last Saved: 5/15/99 3:39:16 PM
  Last Printed: 5/15/99 3:39:16 PM
The date and time information displayed in the Direct Editor are only place holders that should be replaced during the build process with the current data. However this doesn't work properly.
MSI files that you open in Direct Mode in ISD7 are not affected by this problem.

Workarounds:

Open the built MSI in Direct Mode in ISD7 or in Orca and correct the settings.

Status:

InstallShield has confirmed that this is a bug in ISD 7.00.
FIXED in ISD 7.01.

Created: 2001-09-29   Last update: 2001-10-22    InstallShield tracking number: 1-6SPTR

Empty Directory is Created on Target Machine when no Files are Installed

Description:

INSTALLDIR automatically gets entered in CreateFolder table, resulting in a folder being created on the target machine regardless of whether files are installed.

Workarounds:

Go to the CreateFolder table in the Direct Editor and delete the unnecessary entries.

Status:

InstallShield has listed this problem as open issue in the release notes for ISD 7.0.
FIXED in ISD 7.01.

Created: 2001-08-18   Last update: 2001-10-22    InstallShield tracking number: 1-6BF1W

Cannot Specify Disk Volume Label in Release Wizard

Description:

If you specify a volume label in the release wizard, this change will not take effect. ISD will still use the default of "DISK?".

Cause:

The Release Wizard doesn't change the changes for the volume label.

Workarounds:

Go to the ISLogicalDisk table in the Direct Editor and change the entry in the VolumeLabel column.

Status:

InstallShield has confirmed that this is a limitation in ISD 7.00.
FIXED in ISD 7.01.

Created: 2001-09-29   Last update: 2001-10-22    InstallShield tracking number: 1-6MRWX

ICE 20 Errors when Validating a Standard Project

Description:

When you run validation on a standard projects you will get ICE 20 errors like this: "Standard Dialog: 'FilesInUse' not found in Dialog table". This does not happen in Basic MSI projects.

Cause:

ICE makes sure that the default dialogs exist in the package. However Standard Projects use an external user interface (with InstallScript) and therefore don't include Windows Installer's default dialogs.

Workarounds:

ICE validation doesn't apply to setups with external user interface (like Standard Projects). You can safely ignore them.

Status:

This is by design. A feature request has been submitted to exclude the ICE20 suite when validating Standard projects.
FIXED in ISD 7.01.

Created: 2001-09-15   Last update: 2001-10-22  InstallShield tracking number: 1-6L0PU

Unwanted Languages in Dialog Editor

Description:

All available languages are shown in the Dialogs view even if it is non-multilingual project.

Workarounds:

None.

Status:

InstallShield has listed this problem as open issue in the release notes for ISD 7.0.
FIXED in ISD 7.01.

Created: 2001-08-18   Last update: 2001-10-22  InstallShield tracking number: 1-6AKHD

Internal Build Error -5013 in Project Migrated from IPWI

Description:

Windows 2000 Display Icon (ARPPRODUCTICON) value is not upgraded from 2.03 projects.

Workarounds:

Manually add the file in the General Information | Windows 2000 property sheet.

Status:

InstallShield has listed this problem as open issue in the release notes for ISD 7.00.
FIXED in ISD 7.01.

Created: 2001-08-18   Last update: 2001-10-22  InstallShield tracking numbers: 1-6EBL9, 1-6BF1D

ServiceInstall.Dependencies not Populated Properly

Description:

When you create a new project and add a Service Install, setting the Dependency property to "Dep1,Dep2", the ServiceInstall table incorrectly displays this as Dep1[~]Dep2 instead of Dep1[~]Dep2[~][~]. This results in improper registration of the dependent services.

Workarounds:

Go to the ServiceInstall table using the Direct Editor and put the additional [~][~] next to the last dependency in the Dependencies column.

Status:

InstallShield has listed this problem as open issue in the release notes for ISD 7.0.
FIXED in ISD 7.01.

Created: 2001-08-18   Last update: 2001-10-22  InstallShield tracking number: 1-6C84P

Building a Release takes Extremely Long while Adding Files

Description:

Building a release may seem to pause after the "Language English (United States) built" step of the build. This is the phase when your application files are added to the CAB files.

Cause:

When compression is optimized for size, the disk image that is created for the installation is significantly smaller, but it does take a longer time to build.

Workarounds:

In the releases view, click on the release you are building.  In the release's property grid, change the Optimize Size property to No (it is set to Yes by default).

Status:

Size Optimization is a new feature in ISD 7.00, and the slow down is a side effect.
FIXED in ISD 7.01: the default for new releases is now optimized for speed.

Created: 2001-08-30   Last update: 2001-10-22  InstallShield tracking number: 1-6J8A3

Access 2000 Merge Module Overwrites Existing Access 97 Installation

Description:

The Access 2000 merge module installs the Access 2000 runtime in the default directory (e.g. C:\Program Files\Microsoft Office\Office) thus overwriting a pre-existing Access 97 runtime in the same location. The installation directory cannot be changed.

Workarounds:

An updated Access 2000 merge is available upon request from InstallShield support (Mike Marino). It supports a property ACCESS2000INSTALLLOCATION that can be used to change the installation directory.

Status:

InstallShield has confirmed that this is a bug in the Access 2000 merge module included in ISD 7.0.
FIXED in ISD 7.01.

Created: 2001-08-18   Last update: 2001-10-22  InstallShield tracking number: 1-6JB2S

IDE Crashes When Inserting Custom Action into Sequence Tree

Description:

If you right click on the root node of a sequence tree ("User Interface" or "Execute"), select Insert, pick a custom action from the dialog and press the OK button, you may get a Visual C++ runtime error "abnormal program termination" for ISDEV.EXE.

Workarounds:

Instead of the root node, select the first action in the sequence. This will insert your custom action as second action in the sequence. Now right click the first action again and select "Move Down". This will move your custom action to the first position of the sequence.

Status:

InstallShield has confirmed that this is a bug in ISD 7.0.
FIXED in ISD 7.01.

Created: 2001-08-18   Last update: 2001-10-22  InstallShield tracking number: 1-6JB2N, 1-6EGZR

Cannot Access String Table Entries in Basic MSI Project

Description:

A custom action written in InstallScript in a Basic MSI project cannot use string table entries in the form @STRING_IDENTIFIER. This used to work properly in IPWI 2.x. Standard projects are not affected by this problem.

Workarounds:

None.

Status:

InstallShield has confirmed that this is a bug in ISD 7.00.
FIXED in ISD 7.01.

Created: 2001-08-30    Last update: 2001-10-22  InstallShield tracking numbers: 1-6J8AB, 1-6ILG5

Program and Type Library IDs Sometimes not Displayed in IDE

Description:

For components containing a large number of ProgIDs, only the COM classes are displayed in the Advanced Settings | COM registration section of the Component or Setup Design views. The program IDs and type library IDs are not displayed.

Workarounds:

Use the Direct Editor to view the program IDs and type library IDs for this component.

Status:

InstallShield has listed this problem as open issue in the release notes for ISD 7.0.
FIXED in ISD 7.01.

Created: 2001-08-18   Last update: 2001-10-22   InstallShield tracking number: 1-6D72X

Can't Create InstallScript Custom Actions Directly by Entering Type Value

Description:

Instead of using the Custom Action wizard you can directly create a new custom action and populate the property values manually. However the type field does not accept values above 8191 which are required for InstallScript custom actions.

Workarounds:

Run the Custom Actions wizard to create InstallScript custom actions.

Status:

InstallShield has confirmed that this is a bug in ISD 7.00.
FIXED in ISD 7.01.

Created: 2001-10-22    InstallShield tracking number: 1-6GP8V

ISReleaseFlags Property Missing

Description:

Any release flags you specified in the Product Configuration settings, e.g. to filter Features for different release types, should be listed at runtime in property ISReleaseFlags so that you can build conditions based on these flags. However the ISReleaseFlags property is not added to the built MSI package.

Workarounds:

None.

Status:

InstallShield has confirmed that this is a bug in ISD 7.00.
FIXED in ISD 7.01.

Created: 2001-10-22   InstallShield tracking number: 1-6OKIG

Custom Dialogs Fail in Multi Language Setup

Description:

In a Standard project that supports multiple languages the WaitOnDialog function returns error -1 for custom dialogs. If your setup supports only one languages, the function correctly returns -100 (DLG_INIT).

Workarounds:

An updated iswibuild.dll is available upon request from InstallShield support.

Status:

InstallShield has confirmed that this is a bug in ISD 7.00.
FIXED in ISD 7.01.

Created: 2001-10-22   InstallShield tracking number: 1-6ORV5

InstallScript Custom Actions don't Run in Major Upgrade

Description:

InstallScript Custom Actions in Basic MSI setups are not triggered when the setup is upgrading a previous installation (major upgrade package).

Workarounds:

None.

Status:

InstallShield has listed this problem as open issue in the release notes for ISD 7.0.
FIXED in ISD 7.01.

Created: 2001-08-18   Last update: 2001-10-22  InstallShield tracking number: 1-5X5AX

Runtime Error 1706 when Applying a Patch Created from Standard Project

Description:

When applying a patch that was built based on a Standard project, you get runtime error 1706 "No valid source could be found for product [ProductName]."

Cause:

The OnPatchUIBefore and OnPatchUIAfter functions are missing from setup.rul.

Workarounds:

Go to the InstallScript view, select Setup.rul and move cursor to end of script. Select "Miscellaneous" from the left combo box on the tool bar, then select Patch UI Before and Patch UI After from the right combo box. This will insert the default code for the missing functions to your script.

Status:

This problem has been reported in the newsgroups for ISD 7.00.
FIXED in ISD 7.01

Created: 2001-09-29  Last update: 2001-10-22   InstallShield tracking number: 1-6T2M8

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

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