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 ]

[ IS 6.3 | IPSE 6.2 | IS 6.1 | IS 6.0 ]

InstallShield Professional 6.3

Last version: 6.31  with Patches 1 and 2. (Version 6.30 for the German Edition)
Released: September 12, 2001
Download: InstallShield Professional 6.31 can be downloaded at no cost from the InstallShield Download Center. This update is not for the German Edition of IS 6.
Release Notes: A list of fixed bugs and open issues can be found at http://www.installshield.com/downloads/isp/isprel.asp
Installation Notes for users of IS 6.30: IS 6.31 is an update to IS 6.30, do not uninstall 6.30. The maintenance pack will also update any installed language packs, so be sure your language packs are installed before you apply the update.
Installation Notes for users of IPSE 6.2x: IS 6.31 is an update to IS 6.30, i.e. you must have version 6.30 installed. The following procedure is suggested for the update:
1. Uninstall version 6.2x
2. Download and install version 6.30
3. Install any language packs (your 6.2x language packs will work with version 6.30)
4. Apply the 6.31 maintenance pack
Documentation Update: Users of IS 6.31 should also download the latest help files of January 15, 2002. The update can be obtained by selecting "Check for Updates" from the Online menu or by download from the InstallShield Download Center. This documentation update is not for the German Edition of IS 6.
Patches 1 and 2: The patches are available in knowledge base articles Q105927 (patch 1) and Q106585 (patch 2 which requires patch 1 as prerequisite).

Known Bugs in IS 6.31

Media Wizard doesn't Keep Product Name

Description:
Under Media Properties - General - Advanced - Product Name you can specify a product name. However if you close the dialog and later return to it, it doesn't remeber what you have entered and instead displays the default value.
Workarounds:
Don't re-open that dialog. The product name you specified will correctly be used in the build.
Status:
InstallShield confirmed that this is a known issue. Applies to IS 6.30 and 6.31.
FIXED in ISPro 7.0
Created: 2001-10-26    Last update: 2002-08-14     InstallShield Tracking Number: 1-6IVEH

Components Missing in Component Selection Dialog

Description:
To reproduce: Create a project with two components A and B. Build one media containing only A and another containing only B. Install A first, then install B (a maintenence install). Go to Add/Remove Programs  to uninstall B - you can't. The only component presented in the Select Components Dialog is A.
Workarounds:
Leave both components in both builds, and make the unwanted component invisible.
Status:
InstallShield stated that this is not a bug, and will be documented more clearly in a future release. Media information is not being merged, and the component dialog must be based on the media information. A futire version will uninstall the component that is in the log file but not the header, but components missing from the media information will not be shown in the component dialog in any case. When using maintenance mode, only the components that are contained in the latest installed media will be recognized by the installer and thus displayed in the component dialog, and subsequently added/removed etc. Applies to IS 6.30 and 6.31.
Created: 2001-10-26    Last update: 2001-11-27   InstallShield Tracking Number: n/a

FindAllFiles Returns Wrong Files

Description:
Sometimes FindAllFiles may return files that are not in the directory you specified. If you have a huge project with many files and after ComponentMoveData call FindAllFiles on an unrelated directory, FindAllFiles will nonetheless return the files that were copied from ComponentMoveData, as well as the ones it's supposed to return.
Workarounds:
Check every file returned by FindAllFiles with the % operator to make sure it is really what you want.
Status:
This problem has been reported for IS 6.2.
Created: 2001-10-26

VB Project Wizard Fails on Systems with French Locale Settings

Description:
The VB Project Wizard aborts with error message "An error prevented the VB project from rebuilding Check _isVBErr.txt". However this file includes the following message: "La generation de 'Projet1.exe' a reussi." which means "The generation of the project succeeded." This happens if the system locale is set to "French" or "French Canadian", even if you are using an English version of Windows.
Workarounds:
Temporarily change the System Locale (Control Panel, Regional Settings) to English (US).
Status:
This problem has been reported in the newsgroups for IS 6.03 and 6.10. InstallShield has confirmed that this is a problem in IS 6.31.
FIXED in ISPro 7.0
Created: 2000-02-21    Last update: 2002-08-14   InstallShield Tracking Number: 1-3W4AY

