OCX file is not deployed from MSI generated using Visual Studio 2003 on Windows 7

Question

I have an outdated installation from a DotNet 1.1 application (with Visual Studio 2003) that will not deploy the msflxgrd.ocx file in a FIRST installation on Windows 7. If I remove MSI, then run the same MSI again (and future installations on that same laptop), the msflxgrd.ocx file is being deployed. At first I suspected that this was a regsvr32 problem, but since there is no file to register, it is most likely a deployment problem. I have administrator privileges on machines.

I have links to MSI logs here :

Can anybody help?

Thanks!

Answer 1

My previous answer was to explain what is going wrong. The answer will be how to fix it.

InstallShield distributes a merge module for this control, which contains version 6.0.84.18. However, it seems that this merge module is old and does not include the security update released by Microsoft several years ago. See Section:

Merge Modules Updated for Security Bulletin MS08-070

In the stream, Mike Marino tried to get updated merge modules from Microsoft, but he was told:

Microsoft will not provide merge modules for this. They recommended that users either create their own MSM or include these files in their MSI.

So here is what I will do. Make sure msflxgrd.dll is the latest version from MS08-070 (6.1.98.14) or later. Create it in your installer in the SystemFolder directory. Mark it as Permanentenet = true. Set the Register attribute to vsdraCOM and set SharedLegacyFile = true.

Restore your installer and check your upgrade script again. You should be good to go.

Answer 2

From what I see in Magazine 1, the car is not as clean as you think. FindRelatedProducts finds the previous installation of your product and tells RemoveExistingProducts to remove it before installing the new version.

I saw situations when the rules of the components are violated, that MSI believes that the file does not need to be installed, but the file is deleted due to the removal of the updated product and the file is not installed. Uninstalling and reinstalling, you break it down into two steps so that when the second installation evaluates the need for a file, it returns as “yes” and installs.

The fact that this is an OCX COM server is just a coincidence and is not related to the real problem.

I will need MSI already installed and an MSI update to give you specific fixes.

---

Beginning of action 2:55:44 p.m .: FindRelatedProducts. MSI (s) (A0: 18) [14: 55: 44: 119]: REAL ESTATE: adding the PREVIOUSVERSIONSINSTALLED property. Its value is '{08D8BF6E-E399-4B8A-8B8D-7DFF68F81131}'. MSI (s) (A0: 18) [14: 55: 44: 119]: Skip action: ERRCA_CANCELNEWERVERSION (false condition) MSI (s) (A0: 18) [14: 55: 44: 119]: Perform action: VSDCA_VsdLaunchConditions Action completed 14:55:44: FindRelatedProducts. Return value 1.