14 replies to this topic

[jmorgret]

I have added the MDAC 2.7 merge module to my project but when I run the setup, MDAC 2.7 is never installed. I created a log file when I ran the setup and there are two references to MDAC in the log. Early in the log it says something to the effect MDAC; absent. Later the log reads MDAC;null.

If anyone has any ideas why this might be happening please let me know.

Thanks,

Jennifer

[Stefan Krueger]

From which source did you get this module? How is it supposed to work?

[jmorgret]

I downloaded the merge module from InstallShield. I thought it should just work if I selected it in the Merge Modules view. I need it to install MDAC 2.7 if there is any version lower than 2.7 found on the machine.

[Stefan Krueger]

That's strange. What are the installed, request, and action states for MDAC in the two log locations? Maybe you can post the relevant log lines here.
Is this a fresh install or are you installing an update?

[jmorgret]

This is a fresh install not an update. The log has the following lines:

MSI (s) (30:D0): Component: MDAC27.C9C35FC7_5AEE_4C1E_8BD2_80ED9FA87FFF; Installed: Absent; Request: Local; Action: Local

MSI (s) (30:D0): Component: __MDAC27.C9C35FC7_5AEE_4C1E_8BD2_80ED9FA8765; Installed: Null; Request: Local; Action: Local
MSI (s) (30:D0): Component: __MDAC27.C9C35FC7_5AEE_4C1E_8BD2_80ED9FA8766; Installed: Null; Request: Local; Action: Local

Action start 10:56:50: CheckForMDACInstall.C9C35FC7_5AEE_4C1E_8BD2_80ED9FA87FFF.
MSI (s) (30:D0): Creating MSIHANDLE (161) of type 790542 for thread 976
MSI (s) (30:D0): Creating MSIHANDLE (162) of type 0 for thread 976
MSI (s) (30:D0): Closing MSIHANDLE (162) of type 0 for thread 976
MSI (s) (30:D0): Closing MSIHANDLE (161) of type 790542 for thread 976
Action ended 10:56:50: CheckForMDACInstall.C9C35FC7_5AEE_4C1E_8BD2_80ED9FA87FFF. Return value 0.
MSI (s) (30:D0): Skipping action: DisplayErrorMessage.C9C35FC7_5AEE_4C1E_8BD2_80ED9FA87FFF (condition is false)
MSI (s) (30:D0): Skipping action: InstallMDAC.C9C35FC7_5AEE_4C1E_8BD2_80ED9FA87FFF (condition is false)
MSI (s) (30:D0): Skipping action: MDAC_RebootAtEnd.C9C35FC7_5AEE_4C1E_8BD2_80ED9FA87FFF (condition is false)

The version of MDAC that is installed on this machine is 2.53.

[Glytzhkof]

I would open the merge module in Installshield Developer, go to the direct editor and check the conditions associated with the different components.

[Stefan Krueger]

I would be interested in the condition that's used for this custom action in the merge module: InstallMDAC.C9C35FC7_5AEE_4C1E_8BD2_80ED9FA87FFF

[jmorgret]

There are no conditions listed for the MDAC component or the custom action. Are there supposed to be conditions?

I have contacted InstallShield support. Their answer was that the setup was determining that MDAC does not need to be updated even though the current version is 2.53. They suggested that I just run the MDAC install manually from the setup. Not much help.

[Stefan Krueger]

I don't mean a condition on a component, but on the custom action in the ModuleInstallExecute or ModuleInstallUI sequence table

[jmorgret]

InstallMDAC.C9C35FC7_5AEE_4C1E_8BD2_80ED9FA87FFF
Condition: ($MDAC27.C9C35FC7_5AEE_4C1E_8BD2_80ED9FA87FFF = 3) AND (INSTALL_MDAC=1)

From the ModuleInstallExecuteSequence

[Stefan Krueger]

Judging from the log file you posted the first part of the condition should be true. What's the value of the INSTALL_MDAC property in the log?

[wolfUkr]

Why $MDAC27.C9C35FC7_5AEE_4C1E_8BD2_80ED9FA87FFF = 3. What mean this value?
Can I write condition where compare different version MDAC, and if MDAC in merge module was early - install that package.
I insert Merge Module Custom Action, before InstallWelcome.

[Stefan Krueger]

[Sillen]

Hi (My first message here Sweet )

I had exactly the same problem but after some research I found a solution. I used the MDAC27ENU.msm (version 2.71.9040.2 from InstallShields download page) but it didn’t install MDAC. I found that in the MergeModule is a VBscript called Check and in that script is a property called MDAC27_SETUP_VER used but there is no property called this in the Merge Module. So the solution is to add a property MDAC27_SETUP_VER with the value 2.71.9040.2 to your installation then it works fine. I think this is a bug in the SP1 version of the MDAC MergeModule because the old MSM (version 2.70.9001.0) don’t use the property MDAC27_SETUP_VER but MDAC_SETUP_VER.

/Sillen

[SourceList]

Isn't that supposed to be set via a system search for MDAC on the machine (using the Reglocator Table etc)?

Seems odd that you'd want to specify it on the command line or set it in the MSM itself?