Date Stamp of Files in Setup Files Pane is Changed

Description:
If you insert a file in the Setup Files pane of the IDE, its "last modified" date stamp is set to the date and time you inserted the file.
Workarounds:
Use Windows Explorer to copy the file to the appropriate subfolder of the Setup Files in your project directory.
Status:
InstallShield confirmed that this is a problem in IS 6.22 and 6.31. It is also reproducible in IS 6.10.  This only happens on Windows 9x.
Created: 2000-03-22    Last update: 2001-09-13   InstallShield Tracking Number: 1-3VV9A

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 and 6.31.
FIXED in ISPro 7.01
Created: 2001-04-07   Last update: 2003-01-03   InstallShield Tracking Number: 1-53DNB

Media Read Object Doesn't Work on Windows 95 Retail

Description:
The Media Read Object may not work on a clean Windows 95 Retail. It does work on Windows 95b (OSR2).
Cause:
MediaRead.dll has a dependency on IMAGEHLP.DLL. That .DLL is not part of Windows 95 Retail, it is only in OSR2 or later and NT. It is also installed by VB5 and Office97.
Workarounds:
Install an IMAGEHLP.DLL before using the Media Reader. The DLL must be copied to the Windows System Directory, so cannot just be included in SUPPORTDIR.
Status:
InstallShield has confirmed that this is a bug in IS 6.22 and 6.31.
MeidaRead object is no longer required with ISPro 7.0.
Created: 2001-04-07   Last update: 2002-08-14   InstallShield Tracking Number: 1-5XUKO

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 IS 6.22 and 6.31. It was also reported for version 6.1x.
Created: 2000-12-08   Last update: 2001-09-13   InstallShield Tracking Number: 1-3PYX1

Setup Program Loses Focus After SdShowMsg or ShowProgramFolder

Description:
Running a setup, IS6.2 often loses focus and disappears into the background after you click Next on an Sd dialog box. After calling SdShowMsg or ShowProgramFolder, the IS dialog loses focus and doesn't properly regain it.
Workarounds:
Use SetTitle() to display a message on the background, rather than use SdShowMsg(). Or use the method described in article Enable Setup to Take Focus.
Status:
InstallShield confirmed that this is a bug in IS 6.2 and 6.31.
Created: 2000-06-27   Last update: 2001-09-13   InstallShield Tracking Number: 1-5V0RG

PlaceBitmap Does Nothing or Distorts Bitmap

Description:
Although you call PlaceBitmap your graphic does not appear on the screen, or is distorted or extremely enlarged.
Cause:
InstallShield fails to calculate the screen size on some machines. The exact configuration causing this problem is yet unknown.
Workarounds:
Before PlaceBitmap, call the following function: SizeWindow(METAFILE, DX, DY); where DX is the width of the bitmap and DY is the height of the bitmap.
Status:
InstallShield confirmed that this is a bug in IS 6.03. It is still there in 6.10.
FIXED in InstallShield Developer 7.0. A sample project is needed to reproduce this in IS6 - please contact the webmaster if you have a project that exposes this problem.
Created: 1999-12-15   Last update: 2001-09-13   InstallShield Tracking Number: 1-3W4BU

Transparent Control Setting Ignored in Custom Dialog

Description:
If you have set a control to Transparent using VC++, InstallShield will ignore the setting during runtime. Example: Open _ISUSER.DLL in VC++ and change the dialog ID of 12006 to 12106 (Welcome dialog). Include _ISUSER.DLL in the build. Call EzDefineDialog to define the dialog and call WaitOnDialog to display the dialog. The text box control is no longer transparent.
Workarounds:
None.
Status:
InstallShield has confirmed that this is a problem in IS 6.1x and 6.2x. A sample project is needed to reproduce the problem - please contact the webmaster if you have a project that exposes this problem.
Created: 2000-10-04    Last update: 2001-09-13   InstallShield Tracking Number: 1-3NVV0

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 has confirmed that this is a bug in IS 6.30 and 6.31. It is also reproducible in IPSE 6.22. The function works properly in IS 5.53.
Created: 2001-09-08   InstallShield Tracking Number: 1-6JJL1

