Shop

AdminStudio
InstallShield
Advanced Installer
other products

InstallShield

Updateberechtigung von InstallShield 2013 endet am 3. Juni. Bestellen Sie jetzt noch die aktuelle Version zum Update-Preis.
InstallShield 2015
jetzt mit Unterstützung für Windows 10, Visual Studio 2015 u.a.

InstallShield und AdminStudio Schulungen

Offizielle Kurse mit Zertifikat

weitere Infos


 

Known Problems in InstallShield Products

[ MSI Engine | MSMs | Previous InstallShield versions ]

InstallShield 11.5 Problems: General | Basic MSI | InstallScript

FLEXnet InstallShield Windows 11.5 Premier and Professional

Related Knowledge Base articles:

Hotfixes for the English edition:

Hotfixes for localized editions:

Problems that are fixed in InstallShield 12 (released June 6, 2006) but not in version 11.5 are marked  FIXED IN IS12 . Please note that this is based on my understanding of the IS 12 release notes and other documents, but is not a guarantee. If you want to be really sure that the problem is fixed you should download a free evaluation copy and try yourself.

General

 NEW  Application Pool Password Truncated

Description:
When using Installshield 11.5 to install a website in IIS 6 via a Basic MSI project, and the installation also creates several app pools configured to run under specific identities,  Installshield appears to truncate the last character of the password when the password is exactly 8 characters long and ends in the number 7. If the password has more or less than 8 characters or ends something other than the number 7 it works fine. For example the password "abcdefg7" gets truncated.
Status:
This problem has been reported in the InstallShield Community Forum.
Macrovision has reproduced the problem and confirmed that it affects InstallScript and Basic MSI projects.
Created: 2006-06-20      Macrovision tracking number: IOC-000050915

Error 1931 ... xpsp2res.dll when installing InstallShield 11.5

Description:
When installing InstallShield 11.5 (English version) on a non-English version of Windows XP SP2 you get the following error message:
Error 1931 : The windows Installer Service cannot update the system file C:\Windows\...\xpsp2res.dll because the file is protected by Windows. You may need to update your operating system for this program to work correctly
Cause:
The file xpsp2res.dll contains localized resources (strings and the like) for Windows XP SP 2. The version of this file in the IS 11.5 setup is 5.1.2600.2180 which is the same version as the file in XP SP2. However the language in the steup is 1033 (English) while the language of the existing file depends on the language version of Windows. Therefore Windows Installer tries to replace the existing file, according to its file versioning rules, but Windows File Protection prevents this.
Workaround:
This is a non-fatal error message. You can ignore it and continue the instalaltion.
Status:
This problem has been reported in the InstallShield Community Forum and can be reproduced with the CD version of InstallShield 11.5. Whether it has been fixed in the download version is unknown.
Created: 2006-05-16  

InstallShield IDE hangs on Splash screen

Description:
When you try to start InstallShield the program may hang on the splash screen. In task manager you see the isdev.exe using CPU load (reports range from 50%-99% CPU usage).
Workaround:
Uninstalling security updates MS05-052 and/or MS05-054 for Internet Explorer seems to fix the problem. Note that uninstalling those security updates may make your computer vulnerable to attacks, so you should make sure you understand the consequences and take appropriate measures to mitigate the risk.
Status:
These problems have been reported in multiple threads in the InstallShield Community Forum.
Created: 2006-03-14  

 FIXED IN IS12  Several Problems with Visual Studio 2005 Integration (Part 2)

Description:
Several issues occur when InstallShield is run from within Visual Studio 2005:
Cause:
Visual Studio 2005 introduced new security settings that were not used with earlier versions of Visual Studio.
Workaround:
As a general workaround for the Visual Studio 2005 integration issues you can use InstallShield to create your installation and then open the project from within Visual Studio.
To open an InstallShield project from within Visual Studio:
1. On the File menu, point to Open, and click Project. The Open Project dialog box opens.
2. Browse to the InstallShield file you want to open, and select it.
3. Click Open.
Status:
These problems are documented in  knowledge base article Q111934 but are not fixed by Update 4.
Created: 2006-03-09   Macrovision tracking numbers: see article

 FIXED  Several Problems with Visual Studio 2005 Integration (Part 1)

