Shop

AdminStudio
InstallShield
Advanced Installer
other products

InstallShield

WEIHNACHTSAKTION
Upgrades von End-of-Life Altversionen möglich bis 23.12.2014
Details auf Anfrage

AdminStudio

Sonderaktion für Kunden ohne gültigen Wartungsvertrag

Details auf Anfrage

endet 30.12.2014

InstallShield

NEUE VERSION InstallShield 2014

Verbesserte Updates,
Web Deploy und Azure,
Installations-Test auf virtueller Maschine u.a.

Sonderpreis für Upgrades von Express oder Professional auf Premier
Details auf Anfrage
endet 30.12.2014

InstallShield und AdminStudio Schulungen

Offizielle Kurse mit Zertifikat

weitere Infos


 

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

Bugs Bulletin: Windows Installer Engine

Known Problems in the Windows Installer Engine Version 2.0

Windows System Restore Corrupts the Windows Installer Registry Information

Description:
Windows System Restore will corrupt the Windows Installer registry information for Office (and other applications). The use of Windows System Restore is one of the known causes. In the case of Office 2003 SP1 the symptom is the following message when you use the Office Update web site:
The Office Update site is unable to check for updates on this computer. This may be happening because of one of the following reasons:
You do not have administrative privileges for this computer.
There is a network problem and the detection catalog used by the Office Update site failed to download. Go back to the Downloads home page and try running detection again.
Windows Installer patch files (.MSP files) from previously applied Office updates are missing from the \Windows\Installer hidden directory on your computer. MSP files are stored on your computer after update installation completes because they need to be referenced for future update operations. If the files are missing you will not be able to apply Office updates. You may also be unable to uninstall Office products as a result of the same problem. Please contact Microsoft Product Support Services for assistance.
You installed Office updates in the past and then upgraded from Windows Installer version 1.0 to Windows Installer version 1.1. For more information see the KB article Windows Installer May Prompt for Install Source if Unavailable.
Search for Office updates in the Download Catalog
Workarounds:
You will need to use the Windows Installer Cleanup Utility to remove the Windows Installer registry information for all installed Office products (or whatever product is affected by this error). Then you'll need to install Office 2003 again and then install any service packs and public updates. This is documented in the KB article at http://support.microsoft.com/default.aspx?scid=kb;en-us;304498
Status:
FIXED in MSI 3.0 (but installing MSI 3 will not fix it once it's broken).
The information in this article is taken from a newsgroup posting which quoted a Microsoft employee.
Created: 2004-08-05   

"INIT ERROR Failed to create MSI Engine" with Orca on Windows 2003

Description:
On Windows 2003 Server with Platform SDK of February 2003 Orca on validation tells:
"INIT ERROR Failed to create MSI Engine. Could not complete evaluation."
Also WiMakCab.vbs informs about "Invalid installer package format".
Workarounds:
None.
Status:
There is a known problem running validation on Windows Server 2003 machines. The Installer team at Microsoft is working on providing a fix for the issue.
FIXED in MSI 3.1 v2
Created: 2003-07-29    Last update: 2005-06-07

OpenPackage Method ignores "Safe Session" Flag

Description:
The OpenPackage method of the Installer object has an option IGNOREMACHINESTATE flag. Setting this flag should create a "safe session" which ignores the current computer state and also prevents changes to the computer state. While this works properly when calling the OpenPackageEx API from a C program, the flag is ignored when calling the method from VB.
Cause:
The type library in msi.dll is missing the second parameter.
Workarounds:
Use late binding. Or unregister msi.dll, replace it with the patched version in the ZIP package, then re-register the new version.
ZIP FixSafeSession.zip   Written by Christophe Lapeyre
File size: 726.269 bytes   Last update: 2003-02-01
Status:
Microsoft is investigating this problem.
Created: 2003-02-01   

Windows Installer Errors After Installing Service Pack 3 for Windows 2000

Description:
After installing SP3 for Windows 2000 your setup may fail with any of the following error messages:
"The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed. Contact your support personnel for assistance." or:
"This application must be installed to run. Please run Setup from the location where you originally installed the application." or:
"This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package." or:
"The system cannot open the device or file specified."
Workarounds:
There are several possible causes for this problem. The workarounds are documented in Microsoft Knowledge Base article Q324906.
Status:
Microsoft has confirmed that this is a problem in Windows 2000 SP3 as documented in Microsoft Knowledge Base article Q324906.
Created: 2002-10-17   

Error "The Windows Installer Service could not be accessed..."

Description:
Running your setup on Windows NT or 2000 may result in the following error message: "The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or the Windows Installer is not correctly installed. Contact your support personnel for assistance."
Workarounds:
This can be caused by incorrect DCOM settings or missing privileges on the System account. The workaround is documented in Microsoft Knowledge Base article Q319624.
Status:
This is a configuration problem on the target machine as documented in Microsoft Knowledge Base article Q319624.
Created: 2002-10-17   

Error 1706 "No valid source media found"

Description:
Trying to adhere to the current design guidelines for registering applications by installing HKCU keys through the installer, causes an error for subsequent non-admin users on per machine installations. Under the Registry Table topic in MS Installer Documentation: "Note that is recommended that registry entries written to the HKCU hive reference a component having the registryKeyPath bit is set in the Attributes column of the component table. This ensures that the installer writes the necessary registry entries when there are multiple users on the same machine". If you don't do this you won't get the HKCU entries propagated to the other users on the machine and will have to rely on the application writing these keys. The best bet is to set the bit above in the Component Table.
However this doesn't work for a restricted user in a locked down environment if you're installing from CD-ROM. It does not happen if the installation media is on the local hard drive.
Microsoft confirms that the Installer "should" be installing HKCU keys.
Cause:
When logged in as a restricted user under win2k the windows installer does not have access to the CD drive.
Workarounds:
Official workaround provided by Microsoft and confirmed by VeriTest:
Either:
- Readme how to have the admin prevent the error.
- Change the error text to be informative instead of misleading. Something along the lines of, "Please contact your system administrator..."
Or:
- Create the keys through the application
- Document this in the VQ
Solution is to enable the AllowLockdownMedia Group Policy : Add a DWORD registry key AllowLockdownMedia = 1 to HKLM\Software\Policies\Microsoft\Windows\Installer. A Waiver Request is not necessary here. Documenting this as decribed above is enough.
Remark: This policy can also be set using gpedit.msc and is found in "Computer Configuration\Administrative Templates\Windows Component\Windows Installer" and is called "Enable user to use media source while elevated", which needs to be Enabled.
Alternative workaround:
Copy the installation media to the local hard drive druing the initial install. You could do this by packaging the setup into a self extracting exe with a tool like   PackageForTheWeb.
Status:
Microsoft confirmed that this is a known problem - the Installer "should" be installing HKCU keys.
Created: 2002-01-04   

AppSearch Doesn't Find Installed File / MinVersion Field in Signature Table Documented Wrong

Description:
Windows Installer doesn't find an existing file, although it matches the parameters you entered in the Signature table.
Cause:
Windows Installer Help says that the MinVersion field of the Signature table is inclusive, i.e. it should perform a >= comparison. This is wrong, the comparison is exclusive, i.e. the searched file must have a version that is greater than the number specified in the VersionMin field.
Workarounds:
Subtract 1 from the value in the fourth field of the version number you enter in the VersionMin field, e.g. use 1.0.0.49 when 1.0.0.50 should meet the criteria, or use 1.65535.65535.65535 when searching for version 2.0.0.0 or above.
Status:
This problem has been reported in the newsgroups and is reproducible in Windows Installer 1.1, 1.2, and 2.0.
Created: 2001-04-17    Last update: 2001-10-03

Corrupted MSI Packages after Download with Netscape

Description:
When launching an .msi file the following error message may be displayed: "This installation package could not be opened. Contact application vendor to verify this is a valid Windows installation package." This happens if the .msi file was downloaded with Netscape Communicator. Another symptom is that the size of the msi file slightly increases.
Workarounds:
Download with Internet Explorer or package your msi file in a zip or self extracting exe.
Status:
This problem is reproducible with Netscape Communicator 4.77.
Created: 2001-08-04

Installation Fails with Error in SFC.DLL

Description:
Installing Windows Installer based setups or updating the Windows Installer Service may fail on Windows NT with various symptoms. In the Application Event Log you find an entry regarding file C:\WINNT\System32\SFC.DLL.
Cause:
SFC.DLL is a system file on Windows 2000 and used by Windows Installer. Although the file is not used on Windows NT, Windows Installer will try to load it if it exists. On the failing machine a file with name SFC.DLL has been installed by some third party software.
Workarounds:
Temporarily rename the existing SFC.DLL until you have installed the software.
Status:
Microsoft confirmed that this is a bug in Windows Installer version 1.2. See Knowledge Base article Q264652 for more information.
It is unknown whether this problem has been fixed in MSI 2.0.
Created: 2001-04-17

"Windows Installer service failed to start" or "Internal Error 2755"

Description:
When you try to run a Windows Installer based setup, you may receive one of these error messages:
"The Windows Installer service failed to start. Contact your support personnel."
"Error 1631: The Windows Installer service failed to start. Contact your support personnel."
"Internal Error 2755: Please contact product support for assistance."
Cause:
This happens if registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment includes one or more null empty values. Userenv.dll returns an error message when it tries to process the value, and Windows Installer quits.
Workarounds:
Remove null environment variables before you install the program.
Status:
Microsoft confirmed that this is a bug in Windows NT 4.0. A fixed version of Userenv.dll is available from Microsoft. See Knowledge Base article Q251274 for more information.
Created: 2001-04-17

Add/Remove Programs Shows Folder Icon

Description:
On Windows 2000 the Add/Remove Programs control panel applet sometimes shows a Windows Explorer folder icon for your application instead of the icon specified in the APRPRODUCTICON property of your msi package.
Cause:
This happens if a per-user installation is performed. In this case, Add/Remove Programs doesn't properly expand environment variables.
Workarounds:
Perform a per-machine installation instead, by setting ALLUSERS=1.
Status:
Microsoft confirmed that this is a bug in Windows Installer 1.0 and 1.1. It is documented in knowledge base article Q258558.
It is unknown whether this problem has been fixed in MSI 2.0.
Created: 2001-01-30

Installing From URL Through Proxy Fails

Description:
Windows Installer accepts a Uniform Resource Locator (URL) as a valid source for an installation. If the installation database is at a URL, the installer downloads the database to a cache location before starting the installation. The installer also downloads the files and cabinet files from the internet source that are appropriate for the user's selections. However this won't work if you are connected to the Internnet through a proxy server.
Workarounds:
None.
Status:
"Microsoft does not support installing using a URL through proxy server. The only support we can offer in this scenario is including the files inside the .msi file. This method has been proven successful. Windows Installer was not developped as an internet savy deployment strategy." (quoted from a newsgroup article posted by Microsoft)
Created: 2000-10-04

Build Error on Windows 2000

Description:
When you try to build a project on Windows 2000, you may receive the following message: "Fatal error -1001: Error opening MSI database ... Description: Unable to open the package. Windows Installer may not have been properly installed, or you may have an older version. Reinstall if necessary." The exact cause or conditions to reproduce the problem are unknown.
Workarounds:
Delete the files msi.dll, msiexec.exe, msihnd.dll and msimsg.dll. Then reinstall instmsiw.exe from the ISWI package.
Status:
This problem has been reported in the newsgroups.
Created: 2000-05-01

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. The entry exists in registry, but is not displayed. After you shorten the GUID with regedit, the entry appears.
Workarounds:
This problem affects legacy setup programs as well and 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:
This problem has been reported on several newsgroups.
Created: 2000-05-01    Last update: 2000-06-20

Known Problems in Previous Versions of the Windows Installer Engine

Scrollable Text Control has a Character Limit

Description:
There is a limitation in MSI 1.1 that limits Scrollable control to have about 32000 characters.
Workarounds:
None.
Status:
This problem has been reported for MSI 1.1.
MSI 2.0 does not have this limit, or it's a higher limit.
Created: 2002-01-04

Patching Requires Original Installation Source

Description:
While applying a patch (.msp file) you will be prompted to insert the original installation CD. This should not be required since the original msi file is cached on the local hard drive.
Workarounds:
None.
Status:
Microsoft has confirmed that this is a bug in Windows Installer 1.1. See Microsoft knowledge base article Q268800. This problem should be fixed in version 2.0 (not verified yet).
Created: 2000-06-14

Error 1328 When Applying a Patch

Description:
When applying a patch, you may get Error 1328. This happens if you install more than 2 incremental patches, that is, patches that don't remove the previous patch using the ListOfPatchGUIDsToReplace property on the Patch Package to remove the previously released patch transform.
Workarounds:
Since ignoring the 1328 message allows the patch to complete successfully, it is possible to set up an external UI handler to ignore this specific error message. This can be done in an bootstrapper program which calls the patch.
Status:
Microsoft confirmed that this is a bug in Windows Installer versions including 1.2. It should be fixed in version 2.0 (not verified yet).
Created: 2001-01-30    Last update: 2001-03-07

No Scroll Bar in Combo Box

Description:
If a combo box includes more items than fit into the drop down down list, a scroll bar should be displayed. At least that's how all Windows applications behave. However combo boxes on Windows Installer dialogs never have a scroll bar.
Workarounds:
Make the drop down list higher so that all items fit in the list.
Status:
This problem has been reported in several newsgroups and is reproducible with Windows Installer 1.1 and 1.2.
FIXED in Windows Installer 2.0.
Created: 2000-06-14    Last update: 2001-10-03

Patch is Not Correctly Applied

Description:
There is a 100 character limit on all of the transform names applied to an installation. For each patch, there are (at least) two transforms generated. Blowing past the limit causes unpredictable results ranging from inability to apply patch, bad reinstalls, and files left over after uninstall.
Workarounds:
Upgrade to Windows Installer 1.2 (not possible on Windows 2000) or use shorter names. For example, for two patches, you might get:
:Target01ToUpgrade01;:#Target01ToUpgrade01;:Target02ToUpgrade01;:#Target02ToUpgrade01
if you smash it to
:T1U;:#T1U;:T2U;:#T2U
you can get up to 9 patches.
Status:
Microsoft confirmed that this is a bug in Windows Installer that is fixed in version 1.2.
Created: 2001-01-30

Comments Property in Summary Information Stream is Limited to 255 Characters

Description:
The Comments string in the summary information stream must not be longer than 255 characters. Exceeding this limit causes an access violation (GPF).
Workarounds:
Shorten your text in the Comments property.
Status:
Microsoft has confirmed that this is a problem in Windows Installer 1.1 and should be addressed in 1.2.
Created: 2000-06-08

Bugs Bulletin: Merge Modules

For information about availability and download locations of merge modules, see the Merge Modules page.

Files missing after Major Upgrade with MSXML4 Merge Module

Description:
After installing a Major Upgrade for a setup that includes the MSXML4 SP2 merge mdoule the following folders are missing:
C:\WINNT\WinSxS\x86_Microsoft.MSXML2R_6bd6b9abf345378f_4.1.0.0_x-ww_29c3ad6a
and
C:\WINNT\WinSxS\x86_Microsoft.MSXML2_6bd6b9abf345378f_4.1.0.0_x-ww_b319d8da
This has been reported for the SP2 version of the MSXML4 merge modules (msxml4sys32.msm and msxml4sxs32.msm). The single merge module for MSXML 4 SP1 (msxml4.msm) doesn't seem to be affected.
The problem seems to be similar to the one documented in Microsoft Knowledge Base article 905238.
Workarounds:
Move the RemoveExistingProducts action after InstallFinalize.
Status:
This problem has been reported in several newsgroup and forum posts.
Created: 2006-05-24    Reported by Lars Sigebo

Incorrect Versioning in Visual Studio 6 SP6 Merge Modules

Description:
Comparing the actual OCXes delivered by the older merge modules and the new SP6 merge modules you can notice the following interesting discrepancies:
msmask32.ocx
6.0.84.18 - 166,600 - 4/5/2001
6.0.84.18 - 167,968 - 3/9/2004
comctl32.ocx
6.0.81.5 - 608,448 - 5/22/2000
6.0.81.5 - 609,824 - 3/9/2004
mshflxgd.ocx
6.0.88.4 - 438,976 - 5/22/2000
6.0.88.4 - 440,352 - 3/9/2004
comct232.ocx
6.0.80.22 - 164,144 - 4/3/2000
6.0.80.22 - 167,424 - 7/23/1999
mscomm32.ocx
6.0.81.69 - 103,744 - 4/3/2000
6.0.81.69 - 105,472 - 7/23/1999
msmapi32.ocx
6.0.81.69 - 137,000 - 4/3/2000
6.0.81.69 - 137,728 - 7/23/1999
The first line of each triad is the filename. The second and third lines contain the file version, size, and timestamp for the “old” and “new” files. Note that for all six files the version numbers are identical. For the first three, however, the file size and date changed, increasing in both cases. For the last three, however, the file size increased but the date regressed. Furthermore, inspection showed that the digital signatures on the last three files is invalid! The digital signature on the first three validated, so I’m not sure what the differences are.
Workarounds:
None.
Status:
This problem has been reported by a user (thanks to Toby Ovod-Everett).
Created: 2005-08-03   

Merge Modules from Visual Studio 6 SP6 Trigger System File Protection and Auto-Repairs

Description:
Some of the merge modules included in Visual Studio 6 Service Pack 6 try to update files that are under System File Protection in Windows 2000, XP and 2003. This can trigger an error message during installation. Also, later when the installed product is launched, Windows Installer may detect that the file is of lower version than its record (because the previous version was restored by SFP). As a result, it may trigger the resiliency reparation to repair the product.
Cause:
Required operating system conditions are missing from the components in these merge modules. The following modules are affected by this problem:
atl.msm
comcat.msm
mfc42.msm
mfc42u.msm
msvcirt.msm
msvcp60.msm *
msvcrt.msm
oleaut32.msm
Workarounds:
Add the following condition to the components in these merge modules:
NOT (VersionNT > 400) AND NOT (Version9X > 410)
* msvcp60.dll is not included with Windows 2000, so it is not under Windows File Protection in this operating system. Therefore in msvcp60.msm the condition should be:
NOT (VersionNT > 500) AND NOT (Version9X > 410)
Status:
This issue has been confirmed by a Microsoft support engineer in the newsgroups.
Created: 2004-04-16    Last update: 2005-01-26

Merge Modules from Visual Studio .NET 2003 Install to Wrong Directory

Description:
The merge modules for Visual C++ .NET 2003 (VC 7.1) runtime libraries aren't retargetable like they were in Visual C++ .NET 2002 (VC 7.0). As a rersult they install to the wrong directory, e.g. the root of drive C:.
Cause:
The modules are also using the wrong schema (schema 100), which means you can't even manually fix the merge modules.
Workarounds:
None.
Status:
Microsoft has accepted this as a bug and is working on a fix..
Created: 2001-10-10

VBA 6.3 Files Installed to Wrong Directory

Description:
The officevbahelpintl.msm and officehelpchmintl10.msm merge modules from the VBA 6.3 SDK install their files to directory C:\Office10\1033 instead of C:\Program Files\Microsoft Office\Office10\1033. This affects the various language versions of the mentioned merge modules.
Cause:
The Directory table entries in these merge modules are wrong. They look like this (the name of the last sub directory depends on the language version of the module):
Directory Directory_Parent DefaultDir
TARGETDIR   SourceDir
OfficeFolder.
D0DF3458_A845_11D3_8D0A_0050046416B9
TARGETDIR OFFICE10|Office10
OfficeIntlFolder.
D0DF3458_A845_11D3_8D0A_0050046416B9
OfficeFolder.
D0DF3458_A845_11D3_8D0A_0050046416B9
1033
(language specific)
Workarounds:
Open the merge modules in a editor like Orca and change the Directory table like this, to make it similar to the correct directory table in officehelpexeintl10.msm. Replace 1033 with the applicable language code for the particular module:
Directory Directory_Parent DefaultDir
TARGETDIR   SourceDir
ProgramFilesFolder.
D0DF3458_A845_11D3_8D0A_0050046416B9
TARGETDIR PFILES|Program Files
INSTALLLOCATION.
D0DF3458_A845_11D3_8D0A_0050046416B9
ProgramFilesFolder.
D0DF3458_A845_11D3_8D0A_0050046416B9
MSOFFICE|Microsoft Office
OfficeFolder.
D0DF3458_A845_11D3_8D0A_0050046416B9
INSTALLLOCATION.
D0DF3458_A845_11D3_8D0A_0050046416B9
OFFICE10|Office10
OfficeIntlFolder.
D0DF3458_A845_11D3_8D0A_0050046416B9
OfficeFolder.
D0DF3458_A845_11D3_8D0A_0050046416B9
1033
(language specific)
Status:
This problem is reproducible with VBA SDK 6.3.
Created: 2001-10-15

Invalid TahomaF Merge Module

Description:
The TahomaF.msm included with VBA SDK 6.3 does not include the required Summary Information. As a result it doesn't display a name or description in the merge modules view or merge module wizard of the InstallShield IDE. The summary information is required for merge modules by the MSI documentation. Validating the module with Orca results in a ICE39 error.
Workarounds:
None.
Status:
This problem is reproducible with version 6.0.9206 og TahomaF.MSM as included with VBA SDK 6.3.
Created: 2001-10-10

Oleaut32.msm Triggers Auto Repair or System File Protection Error on Windows 2000

Description:
Installing a packge that includes the new module on Windows 2000 brings up "Error 1931.The Windows Installer service cannot update the system file C:\WINNT\System32\olepro32.dll because the file is protected by Windows. You may need to update your operating system for this program to work correctly."
Another symprom is Windows Installer unexpectedly performing an auto repair when the system is started.
Cause:
Oleaut32.msm installs system files that are under Windows File Protection on Windows 2000 and should not be installed on this operating system.
Some versions of Microsoft's Oleaut32 merge modules do not include any component conditions to prevent installation of these files on Windows 2000, Oleaut32.msm version 2.40.4514.1 as included in the VBA SDK 6.2 includes corrupted conditions:
  (Version9X OR (VersionNT < 500)
In this condition, a parenthesis is missing.
Workarounds:
Open the msm and change the condition to:
  (Version9X) OR (VersionNT < 500)
Status:
The corrupted conditions has been reported in the newsgroups for oleaut32.msm version 2.40.4514.1 dated March 3, 2000 that came with the English Edition of the VBA SDK 6.2. in March 2000.
In Oleaut32.msm version 2.40.4275.1 that comes with Service Pack 4 for Visual Studio 6 SP4 and SP5, Visual Studio Installer 1.1, and VBA SDK 6.3 there is no operating system condition on the components at all.
Oleaut32.msm version 2.40.4514.1 that comes with the multi-language edition of the VBA SDK 6.2 (July 2000) has the correct conditions.
The problem is documented in Microsoft Knowledge Base article 316911 which states that a fix is availbale from Microsoft.
Created: 2000-05-16    Last update: 2003-07-10

Merge Module Don't Install Files

Description:
Although you added merge modules to your setup project, the files don't get installed. This happens after you installed Orca or some other tool from the Windows Installer SDK Version 1.5 Beta 1.
Cause:
Version 1.5 Beta 1 of the WIndows Installer SDK, Visual Studio.NET and beta versions of Windows XP include a beta version of Mergemod.dll that is not compatible with previous versions and thus breaks current Windows Installer authoring tools.
Workarounds:
Re-register the release version of Mergemod.dll using Regsvr32.exe.
Status:
Microsoft has confirmed this to be a bug in the beta version of Mergemod.dll. It should be fixed in the final release.
Created: 2001-04-17

BDE Merge Modules Fail in Silent Install

Description:
If you run your setup in silent mode using the /q command line switch, some of the files in the BDE merge modules don't get installed.
Cause:
Some components have conditions that are set by custom actions. These actions are only inserted to the User Interface sequence. In silent mode this sequence is not executed by Windows Installer.
Workarounds:
Set the properties MSSQL and ORACLE in a custom action if your setup runs in silent mode.
Status:
This problem is reproducible with the BDE 5.11 merge modules.
Created: 2001-04-17

ATL Merge Module Fails to Register

Description:
Adding Microsoft's "ATL Module for Windows" (ATL.MSM) to your setup does not properly register ATL on the target pc. On Windows 95 and Windows 98 it doesn't even copy ATL.DLL (this works on Windows NT).
Cause:
There are several bugs in the ATL.MSM, for instance Microsoft has mis-spelled the condition for the ANSI version of ATL.DLL as "Version9x", which should be "Version9X".
Workarounds:
This zip file includes instructions how to fix atl.msm and a validation table.
ZIP FixAtlMsm.zip   From newsgroup microsoft.public.platformsdk.msi
File size: 3.514 bytes   Last update: 2000-05-27
Status:
Microsoft has confirmed that this is a bug in ATL.MSM.
At least some of them are fixed in Visual Studio 6 Service Pack 4 and Visual Studio Installer 1.1.
VS6 SP5 includes an updated version of ATL.MSM. There is currently no information about fixes in the new version.
Created: 2000-03-25   Last update: 2001-03-07

MSDERUN Merge Module Isn't Working [FIXED]

Description:
Adding Microsoft's "Microsoft Data Environment Runtime" merge module (MSDERUN.MSM) to your setup copies Msderun.dll to the target pc, but does not register it properly.
Workarounds:
Add the Common Files Folder in the File System editor.
Add a sub folder named Designer to the Common Files Folder.
Add the MSDERUN.DLL file to the Designer folder.
Set the Register property for this file to 1-vsifrSelfReg.
Status:
Microsoft has confirmed that this is a bug in Msderun.msm version 6.0.84.50.
FIXED in version 6.0.88.4 that comes with Visual Studio 6 SP 4 and VSI 1.1.
Created: 2000-05-27    Last update: 2000-09-16

Incorrect Version Numbering in Microsoft's Merge Modules

Description:
Microsoft doesn't follow consistent rules in versioning their merge modules. Examples:
ATL.MSM: There are two different releases of this merge module, both version 3.0.8449.0, one dated May 26, 2000 and released with VSI 1.0, the other dated June 1, 2000 and released with VSI 1.1 and VS6 SP4. The latter fixes some bugs that had been discovered in the older version.
OLEAUT32.MSM: The version released with VSI 1.1 and VS6 SP4, dated June 1, has version 2.40.4275.1, which is lower than the oleaut32.msm released with VBA SDK 6.2, dated March 3, 2000 with version number 2.40.4514.1 (includes a known bug). The July release of the VBA SDK also includes a oleaut32.msm version 2.40.4514.1, dated July 12, 2000, where that bug is fixed.
Workarounds:
None.
Status:
This problem can be seen by examining the modules with Orca.
Created: 2000-08-09    Last update: 2000-09-04
See also: Bugs in MSDE 2000 Merge Modules

 

 

 

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 © 1997-2014 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