Updates Don't Work With One-Click Installs

Description:
ComponentUpdate does not work properly from a One-Click Install setup because OCI technology only downloads files as required.
Workarounds:
Use a full product build to update previous releases of your application.
Status:
InstallShield has confirmed that this is a bug in IS 6.30 and 6.31.
Created: 2001-05-05   Last update: 2001-09-08   InstallShield Tracking Number: 1-XXRD

ComponentError Returns Empty Information

Description:
Calling ComponentError after a failed component function, sometimes the returned strings for component name and file group are empty, and the returned error number is 0. This happens for instance if you call ComponentValidate on a component that is not password protected, or call any component function on a non-existing component (e.g. spelling error in your script).
Workarounds:
None.
Status:
InstallShield has confirmed that this is a bug in IS 6.22. It has also been reported for IS 6.10.
FIXED in IS 6.31 for ComponentValidate.
Created: 2000-05-26   Last update: 2001-09-08   InstallShield Tracking Numbers: 1-3O4TY (general) & 14752 (ComponentValidate)

Other Known Issues in IS 6.31

Debugger Caused Wrong Behaviour of Script Functions

Description:
A script which uses a function with a variable number of arguments has the right effect if run normally, but gives wrong results when running in the debugger. Here is how to reproduce it: Create a blank project and add the following script:

prototype Test( STRING, ... );

function Test( szFormat, VA )
  STRING szLine;
begin
  switch( SizeOf( VA ) )
    case 0:
      Sprintf( szLine, szFormat );
    case 1:
      // Set breakpoint here
      Sprintf( szLine, szFormat, VA( 0 ) );
    case 2:
      Sprintf( szLine, szFormat, VA( 0 ), VA( 1 ) );
  endswitch;
  MessageBox( szLine, INFORMATION );
end;

function OnBegin()
  STRING szFirst;
  STRING szSecond;
begin
  szFirst = "First";
  szSecond = "Second";
  Test( "First format %s", szFirst );
  // Test( "Second format %s", szSecond );
  Test( "Third format %s and %s", szFirst, szSecond );
end;


When the script is run it produces a message "First format First" and then one "Third format First and Second". If instead you debug the script and set a breakpoint at the line marked, the second message is instead "Third format Information and Second".
Workarounds:
None.
Status:
InstallShield stated that this functionality (variable number of arguments) is undocumented and thus this is not considered a bug.
Created: 2000-06-27   Last update: 2001-09-19   InstallShield Tracking Number: 1-65EBB

Missing Bitmaps on SdOptionsButtons

Description:
Not all bitmaps display on the buttons in SdOptionsButtons. This happens if one of the bitmaps doesn't exist (e.g., "@0") because the designer wanted to leave a blank space on the dialog box. In this case the subsequent bitmaps will not be displayed even if they do exist.
Workarounds:
Either give up on the blank space or create a blank bitmap for the intervening button.
Status:
InstallShield stated that this is by design. Empty buttons are not supported. A feature request has been submitted.
Created: 2000-06-27   Last update: 2001-09-19   InstallShield Tracking Number: 1-5ZO88

Passwords Readable in Data1.hdr

Description:
On the components pane you can specify a password for the active component. In addition you can select that the component should be encrypted. But still the password you specified is stored on your distribution media in Data1.hdr in plain text so that it can be viewed with any text editor.
Even password protecting the whole media (on the Advanced Build Settings dialog in media build wizard) does not help: The media password is also stored as plain text in Data1.hdr.
Workarounds:
Use PackageForTheWeb to create a password protected single-file installer from your media. Be sure to use PFTW version 2.03 or above - previous versions didn't use encryption.
Status:
This problem is reproducible in IS 5 and IS 6. InstallShield stated that this is by design. A feature request has been submitted.
Created: 2000-02-07   Last update: 2001-09-19   InstallShield Tracking Number: 1-3YLQ5