Description:
Several issues occur when InstallShield is run from within Visual Studio 2005:
Cause:
Visual Studio 2005 introduced new security settings that were not used with earlier versions of Visual Studio.
Status:
These problems are documented in  knowledge base article Q111934 which also includes the fix (Update 4.
Created: 2006-03-09   Macrovision tracking numbers: see article

 FIXED  Collaboration must be activated after InstallShield

Description:
If you try to activate InstallShield Collaboration before activating InstallShield 11.5, the activation fails. Note that this issue does not apply to the standalone version of InstallShield Collaboration; it applies only to the version that is included with InstallShield 11.5.
Cause:
A file was missing from the InstallShield Collaboration part of the installation.
Status:
This problem is documented in  knowledge base article Q111934 which also includes the fix (Update 4).
Created: 2006-03-09  

 FIXED  Update 4 cannot be installed

Description:
If you previously installed Update 2 you may not be able to install Update 4. You get an error message that the update is already installed.
Cause:
Apparently Update 4 reused the GUID from Update 2.
Status:
The download for Update 4 has been updated a few hours after this was discovered. You can download the corrected update package from knowledge base article Q111934.
Created: 2006-03-09  

Activation without evaluation period not possible

Description:
The Unable to install an evaluation license (error 100000) occurs when setting the Type of Trial Limit to Days and the Trial Limit Quantity to 0.
Workaround:
Set the Trial Limit Quantity to 1 and remove the evaluation option located on the 1015 dialog contained within the ActivationGui.dll.
Status:
Macrovision has reproduced the problem and determined it to be an issue in their software.
Created: 2006-02-24   Reported by Rene van der Veer   Macrovision tracking number: IOC-000045061

 FIXED IN IS12  Activation does not work through an authenticating proxy server

Description:
Online activation by internet doesn't work for trialware wrapped products (including InstallShield itself) in scenarios where a user is accessing the Internet through an authenticating proxy server.
Cause:
This error occurs because the INetTrans.exe file that was shipped with InstallShield 11.x does not permit activations by Internet through an authenticating proxy server. INetTrans.exe handles the online activation transactions.
Workaround:
Download a fixed INetTrans.exe from knowledge base article Q112019. If you have already distributed trialware that you created with InstallShield to your end users before you installed the above fix, you can provide the updated INetTrans.exe file to any end user who is having trouble performing online activations through an authenticating proxy server. The updated INetTrans.exe file should replace the one that was installed with your trialware on the end user's machine.
Status:
This problem is documented in knowledge base article Q112019 which also includes the fix.
Created: 2006-02-24  

Activation does not work for restricted users under Terminal Services

Description:
When installing a trialware-wrapped application, in a Terminal Server Session under Windows Server 2003, a restricted user cannot activate. You'll get the following error message:
The instruction at "0x77e4a1c4" referenced memory at "0x00000000". The memory could not be "written".
Workaround:
Log on as an Administrator on the local server.
Status:
Macrovision has reproduced the problem and determined it to be an issue in their software.
Created: 2006-02-24   Reported by Rene van der Veer   Macrovision tracking number: IOC-000046358

 FIXED  Customer Experience Improvement Program is always turned on

Description:
Macrovision's optional "Customer Experience Improvement Program" is turned on by default and cannot be turned off in the Options dialog box, which is available from the Tools menu.
Cause:
Normally this feature is turned off, and the user is prompted to join the program 15 days after first using the product. However, due to an oversight during the beta program, this was left on.
Workaround:
If you want to turn the Customer Experience Improvement Program off, you can download a tool from knowledge base article Q111903.
Status:
Fixed in InstallShield 11.5 Update 1.
History:
2005-12-16: This problem is documented in knowledge base article Q111903.
2005-12-29: Fixed in InstallShield 11.5 Update 1.
Created: 2005-12-15   Last update: 2005-12-29   Macrovision tracking number: IOC-000043666

 FIXED IN IS12  Internal Error if InstallShield is installed without the Collaboration feature

Description:
If a custom installation of InstallShield is performed with the InstallShield Collaboration feature deselected, an internal error occurs. This issue occurs with the CD-ROM build of InstallShield.
Workaround:
This has been fixed in the downloadable version of InstallShield. If you are installing InstallShield from the CD-ROM, the InstallShield Collaboration feature should be selected to avoid this error.
Status:
This problem is documented in knowledge base article Q111745.
Created: 2005-12-15

Basic MSI Projects

 3RD PARTY BUG  Merge Module Files install to folder named "Module Retargetable Folder"

Description:
When installing a package that was built including a merge module authored in Visual Studio 2005, the files from the merge module will install to a subdirectory called "Module Retargetable Folder".
Cause:
This problem is caused by a bug in Visual Studio 2005 which creates incorrect Diretory table entries in the merge module.
Workaround:
Knowledge Base article Q112116 explains how the merge module needs to be modified.
Status:
This problem is documented in Knowledge Base article Q112116. This is not a bug in InstallShield but in Visual Studio.
Created: 2006-05-16      Macrovision tracking number: IOC-000046172

SetupCompleteSuccess Dialog hangs in Setup with InstallScript Custom Actions, caused by JDSoftware Virtual Desktops utility

Description:
The utility Virtual Desktops made by JDSoft can cause Basic MSI projects using InstallScript custom actions to hang when the SetupCompleteSuccess finish button is clicked. A custom action named ISCleanupSuccess is launched from this control and hangs when the Virtual Desktops utility is running, causing the installation to appear to be hung. The idriver.exe process must be killed for the setup to exit.
Workaround:
It is recommended that the Virtual Desktops utility be shutdown and disabled before running a Basic MSI project that contains InstallScript custom actions.
Status:
This problem is documented in Knowledge Base article Q111568. Macrovision has not accepted this as a bug.
Created: 2006-05-16     

 FIXED IN IS12  Registry Key's Default Value Data Missing when Merging .REG File

Description:
A registry key's default value data is not captured when merging a REG file during build or importing to the Registry view. This format neither builds nor installs correctly when included as a Component's REG File To Merge At Build. Also, it will not import correctly to the Registry view.
Workaround:
Knowledge Base article Q111533 explains how to modify the .reg file to work around this problem.
Status:
This problem is documented in Knowledge Base article Q111533. It will be fixed in InstallShield 12.
Created: 2006-05-16      Macrovision tracking number: 1-1CI4YR

Error 1001.InstallUtilLib.dll: Unknown error when using the Stand Alone Build Tool

Description:
If you build a project that contains an Installer Class custom action using the stand alone build tool (IsSABld.exe) you may receive an error message like this at run time:
Error 1001.InstallUtilLib.dll: Unknown error
The same setup works correctly when built from the IDE.
Status:
This problem has been reported in the InstallShield Community Forum. A hotfix for the standalone build tool is available in the InstallShield Community Forum.
History:
2006-05-10: This problem has been reported in the InstallShield Community Forum.
2006-05-16: A hotfix for the standalone build tool is available in the InstallShield Community Forum.
Created: 2006-05-10      Last update: 2006-05-16  

Error 1001.InstallUtilLib.dll when using a Merge Module that contains an Installer Class

Description:
If you include a merge module that was ceated with Microsoft Visual Studio .NET 2003 or 2005 and contains an assembly that has an Installer Class you may receive an error message like this at run time:
Error 1001.InstallUtilLib.dll: Unknown error in CorBindToRuntimeHost (0x80131700)
Cause:
This error occurs because some additional steps must be taken to configure the project to support this type of Merge Module.
Workaround:
The required modifications are documented in Knowledge Base article Q108690.
Status:
This problem is documented in Knowledge Base article Q108690.
Created: 2006-05-10  

 FIXED IN IS12  Problems with the InstallShield IDE on Windows Vista

Description:
InstallShield 11.5 development environment encounters the following issues when installed on the Windows Vista Beta 1 operating system:
Status:
These problems are documented in Knowledge Base article Q112050. Since Windows Vista is still a beta product and is not officially supported by InstallShield 11.5 this doesn't really qualify as a bug.
Created: 2006-05-10  

 FIXED IN IS12  IIS Site Settings don't accept Properties

Description:
In Internet Information Services, create a new website, select it and then display the Web Site property page by clicking the Tab on the right hand side. Try typing [IISSITEID] into the Site Number box. You can't! You can only type in numbers. The same goes for TCP Port.
Workaround:
1. In Internet Information Services, create your website
2. In Property Manager, create a property called, say IISSITEID.
3. In Direct Editor, find the ISWebSite table.
4. Change the value of the SiteNumber column to [IISSITEID].
5. Go back to Internet Information Services and you will see [IISSITEID] in the Site Number box.
6. Set the [IISSITEID] property from wherever you want, and it will be resolved correctly at runtime.
The same will work for TCP Port.
Status:
This problem has been reported in the InstallShield Community Forum.
Created: 2006-04-25  

 FIXED IN IS12  Major Upgrade Settings Get Changed

Description:
If you add a Major Upgrade item, select "Within a specific range of versions", and put the checkmark next to the "Version range inclusive" option, your settings change to "With a specific version" with the version number you entered as minimum version when you move to a different view of the IDE or when you close the project.
Workaround:
The problem doesn't occur if you do not select the "Version range inclusive" option. So as a workaround unselect this option, and enter a minimum version that is 1 less and a maximum version that is 1 more than what you specified previously. Sample: instead of 4.0.0000-4.1.0000 enter 3.255.655535-4.1.0001 (255 is the maximum value that Windows Installer allows for the second field of the ProductVersion, and 655535 is the maximum value for the third field).
Status:
Macrovision has accepted this as a bug.
History:
2006-04-04: This problem has been reported to Macrovision support (support incident number: SIOA-000047715)
2006-04-24: Macrovision has accepted this as a bug (work order: IOA-000025014)
Created: 2006-04-04   Last update: 2006-04-25   Macrovision tracking number: IOA-000025014

COM Extraction doesn't work with a 64-bit DLL

Description:
COM extraction will not work with a 64-bit DLL.
Cause:
COM extraction within InstallShield is a 32-bit process.
Workaround:
Manually populate the registry table (and other tables) with the registration information for this DLL.
- or -
Use the self-register option by right-clicking the DLL and selecting the Self-Register checkbox. Before doing this to go to Tools - Options and select to use the Windows SelfReg table instead of the InstallShield one.
Status:
Macrovision support has confirmed that this is a limitation in the current versions of InstallShield. They have not accepted this as a bug but have created a feature request. It is not likely to be fixed for existing versions of InstallShield, not even for InstallShield 12 which is currently in beta test. However, they are considering it for future releases.
Created: 2006-03-31   Last update: 2006-04-25   Reported by Asaf Vishna   Macrovision tracking number: IOB-000005298

XML Element content disappears from XMLFiles view

Description:
On the Advanced tab of the XML Files view when checking the 'Set Element Content' box and setting a value, the value is gone the next time the project is opened. The check box is checked but the Content field is empty. However the value can still be seen in the Direct Editor.
Workaround:
If you want to be confident it holds the right value the easiest way is to visit the direct editor, and look in the ISXml* tables.
Status:
This problem has been reported in the InstallShield Community Forum. It is a known bug according to Michael Urman, Software Engineer in Macrovision's InstallShield Windows Team.
Created: 2006-03-29  

 FIXED IN IS12  Error 1603 ISMsiServerStartup on x64 Systems

Description:
When installing a package from the MSI file directly, without the use of Setup.exe, in a Basic MSI project containing InstallScript custom actions and the InstallScript merge module, the setup may fail with the unspecific error 1603. In the log file the following errors may be seen:
Action ended : ISMsiServerStartup. Return value 1603
1: GetInstallDriver, Can not find InstallDriver in ROT table
Cause:
The issue stems from the InstallScript merge module. The file ISbew64.exe is not installed correctly to a machine running Windows 2003 on x64 into C:\Program Files\Common Files\InstallShield\Driver\1150\Intel.
However when installing from the Setup.exe, the correct set of InstallScript engine files are installed and no error messages are seen.
Workaround:
In some cases these work-arounds have been found to resolved the behavior:
Status:
This problem is documented in Knowledge Base article Q111093.
Created: 2006-03-29   Macrovision tracking number: IOC-000044584

 FIXED IN IS12  Error with MDAC Merge Module on Windows Vista

Description:
Running a setup that includes the MDAC 2.6 or 2.7 merge module on Windows Vista displays an error message "The minimum supported configuration for installing MDAC 2.7 requires one of the following ..." with a list of operating system versions.
Cause:
Windows XP and above include MDAC out of the box so you cannot install the redistributable there. The merge module has a check for Windows XP and 2003 and doesn't even try to install MDAC on these operating system. However it doesn't check for Windows Vista.
Workaround:
The check is done in a VBScript custom action (stored in the Binary table) with this code:
ElseIf ((vVerNT = "501") Or (vVerNT = "502")) Then
' If it is XP do not install
Else

You can edit the merge module to change the code like this:
ElseIf (vVerNT >= "501") Then
' If it is XP or higher do not install
Else
Status:
This problem has been reported in the InstallShield Community Forum. It was anticipated since 2003 when a similar problem was fixed for Windows 2003. Since Vista is not officially supported in InstallShield 11.5 this is strictly speaking not a bug but a feature request. Macrovision said it will be fixed in InstallShield 12.
Created: 2006-03-28   Last update: 2006-04-25   Macrovision tracking number: IOC-000047479

 FIXED IN IS12  Error 1603 "Error installing Windows Installer engine" on Windows Server 2003 SP1

Description:
Running a setup built with IS11.5 using Windows Installer 3.1 on Windows Server 2003 with Service Pack 1 shows the following error message:
1603: Error installing Windows Installer engine. A file which needs to be replaced may be held in use. Close all applications and try again.
When clicking OK on that message box the installation continues properly. On Windows Server 2003 without SP1 the error message isn't displayed.
Cause:
SP1 includes MSI 3.1 and conflicts with the standard MSI 3.1 redistributables.
Workaround:
Don't install the MSI 3.1 runtime files with your setup (install MSI 2.0 or none at all), or build a custom prerequisite to install MSI 3.1 instead of using the option in Release wizard.
Status:
This problem has been reported in the InstallShield Community Forum. Macrovision is aware of the problem and working on a fix in InstallShield 12.0. It's unclear whether a fix will also be released for version 11.5.
Created: 2006-03-28  

Empty Folders Not Created Using Dynamic File Linking

Description:
When a folder that is dynamically linked contains at least one empty subfolder and if files are selectively excluded in the dynamic link, the empty subfolder will not be installed on the target machine. It will appear within the InstallShield IDE, but will not appear in the CreateFolder table.
Workaround:
The best available workaround is to manually create this empty folder by populating the CreateFolder table in the Direct Editor. Another option is to avoid excluding files in the dynamic link.
Status:
This problem is documented in Knowledge Base article Q112059.
Created: 2006-03-22   Macrovision tracking number: IOC-000046703

Access Object Does Not Install During Compressed Install

Description:
If you include the Access 2000/2002/2003 InstallShield Object in your project and create a compressed installation, the Access redistributable is not launched during installation.
Workaround:
Use an uncompressed release.
Status:
This problem is documented in Knowledge Base article Q111852.
Created: 2006-03-22  

MSI Debugger Hangs with InstallScript Custom Action

Description:
In a Basic MSI project that contains at least one InstallScript custom action, running the MSI Debugger causes the InstallShield IDE to hang and stop responding.
Workaround:
Remove all InstallScript custom actions from the project.
Status:
This problem is documented in Knowledge Base article Q112061.
Created: 2006-03-22   Macrovision tracking number: 1-EUQJH

"The wrong volume is in the drive" error with multi-CD setup

Description:
If your setup spans multiple CDs you may get error messages when the setup is finished: "The wrong volume is in the drive..." or "There is no disk in the drive." (after you ejected the last CD). This only happens if you launch the install using .setup.exe, but it works properly if you start the install by double clicking the .msi file.
Workaround:
Do not include a Setup.exe in the build. Instead just ship the MSI. The disadvantage is that MSI 2.0 or any other prerequisites will not be installed, and Small or Minor Updates shipped as full .msi file will not work automatically.
Status:
This problem has been reported in the InstallShield Community Forum and has been reproduced by Macrovision.
Created: 2006-03-14   Macrovision tracking number: IOC-000042357

 FIXED IN IS12  InstallShield crashes on Right-Click in Registry View

Description:
When you right click a registry key in the Destination Computer section of the Registry view and select Permissions, the InstallShield IDE may crash with an Access Violation error. This happens after you installed Update 4.
Workaround:
Work directly within each component's registry view instead of using the global Registry view.
Status:
This problem has been reported in the InstallShield Community Forum and is documented in Knowledge Base article Q112062.
History:
2006-03-14: This problem has been reported in the InstallShield Community Forum and has been reproduced by Bryan Wolf of Macrovision .
2006-03-22: The problem is documented in Knowledge Base article Q112062
Created: 2006-03-14   Updated 2006-03-22   Macrovision tracking number: IOC-000046708

 FIXED IN IS12  StandAlone Build Tool doesn't find Merge Modules and Objects

Description:
The -o command line parameter doesn't t not work as you expect it to, resulting in build errors when you build your project with the StandAlone Build tool.
Workaround:
If you want to use the -o parameter to specify your own location for your objects and merge modules you will need to copy those files from your InstallShield 11.5 install location into the StandAlone Build install location into either a folder named "Objects" or "Modules\i386". You can then specify any path you want on the command line using the -o parameter and the build will use it. This is an unnecessary duplication of these files.
Status:
This problem has been reported in the InstallShield Community Forum and has been confirmed by Sheryl Sikora, Senior Software Build Engineer at Macrovision Corp. It is scheduled to be fixed for the InstallShield 12 release.
Created: 2006-03-14   Macrovision tracking number: IOC-000045700

 FIXED IN IS12  StandAlone Build Tool doesn't find .NET Framework 2.0 Redistributables

Description:
You may get an error message that the .NET Framework redistributable package verison 2.0 cannot be found when you build your project with the StandAlone Build tool.
Cause:
The .NET 2.0 redists are actually installed by the InstallShield 11.5 StandAlone Build to the ...\0409 folder under your StandAlone Build install location (most likely C:\Program Files\Macrovision\InstallShield 11.5 StandaloneBuild) but the StandAlone Build tool is looking for them in the root install folder of the StandAlone Build.
Workaround:
Move the files dotnetfx.exe, dotnetfx20.exe, and 1033dotnetfx.exe into the root install folder of the StandAlone Build.
Status:
This problem has been reported in the InstallShield Community Forum and has been confirmed by Sheryl Sikora, Senior Software Build Engineer at Macrovision Corp.
Fixed in InstallShield 12
Created: 2006-02-24   Last update: 2006-06-20   Macrovision tracking number: IOC-000045607

 FIXED IN IS12  Error on Windows 2003 x64 with InstallScript  Custom Actions

Description:
When installing a package from the MSI file directly, without the use of Setup.exe, in a Basic MSI project containing InstallScript custom actions and the InstallScript merge module, similar errors may be seen:
Action ended : ISMsiServerStartup. Return value 1603
1: GetInstallDriver, Can not find InstallDriver in ROT table.
Cause:
The issue stems from the InstallScript merge module. The file ISbew64.exe is not installed correctly to a machine running Windows 2003 on x64 into C:\Program Files\Common Files\InstallShield\Driver\1150\Intel. However when installing from the Setup.exe, the correct set of InstallScript engine files are installed and no error messages are seen.
Workaround:
Deploy the ISScript.msi prior to the production MSI package. Other potential workarounds are documented in knowledge base article Q111093.
Status:
 This problem is documented in knowledge base article Q111093.
Created: 2006-02-24   Macrovision tracking number: IOC-000044584

Custom Action Type "Error" Missing from Custom Action Wizard

Description:
The custom action type "Error" (which creates a custom action type 19 to display an error message and abort the installation) is not listed in the drop down list in Custom Action Wizard.
Workaround:
Right click the Custom Actions root node and select "New Error".
Status:
This problem has been reported in the InstallShield Community Forum and is reproducible.
Created: 2006-02-20  

 UPDATED  Assemblies are not removed from GAC during uninstall

Description:
When uninstalling your application assemblies may get left behind in the Global Assembly Cache (GAC).
Cause:
The MsiAssemblyName table (which you can see in Direct Editor) may be empty, or may be missing the correct ProcessorArchitecture data. For background information why this only affects uninstallation while installation works fine, please read this article in the Windows Installer Team Blog.
Workaround:
Add the missing information to the MsiAssemblyName table.
Status:
This problem has been reported in the InstallShield Community Forum here and here. The official hotfix is available in Knowledge Base article Q112155.
History:
2006-02-18: This problem has been reported in the InstallShield Community Forum here and here.
2006-05-16: An unofficial hotfix is available in the InstallShield Community Forum.
2006-06-20: The official hotfix is available in Knowledge base article Q112155.
Created: 2006-02-18   Last update: 2006-06-20  

 FIXED IN IS12  ProgId Entries Missing for DLLs Compiled with Visual Studio 2005

Description:
Applications compiled with Microsoft Visual Studio 2005 fail to register correctly and thus it will not even start up. The reason is that many entries are missing in the ProgId table in the .msi file. This happens if you are using the "COM Extract at Build" option.
Workaround:
Pre-release versions of a fix have been posted in the InstallShield Community Forum but don't seem to fix the problem for all users.
Status:
This problem has been reported in the InstallShield Community Forum and has been confirmed by Michael Urman, Software Engineer in Macrovision's InstallShield Windows Team.
Created: 2006-02-18  

Custom Action DLL Removed from Binary Table

Description:
If you have two Custom Actions using the same DLL from the Binary table, and you delete one of them, it removes your DLL From the binary table even though the other one still uses it.
Workaround:
Add the DLL back to the Binary table.
Status:
This problem has been reported in the InstallShield Community Forum.
Created: 2006-02-18  

"There is no disk in the drive" message at end of setup

Description:
When a setup that spans multiple CDs is finished and you remove the last disk from the CD drive users may get the error message: "There is no disk in the drive. Please insert a disk into drive E: Place the CD back in the drive and select Continue".
Workaround:
Do not include a Setup.exe in the build. Instead just ship the MSI. The disadvantage is that machines that do not have MSI 2.0 will require the end user to install it from Windows - Updates or from an included EXE file in your release media.
There is one other possible workaround. This would involve using the 10.5 version of the setup.exe file instead of the 11.5 version. Many things have changed between the versions so this may not work. Just as a test, try replacing the setup.exe in the built uncompressed release with version 10.5 of the EXE. You should be able to find this in the following folder:
C:\Program Files\Macrovision\IS11.5\Redist\Language Independent\Legacy\1050
Status:
Macrovision has reproduced the problem and determined it to be an issue in thier software, according to a post in the InstallShield Community Forum.
Created: 2006-02-01   Macrovision tracking number: IOC-000042357

MSBuild Error if Project Name Contains a Dot

Description:
Using InstallShield 11.5 with Visual Studio, if the project file name in your solution includes a dot, for example: 'CompanyName.ModuleName'. When you build this solution in the VS2005 IDE all works fine, but when you try to build this solution with MSBuild in command line the build fails with error: "...\Macrovision.InstallShield.targets: error: No outputs for project "CompanyName" were provided, but the installation project references "CompanyName.ModuleName.Primary output".
Cause:
The MSBuild itself in the Microsoft.Common.targets uses a converted name like "CompanyName_ModuleName" instead the project name with period.
Workaround:
Convert the name of the reference project in the .isproj file, and in the .ism file correspondly change the <FileName> of the component in the "File" table. This works well, but after each editing in IDE you must manualy refix those lines.
Status:
In the InstallShield Community Forum MichaelU of Macrovision confirmed this problem.
Created: 2006-01-24   Macrovision tracking number: IOC-000045403

XML File Encoding is Changed from UTF-8 to UTF-16

Description:
When using InstallShield XML File Changes view to modify an xml file, the encoding value of the entire xml file is being changed from UTF-8 to UTF-16 at install time. This may cause your application failing to start.
Workaround:
None.
Cause:
Macrovision made some significant changes to the XML File Changes view between IS 11 and 11.5 to make it more functional and feature-rich. In doing so, they are encountering an issue with the MSXML component that they call into to make the XML File Changes view work correctly. For some reason, it seems like MSXML wants the files to be in UTF-16 encoding format and the switch is occuring somewhere in there.
Status:
In the InstallShield Community Forum bryanwolf of Macrovision confirmed that this is unexpected behavior. It still being looked into and no resolution has been posted quite yet.
Created: 2006-01-24   Macrovision tracking number: IOC-000044312

 FIXED  Runtime Error 1001 when calling Installer Classes

Description:
When an installation attempts to call an Installer class that was built with Visual Studio 2005 and that uses .NET 2.0, run-time error 1001 occurs. In addition, .NET 1.1 Installer classes also encounter error 1001 if the .NET 2.0 version of InstallUtilLib.dll is used. (The InstallUtilLib.dll location is specified on the .NET tab of the Options dialog box. This dialog box is available form the Tools menu.)
Cause:
A bug prevented x.0 versions of .NET from using the configfile argument in the CustomActionData property. This argument is required for all versions of .NET after 1.0.
Status:
Fixed in InstallShield 11.5 Update 2/4.
Created: 2006-01-12   Last update: 2006-03-09   Macrovision tracking number: IOC-000043666, IOC-000043943

Access 97 Files Missing in Standalone Builder

Description:
When building a project that includes the Access 97 merge module with the Standalone build, not all required files are included.
Cause:
There are some dependent files of the Access 97 module that are included with the full build but not the Standalone build.
Workaround:
Navigate to the InstallShield Support directory in Windows Explorer. By default, this is C:\Program Files\InstallShield 11\Support. Copy (do not cut) all files with a .kah extension. Paste these files into the Standalone build folder.
Status:
This problem is documented in knowledge base article Q111099.
Created: 2006-01-08  

 FIXED IN IS12  Path Variables View Missing from the IDE

Description:
The Path Variables view located in the Installation Designer > Media section is not visible in the Integrated Development Environment (IDE).
Cause:
Changes included in Microsoft Internet Explorer 7 Beta 1 are affecting views contained in the IDE. At this time, Microsoft Internet Explorer 7 Beta is not compatible with InstallShield Windows Professional or Premier products.
Workaround:
Use Internet Explorer 6 on your development machine.
Status:
This problem is documented in knowledge base article Q111709. It's not really a bug but an incompatibility with the beta version of another product.
Created: 2006-01-08  

 FIXED  Duplicate File Keys for Dynamically Linked Files

Description:
If your project includes dynamic file links you may end up with duplicate keys in the File table. This results in build error -6636.
Cause:
There was a change in the way upper and lower case letters in file names are used to generate File table keys. This causes a problem if you migrate a project from an older version to InstallShield 11.5.
Status:
Fixed in InstallShield 11.5 Update 1.
History:
2005-12-23: This problem has been reported InstallShield Community Forum.
2005-12-29: Fixed in InstallShield 11.5 Update 1.
Created: 2005-12-29   Last update: 2005-12-29

 FIXED  Prerequisites that require MSI 3.1 fail to install

Description:
If your setup includes a prerequisite that requires version 3.1 of the Windows Installer runtime to install it fails to install unless MSI 3.1 is already present on the target machine. This happens even if your setup also includes the MSi 3.1 runtime and you ticked the "Requires Windows Installer engine and/or .NET Framework to be install first" box.
Cause:
This is caused by a logic error introduced in 11.5 due to code that was added for the new ClickOnce projects.
Workaround:
You could create a custom prerequisite to pre-install MSI 3.1.
Status:
Fixed in InstallShield 11.5 Update 1.
History:
2005-12-15: Michael Urman, software engineer on Macrovision's InstallShield Windows Team has confirmed this problem in the InstallShield Community Forum. They are working on a hotfix.
2005-12-19: A preliminary hotfix (which has not yet completed the QA process) is available in this InstallShield Forum thread.
2005-12-29: Fixed in InstallShield 11.5 Update 1.
Created: 2005-12-15   Last update: 2005-12-29   Macrovision tracking number: IOC-000044079

 FIXED IN IS12  Changes to radio buttons have no effect in dialog editor

Description:
When you use the Dialog Editor to change the Radio Buttons on the SetupType Dialog, changes to the Text property or the base font are just ignored.
Workaround:
Go to the Direct Editor and search for the values and change them there.
Status:
Chandima Rajakaruna of Macrovision has confirmed this bug problem in the InstallShield Community Forum.
Created: 2005-12-15   Macrovision tracking number: IOC-000043797

 FIXED  Error 1638 Occurs When Installing .NET 1.1 and J# 1.1

Description:
When end users install .NET 1.1 and J# 1.1 with a language pack onto a machine that meets the following conditions, error 1638 may occur: The .NET core, the .NET language pack, and the J# core are already on the machine. The J# language pack is not on the machine.
Cause:
This error occurs because the installation is attempting to install the already-installed J# core redistributable.
Workaround:
You can download a fixed setup.exe redistributable from knowledge base article Q111912 and copy it to the Redist\Language Independent\i386 folder.
End users can perform either of the following workarounds: Uninstall any of the three installed components through Add or Remove Programs. The recommended one to remove is J#.  Or: Manually install the J# language pack, and then run the installation again.
Status:
Fixed in InstallShield 11.5 Update 1.
History:
2005-12-16: This problem is documented in knowledge base article Q111912.
2005-12-29: Fixed in InstallShield 11.5 Update 1.
Created: 2005-12-15   Last update: 2005-12-29   Macrovision tracking number: IOC-000043217

InstallScript Projects

Runtime Error error -5003 : 0xb7 during Setup Initialization

Description:
When running a pure InstallScript setup, you might receive the following run-time error during setup initialization:
An error (-5003 : 0xb7) has occurred while running the setup.
Workaround:
A workaround is documented in Knowledge Base article Q112104.
Status:
This problem is documented in Knowledge Base article Q112104. Macrovision has not accepted it as a bug.
Created: 2006-05-16  

Runtime Dialogs appear gray after building setup with the StandAlone Build Tool

Description:
When building a pure InstallScript project on a clean machine with the StandAlone build, modified or custom dialogs may appear gray during runtime if the DPI settings on the StandAlone machine is different from the DPI settings on the main development machine.
Workaround:
To resolve this issue, the DPI setting on the clean machine must match the development machine.
Status:
This problem is documented in Knowledge Base article Q112102. Macrovision has not accepted it as a bug.
Created: 2006-05-16  

OnceClick Install (OCI) fails after latest Internet Explorer Update

Description:
The web page which is created by a web install (OneClick Install, OCI) fails to load the InstallShield ActiveX control.
Cause:
This issue seems to be relatd to latest Internet Explorer update from Microsoft, but the code workaround provided by Microsoft doesn't seem to work.
Status:
This problem has been reported in the InstallShield Community Forum.
Created: 2006-05-16  

Wrong Version Information in Self-Extracting Setup.exe

Description:
The version information for the InstallScript self-extracting executable file is not updated appropriately based on the Version setting in the Product Properties area of the General Information view. The version number that is used for the self-extracting .exe file is the version number of the InstallShield product that is used to build the self-extracting executable file.
Status:
This problem is documented in knowledge base article Q111745.
Created: 2006-04-25   Macrovision tracking number: 1-C2ORX

Add/Remove Programs entry not deleted after uninstall with x64 application

Description:
After uninstalling a x64 application, the files are removed but the entry in Add/Remove Programs control panel are left behind. This happens if you have set the REG_DB option to write to the 64 bit registry section. The same setup uninstalls properly on a 32bit windows system.
Cause:
Changing REGDB_OPTIONS to access the 64 bit section in Maintenance will cause the UninstallKey (and any other 32 bit key written by the installer) to remain behind.
Workaround:
You'll need to decide which is easier, manually deleting any 64 bit reg entries or the 32 bit entries post uninstall to make for a clean uninstall.None known.
Status:
This problem has been reported in the InstallShield Community Forum. Chris Hein of Macrovision has confirmed that this si a problem in their software.
Created: 2006-03-31   Macrovision tracking number: IOC-000046694

 FIXED  Error -5003 during setup initialization with One-Click Installs (OCI)

Description:
After installing Update 4 for InstallShield 11.5, InstallScript projects built as One-Click Installations (OCI) can fail with Error -5003 during setup initialization.
Cause:
This behavior is due to the engine32.cab file not being digitally signed properly.
Status:
Fixed in Hotfix for One-Click-Install (OCI) Problem in Update 4.
Created: 2006-03-28  

 FIXED  Files don't installed to the appropriate Program Files Folder on 64-bit target machines

Description:
After installing Update 2 for InstallShield 11.5, InstallScript installations may not install files to the appropriate Program Files Folder on 64-bit target machines.
Workaround:
None known.
Status:
Fixed in InstallShield 11.5 Update 4.
History:
2006-02-18: This problem is documented in knowledge base article Q112023.
2006-03-09: Fixed in InstallShield 11.5 Update 4.
Created: 2006-02-18   Last update: 2006-03-09   Macrovision tracking number: IOC-000045752

CAB Files of Child Installs Missing

Description:
Self-extracting .exe installations fail to extract data#.cab files of secondary (child) installations included in the Disk1 folder of the self-extracting installation. As a result, the secondary installation cannot find its data files, and it prompts for the files with the EnterDisk dialog. Unfortunately, since the files are not extracted from the parent installation's self-extracting .exe file, there is no data file to browse to. Thus, the child installation cannot be completed. This issue does not apply to InstallScript MSI installations.
Workaround:
Rename the data#.cab files before adding them to the Disk1 folder of the parent installation. Once the files have been extracted by the parent installation, rename the files with the appropriate names, and then launch the child installation.
Status:
This problem is documented in knowledge base article Q111745.
Created: 2006-01-12   Macrovision tracking number: 1-CW3Y5

 FIXED  Setup aborts silently in CopyFile or XCopyFile when source file is missing

Description:
In some cases, calling CopyFile or XCopyFile when the file does not exist in the source location causes the installation to exit without any error messages or warnings.
Status:
Fixed in InstallShield 11.5 Update 2/4
Created: 2006-01-12   Last update: 2006-03-09   Macrovision tracking number: IOC-000043943, IOC-000044506

Cannot install version 11.5 Objects if version 11.0 Objects are installed

Description:
If a user has the InstallShield 11 InstallScript objects installed on their machine and then they try to run the installation for the InstallShield 11.5 InstallScript objects, the installation runs in maintenance mode.
Cause:
This issue occurs because the same GUID was used for the InstallShield 11.5 InstallScript objects and the InstallShield 11 InstallScript objects.
Workaround:
A new download for the InstallShield 11.5 InstallScript objects will be available soon from the Downloads page of the Macrovision Web site.
Status:
This problem is documented in knowledge base article Q111745.
Created: 2006-01-12   Macrovision tracking number: IOC-000044917

 FIXED IN IS12  CopyFile crashes the setup if source file is missing

Description:
If you call CopyFile like this:
nErr = CopyFile(szPathAndFileSource,szPathAndFileDestination);
and the source file (szPathAndFileSource) doesn't exist, your setup will die. In previous versions nErr would give you some diagnostic information and setup would continue.
Workaround:
Check for the existence of the file before calling the CopyFile function using:
Is(FILE_EXISTS, szFile)
Status:
This bug has been confirmed in the InstallShield Community Forum.
Created: 2005-12-19   Macrovision tracking number: IOC-000044506

InstallScript Documentation Errors

Description:
There are several enhancements to InstallScript functionality available in InstallShield 11.5 that are not documented in the online help included with the product. Also several errors have been found in the documentation.
Workaround:
For an updated version of the online help that includes documentation for these InstallScript enhancements, see the InstallShield 11.5 Help Library on HelpNet. Details about the documentation errors can be found in knowledge base article Q111745.
Status:
This problem is documented in knowledge base article Q111745.
Created: 2005-12-15

 

 

English News Discussions Windows Installer Virtualization 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