Command Line Compiler Fails on Windows 95/98

Description:
The command line compiler works on Windows NT, but the results are unpredictable on Windows 95 and 98.
Cause:
This is the correct command line syntax for the command line compiler:
Compile <My Install Project>\Script Files\Setup.rul
        -I<Installshield Pro 6 Install Dir>\Script\IFX\Include
        -I<Installshield Pro 6 Install Dir>\Script\ISRT\Include
        <Installshield Pro 6 Install Dir>\Script\IFX\Lib\IFX.obl
        <Installshield Pro 6 Install Dir>\Script\ISRT\Lib\ISRT.obl

In most cases this command line will exceed the 127 character default command line length limit on Windows 9x and is truncated without warning.

Workarounds:
The suggested solution is to store all the command line parameters in a file and start the compiler with Compile @command_file.
Another option would be to increase the command line limit to 250 (Win95) or 255 (Win98) by modifying the config.sys (shell=c:\windows\command.com /u:250 /p). You must shorten the path names or increase the command line limit or both to make this work.
Status:
This is a operating system limitation.
Created: 1999-11-06    Last update: 2001-09-13   InstallShield Tracking Number: 1-3ZIDM

"Setup failed to run installation (0x80040707)"

Description:
During setup initialization, sometimes an error message 0x80040707 with no additional information is displayed. After that setup appears to continue, but is not fully initialized, resulting in various consequential problems.
There are other problems that can also cause an 0x80040707 error message, such as wrong DLL function prototypes or an illegal format specifier in Sprintf. The bug discussed in this article is unique in that it occurs during setup initialization, that is while the "Your Application Name Setup is preparing the InstallShield wizard ..." progress bar is displayed. At this time your install script is not yet running, so the error cannot be cause by an error in your script.
Cause:
It is still obscure which conditions cause this problem. There is a discussion group for people affected by this error (under Special Topics -> DosExecPgm Error). If you are affected by this error, please collect as much information as possible, such as Windows version, language and service pack, network settings, regional settings, virus scanners, Internet Explorer, and other installed software packages, and post it to the group. Hopefully some scheme can be identified that helps to find the cause and fix the problem.
Workarounds:
None.
Status:
This is the IS 6.2 variant of the DosExecPgm problem that happened on IS 6.1. It still exists in IPSE 6.22.
InstallShield stated that this is an operating system issue. Additional information is available in the discussion group.
Created: 2000-06-15    Last update: 2001-09-13   InstallShield Tracking Number: 1-3ZIDA

Files in Setup Files Pane Don't Get Replaced Using Drag & Drop

Description:
If you drag a file from Windows Explorer and drop it in the Setup Files pane (e.g. Splash Screen, Language Independent\Operating System Independent) an existing file will with the same not be overwritten. Instead the new file is renamed by prepending "Copy of " to the original file name.
Workarounds:
Right click in the Setup Files pane, select "Insert Files" and use the file selection box to add the new file. The old file will be overwritten without confirmation.
Status:
InstallShield stated that this is by design. A feature request has been submitted.
Created: 2000-02-07    Last update: 2001-09-13   InstallShield Tracking Number:18798

Boolean Variables Sometimes Use -1 for TRUE

Description:
Boolean properties and Boolean system variables such as BATCH INSTALL get set to –1 instead of 1 to indicate TRUE. This causes the property to appear to be FALSE if a statement such as if (Property = TRUE) is used.
Workarounds:
Use if ( Property ) instead.
Status:
InstallShield stated that this is by design.
Created: 2001-05-05   Last update: 2001-09-13   InstallShield Tracking Number: 17377 & 17365

Multi-CD Setups Unexpectedly Prompt for Disk 1

Description:
Multiple CD installations sometime prompt for Disk 1 at various times during the install.
Workarounds:
Instruct end-users to place the correct CD in the drive when this message occurs, and the setup will complete normally.
Status:
InstallShield stated that this is a limitation of the operating system and only occurs for some CD ROM drives and operating system versions.
Created: 2001-05-05    Last update: 2001-09-08   InstallShield Tracking Number: unknown

Code Signing Fails On Windows Me

Description:
If you are running IS 6 on Windows Me you are unable to sign your setup with iSign.exe (from InstallShield) or signcode.exe (from Microsoft).
Cause:
Signing under Windows Me will only work if the spc and pvk files are created under Win ME.
Workarounds:
Use another operating system version to sign your packages., e.g. Windows 2000, NT4 or 98.
Status:
This problems has been confirmed by Microsoft.
Created: 2001-03-29   InstallShield Tracking Number: n/a

Functions Removed in IS 6

Description:
The following are not really "bugs", i.e. things that have been broken accidentally, but "design desicions": Functionality that has been deliberately removed on the transition from IS5 to IS6. You should consider these limitations before you decide to convert a project from IS5 to IS6. You can find additional information on most of these topics in the Mirgration Whitepaper.
Status:
Version 6.03 has a new event called OnInstallingFile( ) which will return the fully qualified target path and filename of the file being transferred to the system.
A MediaReadObject is available from InstallShield that brings back the ComponentFileEnum and ComponentFileInfo functions.
On the IS6 CD you can also find IS5.5, which includes dialog script source code. Using this code with IS6 is sometimes possible after a few modifications.
In IS Pro 7.0 the COmponentFileEnum and ComponentFileInfo functions and the Sd dialog source codes are available again.
Created: 1999-11-03   Last update: 2002-08-14   InstallShield Tracking Number: n/a

Component may be Deleted During Update

Description:
You create an update following the sample in knowledge base article Q104431 and add a new sub component to a component. When you install the update the parent component is uninstalled. This happens if the parent component didn't have a child component before.
Cause:
A parent component is automatically de-selected if all of its child components are deselected. In this case, the newly added component is the only child component, and is initially unselected. This causes the parent to become unselected, although it was selected during the initial install.
Workarounds:
Make the new component an invisible top level component, and specify it in the required components field of the existing component.
As a precaution in the initial install you can add a dummy child component, so you can later add more children without affecting the selection state of the parent.
Status:
This behaviour is by design.
Created: 2001-02-22   InstallShield Tracking Number: n/a

SdAskDestPath / SelectDir Create Directories Without Asking

Description:
When the Browse button in SdAskDestPath is pressed, the SelectDir function is called. If you specify a folder that does not yet exist, a message box should appear asking whether or not to create the folder. However SelectDir does not display this message box, but creates the new folder without asking.
Workarounds:
Add the following script to your script file pane, and include it at the bottom of your setup.rul. It will ask whether the new directory should be created, and only create it when the NEXT button is pressed. This new version supports silent mode. It is based on the IS5 version and thus does not set the szTitle in the white banner correctly, and does not support multi-line strings (that include "\n") in szTitle.
ZIP AskDestPathFix.zip   Written by Asaf Vishna
File size: 1.603 bytes   Last update: 2000-02-17
Status:
InstallShield stated that this is by design.
Created: 2000-02-03    Last update: 2001-01-13   InstallShield Tracking Number: 1-3ZIDI

Cancel Button on Status Dialog Only Works During File Transfer

Description:
The status dialogs can be used for other purposes than file transfer: Call Enable(STATUSEX) or Enable(STATUSDLG) etc. to display the dialog, and use SetStatusWindow to move the progress bar. However clicking the Cancel button on this dialog does not result in any action - it is simply ignored.
Workarounds:
None.
Status:
InstallShield stated that this is by design. A feature request has been submitted.
Created: 2000-04-28    Last update: 2001-01-16   InstallShield Tracking Number: 1-3O4UO

XCopyFile Doesn't Copy Empty Subdirectories

Description:
Calling XCopy file with INCLUDE_SUBDIR will not copy subdirectories that do not contain any files..
Workarounds:
Call CreateDir to create empty subdirectories, or add dummy files to make sure the directory isn't empty.
Status:
InstallShield stated that this is the intended behaviour. Copying empty subdirectories will be considered as a feature request for a future version.
Created: 2000-05-19    Last update: 2001-01-13   InstallShield Tracking Number: 1-3O4U4

16-Color Splash Screen Not Displayed

Description:
In addition to setup.bmp you can add a 16 color version of your splash screen to the setup files pane. It must be named setup16.bmp and should be displayed instead of setup.bmp on systems that cannot display 256 colors. This doesn't work, IS6 always displays setup.bmp.
Workarounds:
Use only 16 colors in setup.bmp.
Status:
In knowledge base article Q104972 InstallShield states that this functionality has deliberately been removed in InstallShield Professional 6.x. The help file in IPSE 6.22 has been corrected and no longer mentions setup16.bmp.
Created: 2000-02-03    Last update: 2000-11-27   InstallShield Tracking Number: n/a

"Media too small" Error for Floppy Media if Objects Are Used

Description:
When you build your floppy disk based media you get "Error 129: Media too small. Could not fit 'data1.cab' on disk 1." This happens if your projects includes certain objects.
Cause:
The setup engine needs all support files from both your main installation and all objects to be fit into disk1. For a floppy build, it won't fit some times if you use big object like ODBC or MDAC.
Workarounds:
Include the ODBC or MDAC (or whatever applies) installer as separate disk set, and call it from your setup script. Or select a larger media type (like CD-ROM) and split it on diskettes using third party software like WinZip Self Extractor.
Status:
InstallShield confirmed that this is a known limitation (not a bug) in IS 6.x that will not be fixed. Similar problems have been around in IS5.
Created: 1999-12-15    Last update: 2001-01-04   InstallShield Tracking Number:1-3NVW0

"Error loading type library/DLL"

Description:
During setup initialization you may get the following error message: "Setup failed to launch installation engine: Error loading type library/DLL".
Cause:
The most likely cause of this error is deleting stdole32.tlb from the machine, e.g. by uninstallation of some other application. Stdole32.tlb is part of all 32 bit Windows versions, and should never be removed.
Workarounds:
Make sure that stdole32.tlb is installed, and do not uninstall this file.
Status:
This problem is caused by a corrupted Windows installation (missing core file).
Created: 2000-06-29   InstallShield Tracking Number: n/a

One-Click Install not Working with Oracle Web Server

Description:
A One-Click Install hosted on a Oracle OAS 4.0.8.1 web server fails to download files. This is caused by an incompatibility in the way Oracle handles HTTP 1.1 requests.
Workarounds:
Update to OAS 4.0.8.2 or use a different web server (like IIS or Apache).
Status:
InstallShield has stated that the Oracle web server sends invalid responses to HTTP 1.1 requests. It was reported in a newsgroup that the problem does not occur with OAS 4.0.8.2. It works for other versions of the Oracle Web Server.
Created: 2000-06-11    Last update: 2001-09-19   InstallShield Tracking Number: n/a

No Uninstall Entry in Add/Remove Programs Control Panel

Description:
Your program may not be listed in the Add/Remove Programs control panel applet on some or all machines. There are two different problems that can cause this symptom:
a) You migrated your IS5 project to IS6 and still use a procedural script (using program and endprogram keywords).
b) The entry exists in registry, but is not displayed. After you shorten the GUID with regedit, the entry appears.
Workarounds:
a) You have to modify your script. Read knowledge base article Q104766 if you want to use procedural script, or convert your project to event based.
b) This problem affects other setup programs as well (including Windows Installer). This can be caused by an uninstall registry key name that is longer than 60 characters, or the uninstall display name is longer than 32 characters - see Microsoft Knowledge Base article Q247515 for more details. Another possible cause is some sort of registry corruption. Some people have successfully fixed this with Microsoft's TweakUI tool (read Windows Magazine article for more information about TweakUI).
Status:
a) FIXED in 6.11 and 6.20
b) This problem has been reported on several newsgroups. It is an operating system issue.
Created: 2000-04-01    Last update: 2000-06-20   InstallShield Tracking Number: n/a

Sprintf with "%n" Format Specifier Crashes Setup

Description:
If szFormat includes the format specifier" %n", calling Sprintf or SprintfBox results in an unhandled exception "Error 0x80040707: Dll function call crashed ISRT._DoSprintf. Setup will now terminate".
Workarounds:
InstallShield documentation does not list "%n" as valid format specifier. Correct your script code by using "%i" instead.
Status:
This runtime error is caused by erroneous script code. It is not a bug in InstallShield.
Created: 2000-05-31   InstallShield Tracking Number: n/a

Error 0x80010706 "Object Reference not Set" with Word Object

Description:
If you call CreateObject("Word.Application"); and then try to access the Microsoft Word object, you may get error 0x80010706 "Object Reference not Set" on system running Norton AntiVirus 2000 (NAV).
Cause:
To intercept macro viruses, NAV installs a Word plug-in. Because of a bug this plug-in sometimes doesn't allow other applications to connect to Word's automation interface.
Workarounds:
Deactivate the NAV plug-in during setup, as described in Symantec's knowledge base.
Status:
Symantec confirmed that this is a problem in Norton AntiVirus (document ID 1999111512035206).
Created: 2000-04-01   InstallShield Tracking Number: n/a

Setup Engine Files Removed on Windows 95

Description:
Setups created with InstallShield 6 install and use a set of shared installer engine files. These files are required for maintenance mode and uninstall and are shared across all setups. Therefore a reference count for each file is maintained in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\SharedDLLs.
Since the registry size in Windows 95 is limited, it might be full, and the reference count entries cannot be created. As a consequence, any IS6 setup that you uninstall also removes the engine files, leaving the other setups uninstallable.
This problem also affects files in file groups marked as SHARED.
Workarounds:
Run the setup.exe from the original media to uninstall. Clean the registry by removing entries that are no longer needed.
Status:
Microsoft confirmed that is a limitation in Windows 95. For more information see MSDN knowledge base article Q201546
Created: 2000-02-08   InstallShield Tracking Number: n/a

Bitmap on Welcome and Finish Dialogs Cannot be Replaced

Description:
DialogSetInfo( DLG_ALT_IMAGE, ...) replaces only the icon that is emedded in the larger blue bitmap on the left hand side of SdWelcome and the finish dialogs. This only applies to the Windows 2000 style dialogs.
Workarounds:
You can modify the dialog with a resource editor to replace that bitmap. The third-party tool InstallDialogue has a function IdSetWelcomeFinishBitmap that you can use to replace these bitmaps from script.
Status:
This limitation is by design.
Created: 2000-01-24   InstallShield Tracking Number: n/a

Known Problems in IS 6.30

Version: 6.30 (superseded by version 6.31)
Released: May 1, 2001
Download: Users of IPSE 6.2x can download IS 6.30 (English or German Edition) at no cost from the InstallShield Download Center. The East and West language packs from version 6.2x also work for version 6.30, there's no need to update the language packs.
Release Notes: A list of fixed bugs and open issues can be found at http://support.installshield.com/download/is63relnotes.asp

These problems have been fixed in the latest maintenance release and are listed for reference.

Problems Specifying Setup Language on the Command Line

Description:
You can select the setup language using the -l command line parameter. The help files states that "00nn and 04nn are treated as being equivalent when this switch is processed." This is not true.
Workarounds:
Specify the exact language code.
Status:
InstallShield has confirmed that this a documentation error in 6.30 and 6.31. It also exists in IS 6.22.
FIXED in documentation update of October 23, 2001.
Created: 2001-09-08   InstallShield Tracking Number: 1-6JWTR

System Variable SYSINFO.WIN9X.bSubversion_A is Not Set Correctly

Description:
Running a setup on Windows 95a does not set the system variable SYSINFO.WIN9X.bSubversion_A to TRUE.
However SYSINFO.WIN9X.bSubversion_B etc. are set correctly on the respective operating systems.
Workarounds:
You can read the service pack level of Windows 95 from the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion : SubVersionNumber.
Status:
InstallShield confirmed that this is a problem in IS 6.10 - 6.31.
FIXED in documentation update of October 23, 2001.
Created: 2000-03-08    Last update: 2001-11-06   InstallShield Tracking Number: 1-3W4AU

Displaying the Version Info of a Self Extracting Setup Sometimes Causes GPF

Description:
Right clicking on a self extracting setup produced by IPSE to display its version information may cause a general protection fault on Windows 9x. This happens if you specified a long company name when you created the package.
Workarounds:
Use a shorter company name.
Status:
InstallShield has confirmed that this is a bug in IS 6.30.
FIXED in IS 6.31.
Created: 2001-05-05   InstallShield Tracking Numbesr: 1-4X07J & 1-5LD4P

Automatic Proxy Settings Not Supported for OCI

Description:
One-Click Installs can't use automatic proxy settings.
Workarounds:
None.
Status:
InstallShield has confirmed that this is a bug in IS 6.30.
FIXED in IS 6.31.
Created: 2001-05-05   Last update: 2001-09-08   InstallShield Tracking Number: 1-4Q6SF

Russian Language String Table not Working

Description:
When you open a project that includes support for Russian language you may get the message "String table could not be loaded. The project may be corrupt." This happens for new projects created in IS 6.30 as well as older projects that are upgraded to 6.30.
Workarounds:
Use IPSE version 6.12 or 6.22.
Status:
InstallShield has confirmed that this is a bug that has been introduced in IS 6.30. It does not affect versions 6.1x or 6.2x.
FIXED in IS 6.31.
Created: 2001-08-08   Last update: 2001-09-08   InstallShield Tracking Number: 1-63JY5

Setup Launched with DoInstall Uses Wrong Language

Description:
If you launch a setup with DoInstall it runs in a random language, but it should use the same language as the parent setup (SELECTED_LANGUAGE).
Workarounds:
Launch the child setup via LaunchAppAndWait (which is possible in IS 6.30 - unless the child setup uses a newer setup engine than the parent setup) and specify the setup language on the command line.
Status:
InstallShield has confirmed that this is a bug in IS 6.30.
FIXED in IS 6.31.
Created: 2001-05-05    Last update: 2001-09-08   InstallShield Tracking Number: 1-4I9L2

Object Dialogs are Displayed in Wrong Language

Description:
Dialogs embedded in InstallShield Objects are always displayed in the default language, regardless of the language the main setup is runing in.
Workarounds:
None.
Status:
InstallShield has confirmed that this is a bug in IS 6.30.
FIXED in IS 6.31.
Created: 2001-05-05    Last update: 2001-09-08   InstallShield Tracking Number: 1-1DESC

EnterDisk Dialog Sometimes Shows Wrong Disk Number

Description:
EnterDisk dialog box does not display the correct disk number in some cases, this can occur for a variety of different multi-disk setups.
Workarounds:
None.
Status:
InstallShield has confirmed that this is a bug in IS 6.30.
FIXED in IS 6.31.
Created: 2001-05-05    Last update: 2001-09-08   InstallShield Tracking Numbers: 1-4163T & 1-4Y23X

Can't Specify Subcomponents in Media Read Object

Description:
The MediaReadObject provides replacements for the functions ComponentFileEnum and ComponentFileInfo functions that are no longer available in IS6. However you cannot specify subcomponents in the replacement ComponentFileXxxx() functions.
Workarounds:
Create a dummy component with the necessary file groups and make sure that the dummy component is never installed.
Status:
InstallShield has confirmed that this is a bug in IS 6.22.
FIXED in version 1.30 of the Media Read Object which can be downloaded here.
Created: 2001-03-29   InstallShield Tracking Number: 1-4VBSQ/1-5GROT
 

 

 

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